From owner-freebsd-stable Mon Jan 1 0:39:52 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 00:39:50 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.com (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id DB06137B400 for ; Mon, 1 Jan 2001 00:39:49 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.com (Postfix) with ESMTP id 64AE1177E40; Mon, 1 Jan 2001 02:43:24 -0600 (CST) Message-ID: <026e01c073ce$dafdd7a0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: Cc: , References: <200012312213.PAA03257@freeway.dcfinc.com> Subject: Re: 4.2-stable, ports/packages in XF86 4.0.2 Date: Mon, 1 Jan 2001 02:43:03 -0600 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last I checked it would build but would core dump when you try to run it unless it has been fixed. ----- Original Message ----- From: "Chad R. Larson" To: "David W. Chapman Jr." Cc: ; Sent: Sunday, December 31, 2000 4:13 PM Subject: Re: 4.2-stable, ports/packages in XF86 4.0.2 > As I recall, David W. Chapman Jr. wrote: > > The problem is netscape itself, since it comes in binary format, > > anyone who ports it doesn't have a choice into which format, I believe > > the bsdi version of netscape is elf, but I'm not totally sure. > > Or, you could build Mozilla from sources... > > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > chad@dcfinc.com chad@larsons.org larson1@home.com > DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 2: 9:51 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 02:09:50 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shark.harmonic.co.il (jupiter.harmonic.co.il [192.116.140.62]) by hub.freebsd.org (Postfix) with ESMTP id EE8E037B400 for ; Mon, 1 Jan 2001 02:09:48 -0800 (PST) Received: from localhost (roman@localhost) by shark.harmonic.co.il (8.9.3/8.9.3) with ESMTP id MAA21594; Mon, 1 Jan 2001 12:09:30 +0200 Date: Mon, 1 Jan 2001 12:09:30 +0200 (IST) From: Roman Shterenzon To: opentrax@email.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support In-Reply-To: <200012282317.PAA04405@spammie.svbug.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Dec 2000 opentrax@email.com wrote: > > On 28 Dec, Gerald Pfeifer wrote: > > Having been hit by this today, how about MFCing the following change? > > > > revision 1.289 > > date: 2000/11/14 01:11:13; author: jkh; state: Exp; lines: +4 -1 > > In the year 2000, I think it's perfectly reasonable to include audio > > support by default in GENERIC. > > > I can't answer for JKH or others but audio has had a history > of problems, especially durning the boot-up probe stage. > Problems such that it might lock up the machine under > certain conditions. Perhaps this is the reason sound may > never make it into GENERIC. Yes, I really hope that it doesn't make it into the GENERIC. GENERIC kernel should provide fully functional and stable machine without bells and whistles. Sound is a luxury. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 2:22:56 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 02:22:53 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shark.harmonic.co.il (jupiter.harmonic.co.il [192.116.140.62]) by hub.freebsd.org (Postfix) with ESMTP id 1FCBC37B400 for ; Mon, 1 Jan 2001 02:22:52 -0800 (PST) Received: from localhost (roman@localhost) by shark.harmonic.co.il (8.9.3/8.9.3) with ESMTP id MAA22076; Mon, 1 Jan 2001 12:22:46 +0200 Date: Mon, 1 Jan 2001 12:22:45 +0200 (IST) From: Roman Shterenzon To: Stan Brown Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Serial port character loss In-Reply-To: <20001230214035.127F237B402@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This belongs to questions I think. I don't know what is the problem here; I once used sysdep1.c from minicom in one project, and it worked just fine! You can probably make a .xs perl module from it. On Sat, 30 Dec 2000, Stan Brown wrote: > I am writing a perl program to take in serial data, pares it, and put it n a > database. > > Today I started geting wierd results, and after debuging for while discovered I was > losing characters. Check all the obvious handshaking issues, and did not find it, > so I resorted to minicom to check to see if it was my code. Mushc to my suprise I > find that I can not reliably transfer characters betwee 2 STABLE machine. One is a > P75 ,and th othe is a PII 233. > > Both have what I _thought were decent UARTS: > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > > Any sugestions to make this work? BTW, I tried both Xoff/Xon and hardware > handshaking. If I inser 1/2 secind delay betwen each line, all is well. > > > > -- > Stan Brown stanb@awod.com 843-745-3154 > Charleston SC. > -- > Windows 98: n. > useless extension to a minor patch release for 32-bit extensions and > a graphical shell for a 16-bit patch to an 8-bit operating system > originally coded for a 4-bit microprocessor, written by a 2-bit > company that can't stand for 1 bit of competition. > - > (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 2:25:53 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 02:25:51 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shark.harmonic.co.il (jupiter.harmonic.co.il [192.116.140.62]) by hub.freebsd.org (Postfix) with ESMTP id C163B37B400 for ; Mon, 1 Jan 2001 02:25:49 -0800 (PST) Received: from localhost (roman@localhost) by shark.harmonic.co.il (8.9.3/8.9.3) with ESMTP id MAA22189; Mon, 1 Jan 2001 12:25:40 +0200 Date: Mon, 1 Jan 2001 12:25:40 +0200 (IST) From: Roman Shterenzon To: Mike Tancsa Cc: stable@FreeBSD.ORG Subject: Re: slow NAT ? In-Reply-To: <4.2.2.20001231124602.01d21878@marble.sentex.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Dec 2000, Mike Tancsa wrote: > > I upgraded my home firewall today to sources as of last night and noticed > that traffic via NAT is rather slow. For example, an ftp from a machine > being nat'd I guess about 300Kbps. From the FreeBSD box, I get about 1Mb > on my DSL connection. If I use squid or a proper proxy, its not an > issue. This is both with the built in NAT on PPP and NATD by itself. Any > ideas as to how to track this down ? > 4.2-STABLE FreeBSD 4.2-STABLE #0: Sat Dec 30 09:37:21 EST 2000 > Its only a CPU: Pentium/P55C (167.05-MHz 586-class CPU) with 96M of RAM. Was it that slow before the upgrade? As a workaround you can use ipnat which performs NAT in kernel-space rather than in user-space (as libalias does). --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 2:28:45 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 02:28:43 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shark.harmonic.co.il (jupiter.harmonic.co.il [192.116.140.62]) by hub.freebsd.org (Postfix) with ESMTP id 0296137B400 for ; Mon, 1 Jan 2001 02:28:42 -0800 (PST) Received: from localhost (roman@localhost) by shark.harmonic.co.il (8.9.3/8.9.3) with ESMTP id MAA22297; Mon, 1 Jan 2001 12:28:33 +0200 Date: Mon, 1 Jan 2001 12:28:32 +0200 (IST) From: Roman Shterenzon To: "Chad R. Larson" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: alternative network media In-Reply-To: <200012312328.QAA03494@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Dec 2000, Chad R. Larson wrote: > As I recall, Ben Jackson wrote: > >> So, I bought this ultra-slim Sony notebook (Vaio SR-5K) and it has > >> both USB and Firewire ports on it. That got me thinking. Has > >> anyone tried to develop IP drivers for either of those? > > > > Pretty neat to see kldload usb, kldload if_kue, usbd -e, and poof, a > > new interface. > > Any Firewire networking support? The 400 Mbit oughta screem. Just a side note; what is the bandwidth of your harddisk? :) --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 2:37:28 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 02:37:26 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shark.harmonic.co.il (jupiter.harmonic.co.il [192.116.140.62]) by hub.freebsd.org (Postfix) with ESMTP id 00D7737B400 for ; Mon, 1 Jan 2001 02:37:25 -0800 (PST) Received: from localhost (roman@localhost) by shark.harmonic.co.il (8.9.3/8.9.3) with ESMTP id MAA22430; Mon, 1 Jan 2001 12:32:23 +0200 Date: Mon, 1 Jan 2001 12:32:22 +0200 (IST) From: Roman Shterenzon To: Greg Lehey Cc: freebsd-stable@FreeBSD.ORG Subject: Re: vinum malfunction! In-Reply-To: <20001231101426.K99806@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've submitted kern/22021 which was left untouched, it has all the needed details. :( On Sun, 31 Dec 2000, Greg Lehey wrote: > [Format recovered--see http://www.lemis.com/email/email-format.html] > > Please limit your lines to < 80 characters. > > On Saturday, 30 December 2000 at 19:00:27 +0100, O. Hartmann wrote: > > Dear Sirs. > > Today I run a make world and compiled a new kernel for our server, > > which uses a vinum RAID 0. At the same time I reconfigured the > > kernel to use SC console driver and VESA instead of VT console. > > > > Since the new kernel got compiled loading of vinum fails! I do not > > know why, I removed all kernel changes, but it does not help. > > > > Does anyone know why? > > Of course not. You haven't given *any* details. > > Take a look at http://www.vinumvm.org/vinum/how-to-debug.html and give > some information, and I'll probably be able to help. > > Greg > -- > When replying to this message, please take care not to mutilate the > original text. > For more information, see http://www.lemis.com/email.html > 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-stable" in the body of the message > --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 3:13:59 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 03:13:57 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from OpsyDopsy.net.dhis.org (unknown [213.22.0.13]) by hub.freebsd.org (Postfix) with ESMTP id C180C37B400 for ; Mon, 1 Jan 2001 03:13:56 -0800 (PST) Received: by OpsyDopsy.net.dhis.org (8.11.1/8.11.1) id f01BF5C01865 for stable@freebsd.org; Mon, 1 Jan 2001 11:15:05 GMT (envelope-from root) From: Joao Fernandes Reply-To: root@OpsyDopsy.net.dhis.org To: stable@freebsd.org Subject: Programming In C List? Date: Mon, 1 Jan 2001 11:14:13 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <01010111150500.01860@OpsyDopsy.net.dhis.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone knows where I could post a problem I'm having with programming in FBSD? Thanks in advance. Joao Fernandes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 3:16:42 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 03:16:40 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shark.harmonic.co.il (jupiter.harmonic.co.il [192.116.140.62]) by hub.freebsd.org (Postfix) with ESMTP id 8DA1137B400 for ; Mon, 1 Jan 2001 03:16:38 -0800 (PST) Received: from localhost (roman@localhost) by shark.harmonic.co.il (8.9.3/8.9.3) with ESMTP id NAA24029; Mon, 1 Jan 2001 13:16:31 +0200 Date: Mon, 1 Jan 2001 13:16:31 +0200 (IST) From: Roman Shterenzon To: Joao Fernandes Cc: stable@FreeBSD.ORG Subject: Re: Programming In C List? In-Reply-To: <01010111150500.01860@OpsyDopsy.net.dhis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG freebsd-questions@freebsd.org On Mon, 1 Jan 2001, Joao Fernandes wrote: > Does anyone knows where I could post a problem I'm having with programming in > FBSD? > > Thanks in advance. > > Joao Fernandes > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 3:33:10 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 03:33:08 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id 697DB37B400 for ; Mon, 1 Jan 2001 03:33:07 -0800 (PST) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f01BX6q46169 for ; Mon, 1 Jan 2001 12:33:06 +0100 (CET) Received: from rose.lpthe.jussieu.fr (root@177.ext.jussieu.fr [134.157.81.177]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f01BX4311519 for ; Mon, 1 Jan 2001 12:33:04 +0100 (MET) Received: (from michel@localhost) by rose.lpthe.jussieu.fr (8.11.1/8.11.1) id f01AXcX00471 for freebsd-stable@FreeBSD.ORG; Mon, 1 Jan 2001 11:33:38 +0100 (CET) (envelope-from michel) Date: Mon, 1 Jan 2001 11:33:38 +0100 From: Michel Talon To: freebsd-stable@FreeBSD.ORG Subject: Re: Need Assistance ASAP -- PLEASE Message-ID: <20010101113338.A445@lpthe.jussieu.fr> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <013f01c07386$ac3e2660$1001220a@zeus> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <013f01c07386$ac3e2660$1001220a@zeus> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 31, 2000 at 07:06:21PM -0500, Brandon L. Newport wrote: > Ok here is the deal, I am setting up a new server for a company (just happens to be my fathers). He has heard many things about Linux and has an NT server currently. The problem he "knows Windows really good", so about once a week he breaks things and calls me of course. He heard Linux was faster, better and of course cheaper than NT. So he wanted to go that route. However because I am technical support for him I would like to use FreeBSD instead. > > I know Linux pretty well. I work with Solaris and NT but I dont know FreeBSD. I am the the newbie stages of learning it. > > Here is the big problem, He just brought the parts for the server I spec'd out by yesterday. I have configured it and actually have FreeBSD installed. However I cannot get a few things working and it has to up and running by next Sunday 100%!!!! > > So here is the machine: > > Supermicro Motherboard P6DGU (Dual Processor, onboard SCSI, USB) > Duel PIII - 650MHz processors > 256MB RAM > 9G IBM SCSI > 4G IBM SCSI > 2G Seagate SCSI > 18G IBM SCSI > Matrox G450 32MB > Hitachi 17" Monitor > Yamaha CD-RW There may be a problem with the Matrox G450. We have received some at the lab, and up to now, the guy in charge has not been able to run X on these video cards (under Linux). I have read the XFree4.02 doc, and apparently it can run the G450 with some additionnal soft to be downloaded somewhere. All the other parts and softs are very standard, and can be installed on FreeBSD exactly the same as under Linux. -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 4:16:28 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 04:16:25 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from front001.cluster1.charter.net (outbound.charter.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id BAE5837B400 for ; Mon, 1 Jan 2001 04:16:24 -0800 (PST) Received: from [24.217.145.132] (HELO dave) by front001.cluster1.charter.net (CommuniGate Pro SMTP 3.3.2a) with SMTP id 12418059; Mon, 01 Jan 2001 07:16:20 -0500 From: David Uhring To: , freebsd-stable@FreeBSD.ORG Subject: Re: Boot ManagerQuestions Date: Mon, 1 Jan 2001 06:16:20 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="US-ASCII" References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01010106162000.00126@dave> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday 29 December 2000 15:46, doug@safeport.com wrote: > I hit issues here because I have a couple of old Dell LM laptops that > make find work stations (at least through KDE 1.9). > > I have two questions: > > 1) Sometimes sysinstall leaves without (re)writing the MBR. The fix > as pointed out to me on this list by Steve Coles is "fdisk /mbr". > This (fdisk) is such dirt dumb code it would seem nothing too serious > is broken here. Is this worth fixing? > > 2) I have a new system that came no OS but had some diagonistics on a > small DOS partition. I thought it would be cool to leave them > there so I left the utility partition and divided the disk up as > follows: > > 10Mb - utility partition > 5G - FreeBSD > ~16G - win98 > > As it came from the factory, the first partition was listed (by > sysinstall) as unknown. I installed FreeBSD and then windows. > After doing windows I had to do the fdisk bit. At the end of this I > had: > > F1 = DOS (the utilities) > F2 = FreeBSD > F3 = Windows 98 > > I messed up on the sizes so I did it again. This time through, > sysinstall said "You only get one FAT" (my wording) and marked the > 3rd partition as unknown. > > How come you only get one fat? Multiple DOS partitions obviously > work in general. > > Does anyone know the MS/IBM approved codes for the various types > > 6 = DOS FAT16 > ? = DOS FAT32 > 165 = FreeBSD > ? = others > > Would sysinstall let me have a FAT16 and a FAT32? > > Thanks for any thoughts and/orpointers > > _____ > Douglas Denault > doug@safeport.com > Voice: 301-469-8766 > Fax: 301-469-0601 > List of partition types from Linux fdisk: Command (m for help): Partition number (1-10): Hex code (type L to list codes): 0 Empty a OS/2 Boot Manag 65 Novell Netware a6 OpenBSD 1 DOS 12-bit FAT b Win95 FAT32 75 PC/IX a7 NEXTSTEP 2 XENIX root c Win95 FAT32 (LB 80 Old MINIX b7 BSDI fs 3 XENIX usr e Win95 FAT16 (LB 81 Linux/MINIX b8 BSDI swap 4 DOS 16-bit <32M f Win95 Extended 82 Linux swap c7 Syrinx 5 Extended 40 Venix 80286 83 Linux native db CP/M 6 DOS 16-bit >=32 51 Novell? 85 Linux extended e1 DOS access 7 OS/2 HPFS 52 Microport 93 Amoeba e3 DOS R/O 8 AIX 63 GNU HURD 94 Amoeba BBT f2 DOS secondary 9 AIX bootable 64 Novell Netware a5 BSD/386 ff BBT The codes for BSDI are not current. BSDI-4.1 uses (IIRC) 9e. Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 5:51:52 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 05:51:49 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 88C1837B400 for ; Mon, 1 Jan 2001 05:51:48 -0800 (PST) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1) with ESMTP id f01Dpf702131; Mon, 1 Jan 2001 08:51:42 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010101084935.01e47880@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 01 Jan 2001 08:51:40 -0500 To: Roman Shterenzon From: Mike Tancsa Subject: Re: slow NAT ? Cc: stable@FreeBSD.ORG In-Reply-To: References: <4.2.2.20001231124602.01d21878@marble.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:25 PM 1/1/2001 +0200, Roman Shterenzon wrote: >On Sun, 31 Dec 2000, Mike Tancsa wrote: > > > > > I upgraded my home firewall today to sources as of last night and noticed > > that traffic via NAT is rather slow. For example, an ftp from a machine > > being nat'd I guess about 300Kbps. From the FreeBSD box, I get about 1Mb > > on my DSL connection. If I use squid or a proper proxy, its not an > > issue. This is both with the built in NAT on PPP and NATD by itself. Any > > ideas as to how to track this down ? > > 4.2-STABLE FreeBSD 4.2-STABLE #0: Sat Dec 30 09:37:21 EST 2000 > > Its only a CPU: Pentium/P55C (167.05-MHz 586-class CPU) with 96M of RAM. > >Was it that slow before the upgrade? >As a workaround you can use ipnat which performs NAT in kernel-space >rather than in user-space (as libalias does). It was somewhat slower, but not this bad. However, I dont have any benchmarks from before to measure the difference. I will try IPNAT to see if that helps at all. Thanks, ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 6:40:20 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 06:40:18 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shark.harmonic.co.il (jupiter.harmonic.co.il [192.116.140.62]) by hub.freebsd.org (Postfix) with ESMTP id DBEB437B400 for ; Mon, 1 Jan 2001 06:40:16 -0800 (PST) Received: from localhost (roman@localhost) by shark.harmonic.co.il (8.9.3/8.9.3) with ESMTP id QAA31530; Mon, 1 Jan 2001 16:40:09 +0200 Date: Mon, 1 Jan 2001 16:40:08 +0200 (IST) From: Roman Shterenzon To: Erich Zigler Cc: stable@FreeBSD.ORG Subject: Re: seekp() In-Reply-To: <20001226142555.A75344@superhero.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 Dec 2000, Erich Zigler wrote: > I'm currently working on porting a program in C++ on 4.2-STABLE. Everytime I > use a seekp() the program compiles fine, but it cores when the seekp() is > called. > > I am working on Gabber, http://gabber.sourceforge.net > > I was wondering if anyone else had similar problems with seekp() in other > programs? seekp() seems to be called correctly at least by every reference > book I can find. From /usr/src/contrib/libio/iostream.cc: ostream& ostream::seekp(streampos pos) { pos = _strbuf->pubseekpos(pos, ios::out); if (pos == streampos(EOF)) set(ios::badbit); return *this; } ostream& ostream::seekp(streamoff off, _seek_dir dir) { streampos pos = _IO_seekoff (_strbuf, off, (int) dir, _IOS_OUTPUT); if (pos == streampos(EOF)) set(ios::badbit); return *this; } Are you sure you're doing it right? --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 6:51:46 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 06:51:43 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id 50DA837B400 for ; Mon, 1 Jan 2001 06:51:39 -0800 (PST) Received: from world.std.com (root@world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id JAA23858; Mon, 1 Jan 2001 09:51:36 -0500 (EST) Received: (from kwc@localhost) by world.std.com (8.9.3/8.9.3) id JAA12871; Mon, 1 Jan 2001 09:51:20 -0500 (EST) Date: Mon, 1 Jan 2001 09:51:20 -0500 (EST) From: Kenneth W Cochran Message-Id: <200101011451.JAA12871@world.std.com> To: David Uhring Subject: Re: Boot ManagerQuestions Cc: freebsd-stable@freebsd.org References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Another datapoint... Try this URL: http://www.win.tue.nl/math/dw/personalpages/aeb/linux/partitions It has descriptions & discussion of partition types. I found this from the SlashDot article about the FreeBSD partition-ID problem on some recent IBM ThinkPads. The same URL shows up on an AltaVista search of "partition +types". -kc >From: David Uhring >To: , freebsd-stable@FreeBSD.ORG >Subject: Re: Boot ManagerQuestions >Date: Mon, 1 Jan 2001 06:16:20 -0600 > >On Friday 29 December 2000 15:46, doug@safeport.com wrote: >> I hit issues here because I have a couple of old Dell LM laptops that >> make find work stations (at least through KDE 1.9). >> >> I have two questions: >> >> 1) Sometimes sysinstall leaves without (re)writing the MBR. ... >> >> 2) I have a new system that came no OS but had some diagonistics on a >> small DOS partition. ... > >[...] > >> Does anyone know the MS/IBM approved codes for the various types >> >> 6 = DOS FAT16 >> ? = DOS FAT32 >> 165 = FreeBSD >> ? = others >> >> Would sysinstall let me have a FAT16 and a FAT32? >> >> Thanks for any thoughts and/orpointers >> >> _____ >> Douglas Denault >> doug@safeport.com >> Voice: 301-469-8766 >> Fax: 301-469-0601 >> >List of partition types from Linux fdisk: > >Command (m for help): Partition number (1-10): Hex code (type L to list codes): > 0 Empty a OS/2 Boot Manag 65 Novell Netware a6 OpenBSD > 1 DOS 12-bit FAT b Win95 FAT32 75 PC/IX a7 NEXTSTEP > 2 XENIX root c Win95 FAT32 (LB 80 Old MINIX b7 BSDI fs > 3 XENIX usr e Win95 FAT16 (LB 81 Linux/MINIX b8 BSDI swap > 4 DOS 16-bit <32M f Win95 Extended 82 Linux swap c7 Syrinx > 5 Extended 40 Venix 80286 83 Linux native db CP/M > 6 DOS 16-bit >=32 51 Novell? 85 Linux extended e1 DOS access > 7 OS/2 HPFS 52 Microport 93 Amoeba e3 DOS R/O > 8 AIX 63 GNU HURD 94 Amoeba BBT f2 DOS secondary > 9 AIX bootable 64 Novell Netware a5 BSD/386 ff BBT > >The codes for BSDI are not current. BSDI-4.1 uses (IIRC) 9e. > >Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 8: 3:39 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 08:03:36 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from westhost15.westhost.net (westhost15.westhost.net [216.71.84.69]) by hub.freebsd.org (Postfix) with ESMTP id DD8B337B400 for ; Mon, 1 Jan 2001 08:03:35 -0800 (PST) Received: from beast (h0020af68b314.ne.mediaone.net [24.91.189.27]) by westhost15.westhost.net (8.8.5/8.8.5) with SMTP id KAA25972 for ; Mon, 1 Jan 2001 10:04:48 -0600 From: "Paul A. Howes" To: Subject: Keeping "Stable"... Date: Mon, 1 Jan 2001 11:01:51 -0500 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004E_01C073E2.3E9B9280" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_004E_01C073E2.3E9B9280 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit All- I would like to do a CVSup once a week at an off-peak time, and rebuild the world and several kernels. Also, I would like to be able to rebuild any ports that I have installed, and create packages from them so my other FreeBSD machines can simply pkg_add them. I'm curious if anyone has come up with an automated way of maintaining their FreeBSD system(s), similar to what I have outlined above. The CVSup and building the world is easy enough to launch through a cron job. But the ports can get out of sync with each other so easily, if they're not all rebuilt in the right order, etc. Thanks, Paul ------=_NextPart_000_004E_01C073E2.3E9B9280 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
All-
 
I would like = to do a=20 CVSup once a week at an off-peak time, and rebuild the world and several = kernels.  Also, I would like to be able to rebuild any ports that I = have=20 installed, and create packages from them so my other FreeBSD machines = can simply=20 pkg_add them.
 
I'm curious if anyone has come up with an automated way = of=20 maintaining their FreeBSD system(s), similar to what I have outlined=20 above.  The CVSup and building the world is easy enough to launch = through a=20 cron job.  But the ports can get out of sync with each other so = easily, if=20 they're not all rebuilt in the right order, = etc.
 
Thanks,
Paul
 
------=_NextPart_000_004E_01C073E2.3E9B9280-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 9:37:35 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 09:37:34 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 14BD937B400 for ; Mon, 1 Jan 2001 09:37:33 -0800 (PST) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA30946; Mon, 1 Jan 2001 09:37:21 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200101011737.JAA30946@gndrsh.dnsmgr.net> Subject: Re: Boot ManagerQuestions In-Reply-To: from Chris BeHanna at "Dec 30, 2000 05:23:45 pm" To: behanna@zbzoom.net Date: Mon, 1 Jan 2001 09:37:20 -0800 (PST) Cc: stable@FreeBSD.ORG (FreeBSD-Stable) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 29 Dec 2000 doug@safeport.com wrote: > > > [...snip of questions I leave for others...] > > > > Does anyone know the MS/IBM approved codes for the various types > > > > 6 = DOS FAT16 > > ? = DOS FAT32 > > FAT32 and FAT16 are both 6. Wrong. 4 is DOS FAT 16 < 32mb 6 is DOS FAT 16 > 32mb 11 is DOS/Win9X FAT32 12 is DOS/Win9X FAT32 LBA (rarely actually used) See /usr/src/sbin/i386/fdisk.c for a good list. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 11:33:38 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 11:33:36 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 15B7A37B400 for ; Mon, 1 Jan 2001 11:33:36 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 89231574D5; Mon, 1 Jan 2001 13:34:11 -0600 (CST) Date: Mon, 1 Jan 2001 13:34:11 -0600 From: "Michael C . Wu" To: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support Message-ID: <20010101133411.B51028@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , Roman Shterenzon , freebsd-stable@FreeBSD.ORG References: <200012282317.PAA04405@spammie.svbug.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 roman@harmonic.co.il on Mon, Jan 01, 2001 at 12:09:30PM +0200 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 01, 2001 at 12:09:30PM +0200, Roman Shterenzon scribbled: | On Thu, 28 Dec 2000 opentrax@email.com wrote: | > On 28 Dec, Gerald Pfeifer wrote: | > > Having been hit by this today, how about MFCing the following change? | > > | > > revision 1.289 | > > date: 2000/11/14 01:11:13; author: jkh; state: Exp; lines: +4 -1 | > > In the year 2000, I think it's perfectly reasonable to include audio | > > support by default in GENERIC. | > > | > I can't answer for JKH or others but audio has had a history | > of problems, especially durning the boot-up probe stage. | > Problems such that it might lock up the machine under | > certain conditions. Perhaps this is the reason sound may | > never make it into GENERIC. I do not recall ever having such trouble with newpcm, nor has newpcm been troublesome for people. If newpcm does not probe, the boot process continues on. There is no "probe problem." JMJr: Stop spreading baseless, false information like this, please. | Yes, I really hope that it doesn't make it into the GENERIC. | GENERIC kernel should provide fully functional and stable machine without | bells and whistles. Sound is a luxury. "Fully functional" for a desktop implies a working sound card too. This is one of of those things that does not really matter very much. A good server admin will recompile and customize his kernel. And a desktop user probably does not know how to compile a kernel. Are you telling me that, in your consultancy, you just keep GENERIC? There is no need for this bikeshed. Whether pcm is included in GEERIC or not does not really hurt anybody either way. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 14:58:29 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 14:58:25 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id EFC4037B400 for ; Mon, 1 Jan 2001 14:58:22 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 1093E6A913; Tue, 2 Jan 2001 09:28:20 +1030 (CST) Date: Tue, 2 Jan 2001 09:28:20 +1030 From: Greg Lehey To: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG Subject: Re: vinum malfunction! Message-ID: <20010102092819.K44043@wantadilla.lemis.com> References: <20001231101426.K99806@wantadilla.lemis.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 roman@harmonic.co.il on Mon, Jan 01, 2001 at 12:32:22PM +0200 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 1 January 2001 at 12:32:22 +0200, Roman Shterenzon wrote: > On Sun, 31 Dec 2000, Greg Lehey wrote: > >> [Format recovered--see http://www.lemis.com/email/email-format.html] >> >> Please limit your lines to < 80 characters. >> >> On Saturday, 30 December 2000 at 19:00:27 +0100, O. Hartmann wrote: >>> Dear Sirs. >>> Today I run a make world and compiled a new kernel for our server, >>> which uses a vinum RAID 0. At the same time I reconfigured the >>> kernel to use SC console driver and VESA instead of VT console. >>> >>> Since the new kernel got compiled loading of vinum fails! I do not >>> know why, I removed all kernel changes, but it does not help. >>> >>> Does anyone know why? >> >> Of course not. You haven't given *any* details. >> >> Take a look at http://www.vinumvm.org/vinum/how-to-debug.html and give >> some information, and I'll probably be able to help. > > I've submitted kern/22021 which was left untouched, it has all the needed > details. Please don't jump to conclusions. O. Hartmann has, as I mentioned, given *no* information. If you can find the cause of the problem from what he has done, please go ahead and do so. All I can see here is that he is talking about RAID-0, while the problem you failed to describe in 22021 occurs only with RAID-5. kern/22021 was closed one day after it was issued. To quote: Greg Lehey, 17 October 2000 I'm sorry, this PR is so completely mutilated that I can't read it. It appears to have been sent with quoted-printable, but without declaring the fact. As a result, the information is almost completely illegible. It's not so completely mutilated, however, that I don't note that it includes dmesg and kernel config information, information that I specifically ask *not* to include in problem reports. I'm closing this PR because it'll be easier to resubmit it than to fix it. Please read http://www.vinumvm.org/vinum/how-to-debug.html and http://www.lemis.com/email.html before doing so. Since you mention this PR, I suppose I should amplify on this comment. First, it is by *far* the most illegible PR I have ever seen. For example: #39 0xc0236a0d in trap_pfault (frame=3D0xc0276a70, usermode=3D0, eva=3D84) at ../../i386/i386/trap.c:820 #40 0xc023660b in trap (frame=3D{tf_fs =3D -1071185904, tf_es =3D -10723655= 52,=20 tf_ds =3D 7077904, tf_edi =3D -1049722848, tf_esi =3D -1049722880,=20 tf_ebp =3D -1071158580, tf_isp =3D -1071158628, tf_ebx =3D -103960512= 0,=20 tf_edx =3D 0, tf_ecx =3D 90505217, tf_eax =3D -7113793, tf_trapno =3D= 12,=20 tf_err =3D 2, tf_eip =3D -1051657113, tf_cs =3D 8, tf_eflags =3D 6611= 8,=20 tf_esp =3D -1049722848, tf_ss =3D -1051996160}) at ../../i386/i386/tr= ap.c:426 #41 0xc150fc67 in ?? () #42 0xc0178d6b in biodone (bp=3D0xc16e8020) at ../../kern/vfs_bio.c:2637 #43 0xc0126bb9 in dadone (periph=3D0xc14ca700, done_ccb=3D0xc1658c00) at ../../cam/scsi/scsi_da.c:1246 Apart from the fact that it's barely legible, this also shows: 1. You did a backtrace without loading Vinum symbols. 2. It's related to a known, but rare, RAID-5 problem which I am trying to get information on. You don't mention that you resubmitted this PR as 22103. Despite my requests, 1. You insisted on including the config file and dmesg, which just bloat the PR and make it more difficult to read. 2. The backtrace still does not include Vinum symbols, making it pretty useless. 3. It includes (without comment) a mail exchange with Andy Newman, which have been twice mutilated, once before I received the message, once after. After fighting my way through this PR, I don't have any additional information. Dealing with this kind of PR is an absolute pain. It's bloated, illegible, full of irrelevant information and lacking the information I need. It is, however, one of the few cases I've seen of a particular buffer header corruption which occurs only in RAID-5, and I would like to fix it. If you want to help, instead of sending "me too" messages about what is obviously a completely different problem, help me find the problem you're having. 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-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 15: 4: 1 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 15:03:58 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id CFCCD37B400 for ; Mon, 1 Jan 2001 15:03:57 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id wjmsaaaa for ; Tue, 2 Jan 2001 10:12:00 +1100 Message-ID: <3A510D08.B3A3042@quake.com.au> Date: Tue, 02 Jan 2001 10:04:40 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: stable@FreeBSD.ORG Subject: Re: slow NAT ? References: <4.2.2.20001231124602.01d21878@marble.sentex.net> <4.2.2.20010101084935.01e47880@marble.sentex.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Tancsa wrote: > > At 12:25 PM 1/1/2001 +0200, Roman Shterenzon wrote: > >On Sun, 31 Dec 2000, Mike Tancsa wrote: > > > > > > > > I upgraded my home firewall today to sources as of last night and noticed > > > that traffic via NAT is rather slow. For example, an ftp from a machine > > > being nat'd I guess about 300Kbps. From the FreeBSD box, I get about 1Mb > > > on my DSL connection. If I use squid or a proper proxy, its not an > > > issue. This is both with the built in NAT on PPP and NATD by itself. Any > > > ideas as to how to track this down ? > > > 4.2-STABLE FreeBSD 4.2-STABLE #0: Sat Dec 30 09:37:21 EST 2000 > > > Its only a CPU: Pentium/P55C (167.05-MHz 586-class CPU) with 96M of RAM. > > > >Was it that slow before the upgrade? > >As a workaround you can use ipnat which performs NAT in kernel-space > >rather than in user-space (as libalias does). > > It was somewhat slower, but not this bad. However, I dont have any > benchmarks from before to measure the difference. I will try IPNAT to see > if that helps at all. It seems strange to me that it would be going noticeably slower... I mean sure its going to slow it down a little, but so is every other sharing type program... I use NATd on a P166 with 34mb ram and NetGear 10/100 cards, If anything its no different speeds from any other method, I have a max downstream of 400kbs which I achieve to most places most of the time... Basically NATd dosent seem to effect the speed much at all... I am using 4.0 but if anything NATd should be better in 4.2 so it seems strange, maybe there is a problem some place else? Good Luck! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 15:20: 9 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 15:20:06 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from awww.jeah.net (awww.jeah.net [216.111.239.130]) by hub.freebsd.org (Postfix) with ESMTP id 6057737B400 for ; Mon, 1 Jan 2001 15:20:02 -0800 (PST) Received: from localhost (root@localhost) by awww.jeah.net (8.11.1/8.11.0) with ESMTP id f01NKfM08821 for ; Mon, 1 Jan 2001 17:20:41 -0600 (CST) (envelope-from root@jeah.net) Date: Mon, 1 Jan 2001 17:20:41 -0600 (CST) From: JEAH Communications Administration To: stable@freebsd.org Subject: inetd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a telnet/ftp flood today. Isn't there a way to tell inetd to only allow like 25 telnet/ftp connections at a time? There were over 500 loaded.. Systems Administration ** root@JEAH.net JEAH Communications ** www.JEAH.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 15:42:40 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 15:42:38 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-99.zoominternet.net [24.154.28.99]) by hub.freebsd.org (Postfix) with ESMTP id C67D437B402 for ; Mon, 1 Jan 2001 15:42:37 -0800 (PST) Received: from browning.pennasoft.com (browning [192.168.168.11]) by topperwein.dyndns.org (8.11.1/8.11.1) with ESMTP id f01NhYP48058 for ; Mon, 1 Jan 2001 18:43:39 -0500 (EST) (envelope-from behanna@zbzoom.net) Date: Mon, 1 Jan 2001 18:43:48 -0500 (EST) From: Chris BeHanna Sender: behanna@browning.pennasoft.com Reply-To: behanna@zbzoom.net To: FreeBSD-Stable Subject: Re: Boot ManagerQuestions In-Reply-To: <200101011737.JAA30946@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Jan 2001, Rodney W. Grimes wrote: > > On Fri, 29 Dec 2000 doug@safeport.com wrote: > > > > > [...snip of questions I leave for others...] > > > > > > Does anyone know the MS/IBM approved codes for the various types > > > > > > 6 = DOS FAT16 > > > ? = DOS FAT32 > > > > FAT32 and FAT16 are both 6. > > Wrong. 4 is DOS FAT 16 < 32mb > 6 is DOS FAT 16 > 32mb > 11 is DOS/Win9X FAT32 > 12 is DOS/Win9X FAT32 LBA (rarely actually used) When I partitioned the drive on the box that I'm using at this very minute, I gave type 6 to my DOS partitions. Those partitions currently house FAT32 filesystems. IOW, in practice, I doubt it matters if you assign 6 or 11 to a DOS partition. -- Chris BeHanna Software Engineer behanna@bogus.zbzoom.net Remove "bogus" before responding. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 16: 1: 5 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 16:01:03 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from awww.jeah.net (awww.jeah.net [216.111.239.130]) by hub.freebsd.org (Postfix) with ESMTP id C526D37B400 for ; Mon, 1 Jan 2001 16:01:02 -0800 (PST) Received: from localhost (chris@localhost) by awww.jeah.net (8.11.1/8.11.0) with ESMTP id f0201ka09575; Mon, 1 Jan 2001 18:01:46 -0600 (CST) (envelope-from chris@jeah.net) Date: Mon, 1 Jan 2001 18:01:45 -0600 (CST) From: Chris Byrnes To: Alessandro de Manzano Cc: FreeBSD Subject: Re: inetd In-Reply-To: <20010102005750.A7125@libero.sunshine.ale> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I should really "man" first. I'm surprised that defaults aren't lower. I don't know why a machine would need unlimited connections by default. I'm doing 'inetd -C 64 -R 128 -wW' from now on. CB Chris Byrnes JEAH Communications (Direct) 608-256-6167 (Toll-Free) 866-299-5324 http://www.JEAH.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 16:10: 5 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 16:10:01 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay4.inwind.it (relay4.inwind.it [212.141.53.75]) by hub.freebsd.org (Postfix) with ESMTP id 7DD0C37B400 for ; Mon, 1 Jan 2001 16:10:01 -0800 (PST) Received: from bartequi.ottodomain.org (62.98.170.150) by relay4.inwind.it (5.1.056) id 3A4B0A72000B22DC; Tue, 2 Jan 2001 01:09:51 +0100 From: Salvo Bartolotta Date: Tue, 02 Jan 2001 00:11:52 GMT Message-ID: <20010102.115200@bartequi.ottodomain.org> Subject: Re: inetd To: JEAH Communications Administration Cc: freebsd-stable@freebsd.org In-Reply-To: References: X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 1/2/01, 12:20:41 AM, JEAH Communications Administration=20 wrote regarding inetd: > I had a telnet/ftp flood today. Isn't there a way to tell inetd to=20 only > allow like 25 telnet/ftp connections at a time? There were over 500 > loaded.. The above question is probably more suitable for... -questions. Have you tried the inetd(8) options (eg -c, -C, ...) ? HTH, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 17:51:38 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 17:51:32 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id ACFDC37B402 for ; Mon, 1 Jan 2001 17:51:31 -0800 (PST) Received: (qmail 29723 invoked by uid 0); 2 Jan 2001 01:51:29 -0000 Received: from tk212017108240.univie.teleweb.at (HELO ntaflos.gmx.net) (212.17.108.240) by mail.gmx.net (mail01) with SMTP; 2 Jan 2001 01:51:29 -0000 Message-Id: <5.0.2.1.0.20010102024319.00a4ea40@pop.gmx.net> X-Sender: 4037158@pop.gmx.net X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 02 Jan 2001 02:51:25 +0100 To: Ty From: Andreas Ntaflos Subject: Re: sblive installed, but no sound in 4.2 Cc: questions@freebsd.org, stable@freebsd.org In-Reply-To: <3A50E357.4090700@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi everything you did seems right, i have an sb live working under fbsd 4.2. maybe it helps if you do a MAKEDEV all in /dev after rebuilding the kernel (as this should always be done after building a new kernel), before you do a MAKEDEV snd0. that's the only step i could imagine you forgot, as everything else is what i did too, and my sound works very well under 4.2 regards Andreas Ntaflos At 12:06 01.01.2001 -0800, you wrote: >Hello, > >I believe I have my sound blaster live correctly installed under feebsd >4.2 yet I can't hear any audio. I do have the mixer settings up. >i recompiled the kernel with >device pcm >(and i have device pci in already) > >then rebooted and did a >cd /dev >./MAKDEV snd0 > >cat /dev/sndstat > >shows: > >FreeBSD Audio Driver (newpcm) Dec 31 2000 12:36:40 >Installed devices: >pcm0: at io 0xd000 irq 10 (4p/3r channels duplex) > >Mixer shows > >Mixer vol is currently set to 62:62 >Mixer pcm is currently set to 100:100 >Mixer speaker is currently set to 100:100 >Mixer line is currently set to 75:75 >Mixer mic is currently set to 80:80 >Mixer cd is currently set to 69:69 >Mixer rec is currently set to 0:0 >Mixer line1 is currently set to 75:75 >Mixer phin is currently set to 69:69 >Mixer phout is currently set to 97:97 >Mixer video is currently set to 100:100bash-2.04# cat /dev/sndstat > >help, is there something i'm missing here? I've put the volume to 100% on >everything including speakers and I don't hear a peep, no matter what type >of audio I attempt to play. > >thank you! > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 18:22:46 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 18:22:44 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 07C5E37B400 for ; Mon, 1 Jan 2001 18:22:39 -0800 (PST) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id SAA31742; Mon, 1 Jan 2001 18:22:35 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200101020222.SAA31742@gndrsh.dnsmgr.net> Subject: Re: Boot ManagerQuestions In-Reply-To: from Chris BeHanna at "Jan 1, 2001 06:43:48 pm" To: behanna@zbzoom.net Date: Mon, 1 Jan 2001 18:22:34 -0800 (PST) Cc: stable@FreeBSD.ORG (FreeBSD-Stable) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 1 Jan 2001, Rodney W. Grimes wrote: > > > > On Fri, 29 Dec 2000 doug@safeport.com wrote: > > > > > > > [...snip of questions I leave for others...] > > > > > > > > Does anyone know the MS/IBM approved codes for the various types > > > > > > > > 6 = DOS FAT16 > > > > ? = DOS FAT32 > > > > > > FAT32 and FAT16 are both 6. > > > > Wrong. 4 is DOS FAT 16 < 32mb > > 6 is DOS FAT 16 > 32mb > > 11 is DOS/Win9X FAT32 > > 12 is DOS/Win9X FAT32 LBA (rarely actually used) > > When I partitioned the drive on the box that I'm using at this > very minute, I gave type 6 to my DOS partitions. Those partitions > currently house FAT32 filesystems. Your sure it still is type 6 after your ran fat32 format??? > IOW, in practice, I doubt it matters if you assign 6 or 11 to a > DOS partition. I am not sure on that, I've never seen a type 6 fat32, but then I have never purposefully tried to create one either. Win9x OSr2 and later fdisk creates them as type 11 if you answer yes to the Enable large disk question, if they are larger than some magic number, otherwise it just creates type 6 partitions. The magic size is either 504MB or 2G, can't recall right now. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 19:44:58 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 19:44:57 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.gelrevision.nl (mail.gelrevision.nl [195.86.58.10]) by hub.freebsd.org (Postfix) with ESMTP id CC3D537B400 for ; Mon, 1 Jan 2001 19:44:56 -0800 (PST) Received: from oT.An'Era [195.86.231.176] by mail.gelrevision.nl with ESMTP (SMTPD32-6.00) id AE0CB03E0282; Tue, 02 Jan 2001 04:42:04 +0100 Date: Tue, 2 Jan 2001 04:44:35 +0100 (CET) From: Maarten van Schie Sender: To: Subject: Re: Boot ManagerQuestions In-Reply-To: <200101020222.SAA31742@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You guys talk about a 'duel boot'. But as far as I go a duel is an opposition. It should be 'dual' caused by the composition. Maarten. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 20: 3:11 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 20:03:08 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 47CF837B400 for ; Mon, 1 Jan 2001 20:03:08 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id olmsaaaa for ; Tue, 2 Jan 2001 15:11:07 +1100 Message-ID: <3A515318.EBF64EED@quake.com.au> Date: Tue, 02 Jan 2001 15:03:36 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: stable@FreeBSD.ORG Subject: Re: Boot ManagerQuestions References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maarten van Schie wrote: > > You guys talk about a 'duel boot'. But as far as I go a duel is an > opposition. It should be 'dual' caused by the composition. That might be a nice situation, but as soon as there is more than one O/S on a system they are both fighting for control, take as a prime example the system clock... So I think a duel boot is by definition a better description of for what we are talking about! Happy knit picking! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 20:15:55 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 20:15:53 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.gelrevision.nl (mail.gelrevision.nl [195.86.58.10]) by hub.freebsd.org (Postfix) with ESMTP id 84B2537B402 for ; Mon, 1 Jan 2001 20:15:52 -0800 (PST) Received: from oT.An'Era [195.86.231.176] by mail.gelrevision.nl with ESMTP (SMTPD32-6.00) id A54D8A2901CE; Tue, 02 Jan 2001 05:13:01 +0100 Date: Tue, 2 Jan 2001 05:15:33 +0100 (CET) From: Maarten van Schie Sender: To: Kal Torak Cc: Subject: Re: Boot ManagerQuestions In-Reply-To: <3A515318.EBF64EED@quake.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Jan 2001, Kal Torak wrote: > Maarten van Schie wrote: > > > > You guys talk about a 'duel boot'. But as far as I go a duel is an > > opposition. It should be 'dual' caused by the composition. > > > That might be a nice situation, but as soon as there is more than one > O/S on a system they are both fighting for control, take as a prime > example the system clock... > > So I think a duel boot is by definition a better description of > for what we are talking about! I never realy encountered problems confronting Windows with Linux or Windows with FreeBSD, so that's not realy true. If others do I reccon they force them to(?). Maarten. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 21: 4:20 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 21:04:18 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 0C36E37B402 for ; Mon, 1 Jan 2001 21:04:18 -0800 (PST) Received: (qmail 30123 invoked from network); 2 Jan 2001 05:02:54 -0000 Received: from acs-24-154-25-123.zoominternet.net (HELO cvzoom.net) (24.154.25.123) by scully.zoominternet.net with SMTP; 2 Jan 2001 05:02:54 -0000 Sender: dmmiller@FreeBSD.ORG Message-ID: <3A516151.541764AB@cvzoom.net> Date: Tue, 02 Jan 2001 00:04:17 -0500 From: Donn Miller X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Michael C . Wu" Cc: Roman Shterenzon , freebsd-stable@FreeBSD.ORG Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support References: <200012282317.PAA04405@spammie.svbug.com> <20010101133411.B51028@peorth.iteration.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Michael C . Wu" wrote: > "Fully functional" for a desktop implies a working sound card too. > This is one of of those things that does not really matter very much. > A good server admin will recompile and customize his kernel. > And a desktop user probably does not know how to compile a kernel. > Are you telling me that, in your consultancy, you just keep GENERIC? > > There is no need for this bikeshed. Whether pcm is included in GEERIC > or not does not really hurt anybody either way. FreeBSD is most often used as a server, not a desktop. Why exactly is sound needed for a first install? If nothing else, PCM could be loaded via a kernel module. Optional stuff usually should not be statically linked into the kernel, but should be placed in KLD's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 21:53:51 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 21:53:49 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id B784037B400 for ; Mon, 1 Jan 2001 21:53:48 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id jmmsaaaa for ; Tue, 2 Jan 2001 17:01:47 +1100 Message-ID: <3A516D09.648AE420@quake.com.au> Date: Tue, 02 Jan 2001 16:54:17 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support References: <200012282317.PAA04405@spammie.svbug.com> <20010101133411.B51028@peorth.iteration.net> <3A516151.541764AB@cvzoom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller wrote: > > "Michael C . Wu" wrote: > > > "Fully functional" for a desktop implies a working sound card too. > > This is one of of those things that does not really matter very much. > > A good server admin will recompile and customize his kernel. > > And a desktop user probably does not know how to compile a kernel. > > Are you telling me that, in your consultancy, you just keep GENERIC? > > > > There is no need for this bikeshed. Whether pcm is included in GEERIC > > or not does not really hurt anybody either way. > > FreeBSD is most often used as a server, not a desktop. Why exactly is > sound needed for a first install? If nothing else, PCM could be loaded > via a kernel module. Optional stuff usually should not be statically > linked into the kernel, but should be placed in KLD's. While this is true, the GENERIC kernel is supposed to support as much hardware "out of the box" as possible, so a user can install and not have to worry about setting up devices... Why should FreeBSD be used only as a server? There are plenty of linux desktops around, and FreeBSD can be used just as well, even better maybe! I dont see why sound shouldnt be in the GENERIC kernel, since if we decide what should be "generic" based on what a server will use then maybe we should take out mouse and USB support as well? What about all these ata devices? Any self respecting server would use SCSI! As you can see, that is a bit extreme... But you would have to say that sound is pretty much "generic" these days, so really belongs in the GENERIC kernel... Just my 2c, Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 21:57:57 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 21:57:54 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 561B237B402 for ; Mon, 1 Jan 2001 21:57:54 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id mmmsaaaa for ; Tue, 2 Jan 2001 17:05:56 +1100 Message-ID: <3A516E01.6A17FE3B@quake.com.au> Date: Tue, 02 Jan 2001 16:58:25 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: stable@FreeBSD.ORG Subject: Re: Boot ManagerQuestions References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maarten van Schie wrote: > > On Tue, 2 Jan 2001, Kal Torak wrote: > > > Maarten van Schie wrote: > > > > > > You guys talk about a 'duel boot'. But as far as I go a duel is an > > > opposition. It should be 'dual' caused by the composition. > > > > > > That might be a nice situation, but as soon as there is more than one > > O/S on a system they are both fighting for control, take as a prime > > example the system clock... > > > > So I think a duel boot is by definition a better description of > > for what we are talking about! > > I never realy encountered problems confronting Windows with Linux or > Windows with FreeBSD, so that's not realy true. If others do I reccon they > force them to(?). Obviously you have never tried to have a system use UTC... Any playing with BIOS settings would eventually break things in one system (eg. PnP O/S Installed, CardBuss mode, various other resource settings) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 21:59: 3 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 21:59:00 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id A6FAD37B400 for ; Mon, 1 Jan 2001 21:59:00 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id B54A4574E3; Mon, 1 Jan 2001 23:59:36 -0600 (CST) Date: Mon, 1 Jan 2001 23:59:36 -0600 From: "Michael C . Wu" To: Donn Miller Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support Message-ID: <20010101235936.A54831@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , Donn Miller , freebsd-stable@FreeBSD.ORG References: <200012282317.PAA04405@spammie.svbug.com> <20010101133411.B51028@peorth.iteration.net> <3A516151.541764AB@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A516151.541764AB@cvzoom.net>; from dmmiller@cvzoom.net on Tue, Jan 02, 2001 at 12:04:17AM -0500 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 12:04:17AM -0500, Donn Miller scribbled: | "Michael C . Wu" wrote: | FreeBSD is most often used as a server, not a desktop. Why exactly is | sound needed for a first install? If nothing else, PCM could be loaded | via a kernel module. Optional stuff usually should not be statically | linked into the kernel, but should be placed in KLD's. No one rebutted against your point. I am certain that I did not. All I pointed out was that this is a quite non-crucial discussion. Bikeshed. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 22: 0:52 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 22:00:48 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.ticonet.co.cr (mail.ticonet.co.cr [196.40.4.5]) by hub.freebsd.org (Postfix) with ESMTP id A7FC737B6B1; Mon, 1 Jan 2001 22:00:19 -0800 (PST) Received: from Popeye [196.40.53.184] by mail.ticonet.co.cr (SMTPD32-6.05) id AA4327B01DA; Mon, 01 Jan 2001 22:52:51 +0000 To: Happy@FreeBSD.ORG, New@FreeBSD.ORG, !!@Year.FreeBSD.ORG From: Oldies@FreeBSD.ORG, Online@FreeBSD.ORG, Casino@FreeBSD.ORG Subject: 01-01-2001 Date: Mon, 01 Jan 2001 23:59:16 -0600 Message-Id: <36892.999497453704000.238432@localhost> MIME-Version: 1.0 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oldies Online Casino - Happy New Year!!!

Oldies Online Casino
Would like to welcome you and your family a Happy New Year!

We Would also like to offer ALL NEW & EXISTING Members a
Holiday 25% Bonus
Oldies Online Casino offers Free no download Flash Internet
gambling, games include craps, keno, slots, video poker,
roulette and blackjack in real time. Play for fun or cash!
http://www.oldiesonlinecasino.com

to unsubscribe click here

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 22: 3:17 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 22:03:15 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from saturn.home.ben.com (c1058885-a.bvrtn1.or.home.com [24.12.186.106]) by hub.freebsd.org (Postfix) with ESMTP id A93FE37B400 for ; Mon, 1 Jan 2001 22:03:14 -0800 (PST) Received: (from bjj@localhost) by saturn.home.ben.com (8.11.1/8.9.3) id f0263A882147; Mon, 1 Jan 2001 22:03:10 -0800 (PST) From: Ben Jackson Message-Id: <200101020603.f0263A882147@saturn.home.ben.com> Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support In-Reply-To: <3A516D09.648AE420@quake.com.au> from Kal Torak at "Jan 2, 2001 04:54:17 pm" To: Kal Torak Date: Mon, 1 Jan 2001 22:03:10 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Donn Miller wrote: > While this is true, the GENERIC kernel is supposed to support as much > hardware "out of the box" as possible, so a user can install and not > have to worry about setting up devices... So a user can *install* and not have to worry about setting up devices. You don't need a soundcard to do an install. Once you've done the installation you can build a kernel which supports your soundcard. If it's causing problems on installs maybe it should be disabled by default, even if it is built into the kernel. --Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 1 23:45:28 2001 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 1 23:45:25 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from gw-nl1.origin-it.com (gw-nl1.origin-it.com [193.79.128.34]) by hub.freebsd.org (Postfix) with ESMTP id E441737B400 for ; Mon, 1 Jan 2001 23:45:24 -0800 (PST) Received: from mail.de.origin-it.com (localhost.origin-it.com [127.0.0.1]) by gw-nl1.origin-it.com with ESMTP id IAA00207; Tue, 2 Jan 2001 08:45:22 +0100 (MET) (envelope-from Helge.Oldach@de.origin-it.com) Received: from smtprelay-de1.origin-it.com(172.16.188.53) by gw-nl1.origin-it.com via mwrap (4.0a) id xma000202; Tue, 2 Jan 01 08:45:23 +0100 Received: from mailhub.de.origin-it.com (mailhub.de.origin-it.com [172.16.189.20]) by mail.de.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id IAA01382; Tue, 2 Jan 2001 08:45:22 +0100 (MET) Received: from galaxy.de.cp.philips.com (galaxy.de.cp.philips.com [130.143.166.29]) by mailhub.de.origin-it.com (8.11.1/8.11.1/hmo23oct00) with ESMTP id f027jKY86727; Tue, 2 Jan 2001 08:45:21 +0100 (CET) (envelope-from Helge.Oldach@de.origin-it.com) Received: (from hmo@localhost) by galaxy.de.cp.philips.com (8.9.3/8.9.3/hmo14aug98) id IAA24741; Tue, 2 Jan 2001 08:45:19 +0100 (MET) Message-Id: <200101020745.IAA24741@galaxy.de.cp.philips.com> Subject: Re: 4.2-stable, ports/packages in XF86 4.0.2 In-Reply-To: <023d01c0736c$e13ff060$931576d8@inethouston.net> from "David W. Chapman Jr." at "Dec 31, 2000 3: 1:43 pm" To: dwcjr@inethouston.net (David W. Chapman Jr.) Date: Tue, 2 Jan 2001 08:45:19 +0100 (MET) Cc: kaltorak@quake.com.au, freebsd-stable@freebsd.org From: Helge Oldach X-Address: Atos Origin, Billstrasse 80, D-20539 Hamburg, Germany X-Phone: +49 40 7886 464, Fax: +49 40 7886 235, Mobile: +49 172 4515513 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David W. Chapman Jr.: >The problem is netscape itself, since it comes in binary format, anyone who >ports it doesn't have a choice into which format, I believe the bsdi version >of netscape is elf, but I'm not totally sure. It is, and the BSDI binary runs just smoothly on FreeBSD. The only issue is that the latest version is not 4.76 but 4.75. I am not sure whether this is because the BSDI version was not suffering the bug that made Netscape to release 4.76, or whether they just dropped BSDI support. Helge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 0:28:46 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 00:28:44 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 6055C37B400 for ; Tue, 2 Jan 2001 00:28:44 -0800 (PST) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id BAA07615; Tue, 2 Jan 2001 01:28:40 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200101020828.BAA07615@freeway.dcfinc.com> Subject: Re: alternative network media In-Reply-To: from Roman Shterenzon at "Jan 1, 1 12:28:32 pm" To: roman@harmonic.co.il (Roman Shterenzon) Date: Tue, 2 Jan 2001 01:28:40 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: chad@freeway.dcfinc.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Roman Shterenzon wrote: > On Sun, 31 Dec 2000, Chad R. Larson wrote: > > Any Firewire networking support? The 400 Mbit oughta screem. > > Just a side note; what is the bandwidth of your harddisk? :) Dunno yet. I tried to run SpinRite 5.0 against it, but there was some problem with SpinRite recognizing the hard drive partitions built under Win2K Pro. Sony supplied a software package (SmartConnect) that will permit file and printer sharing between to systems over a Firewire connection. Being able to interface with it seems useful. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 0:48:22 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 00:48:19 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id A207F37B400 for ; Tue, 2 Jan 2001 00:48:18 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id KAA30418; Tue, 2 Jan 2001 10:46:26 +0200 To: Greg Lehey Subject: Re: vinum malfunction! Message-ID: <978425185.3a519561dbcdb@webmail.harmonic.co.il> Date: Tue, 02 Jan 2001 10:46:25 +0200 (IST) From: Roman Shterenzon Cc: Roman Shterenzon , freebsd-stable@FreeBSD.ORG References: <20001231101426.K99806@wantadilla.lemis.com> <20010102092819.K44043@wantadilla.lemis.com> In-Reply-To: <20010102092819.K44043@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Greg Lehey : > > I've submitted kern/22021 which was left untouched, it has all the > needed > > details. > > You don't mention that you resubmitted this PR as 22103. Despite my > requests, my fault, I meant 22103 indeed, and not 22021 which was closed. > 1. You insisted on including the config file and dmesg, which > just bloat the PR and make it more difficult to read. yes I did. sed(1) is your friend. > 2. The backtrace still does not include Vinum symbols, making it > pretty useless. To the very least it's not true. Please check again http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22103 During symbol reading, inner block (0xc1505000-0xc150500a) not inside outer block (0xc150bc0c-0xc150c3c2). During symbol reading, block at 0xc15050d4 out of order. #5 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../dev/vinum/vinuminterrupt.c:199 #6 0xc0178d6b in biodone (bp=0xc16e6420) at ../../kern/vfs_bio.c:2637 as you see, frame #5 is from vinum module, and symbols are included. > 3. It includes (without comment) a mail exchange with Andy Newman, > which have been twice mutilated, once before I received the > message, once after. This is completely irrelevant. > After fighting my way through this PR, I don't have any additional > information. You fighted your way too fast. > Dealing with this kind of PR is an absolute pain. It's bloated, > illegible, full of irrelevant information and lacking the information > I need. It is, however, one of the few cases I've seen of a ..or any other reason that prevents you from working on it. I haven't heard from you since the last time I updated te PR with the kdb session which had symbols. > particular buffer header corruption which occurs only in RAID-5, and I > would like to fix it. If you want to help, instead of sending "me > too" messages about what is obviously a completely different problem, > help me find the problem you're having. I'm terribly sorry, but I won't be able to assist you any further. The machine in question uses vinum raid-1 now, and is going to receive Mylex very soon. vinum RAID-5 is dangerous, shouldn't be used in sensitive environments, and it cost me much health. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 1: 2:49 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 01:02:46 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 1749C37B400 for ; Tue, 2 Jan 2001 01:02:44 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 9719A6A911; Tue, 2 Jan 2001 19:32:41 +1030 (CST) Date: Tue, 2 Jan 2001 19:32:41 +1030 From: Greg Lehey To: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG Subject: Re: vinum malfunction! Message-ID: <20010102193241.C40453@wantadilla.lemis.com> References: <20001231101426.K99806@wantadilla.lemis.com> <20010102092819.K44043@wantadilla.lemis.com> <978425185.3a519561dbcdb@webmail.harmonic.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <978425185.3a519561dbcdb@webmail.harmonic.co.il>; from roman@harmonic.co.il on Tue, Jan 02, 2001 at 10:46:25AM +0200 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] On Tuesday, 2 January 2001 at 10:46:25 +0200, Roman Shterenzon wrote: > Quoting Greg Lehey : > >>> I've submitted kern/22021 which was left untouched, it has all the >>> needed details. >> >> 1. You insisted on including the config file and dmesg, which >> just bloat the PR and make it more difficult to read. > > yes I did. sed(1) is your friend. OK, take sed(1) and a few other tools, and write a usable problem report. It's just plain impolite to expect people who are working for free to endure this kind of crap. In fact, even if you were paying them, it's still impolite. >> 2. The backtrace still does not include Vinum symbols, making it >> pretty useless. > > To the very least it's not true. > Please check again http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22103 There's one there which is missing symbols. In a total of 30 printed pages of mainly irrelevant text, I might have missed something. >> 3. It includes (without comment) a mail exchange with Andy Newman, >> which have been twice mutilated, once before I received the >> message, once after. > > This is completely irrelevant. Precisely. Please don't include irrelevant information. >> Dealing with this kind of PR is an absolute pain. It's bloated, >> illegible, full of irrelevant information and lacking the information >> I need. It is, however, one of the few cases I've seen of a > > ..or any other reason that prevents you from working on it. Sorry, what are you trying to say? > vinum RAID-5 is dangerous, shouldn't be used in sensitive > environments, and it cost me much health. This kind of blanket statement detracts from anything useful you might have to say. Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html 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-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 1:19:46 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 01:19:43 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id 56DA037B400 for ; Tue, 2 Jan 2001 01:19:42 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id LAA30440; Tue, 2 Jan 2001 11:18:00 +0200 To: Greg Lehey Subject: Re: vinum malfunction! Message-ID: <978427080.3a519cc850a45@webmail.harmonic.co.il> Date: Tue, 02 Jan 2001 11:18:00 +0200 (IST) From: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG References: <20001231101426.K99806@wantadilla.lemis.com> <20010102092819.K44043@wantadilla.lemis.com> <978425185.3a519561dbcdb@webmail.harmonic.co.il> <20010102193241.C40453@wantadilla.lemis.com> In-Reply-To: <20010102193241.C40453@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Greg Lehey : > >> 2. The backtrace still does not include Vinum symbols, making it > >> pretty useless. > > > > To the very least it's not true. > > Please check again http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22103 > > There's one there which is missing symbols. In a total of 30 printed > pages of mainly irrelevant text, I might have missed something. > > >> 3. It includes (without comment) a mail exchange with Andy Newman, > >> which have been twice mutilated, once before I received the > >> message, once after. > > > > This is completely irrelevant. > > Precisely. Please don't include irrelevant information. > > >> Dealing with this kind of PR is an absolute pain. It's bloated, > >> illegible, full of irrelevant information and lacking the information > >> I need. It is, however, one of the few cases I've seen of a > > > > ..or any other reason that prevents you from working on it. > > Sorry, what are you trying to say? > > > vinum RAID-5 is dangerous, shouldn't be used in sensitive > > environments, and it cost me much health. > > This kind of blanket statement detracts from anything useful you might > have to say. > > Greg > -- > When replying to this message, please take care not to mutilate the > original text. > For more information, see http://www.lemis.com/email.html > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > To sum it up: 1) This argument is becoming ugly. 2) The fact is, I did my best, and _DID_ provide you with _ALL_ needed information. (among with some useless and some mutilated text). 3) I was trying to say that saying "too much text doesn't allow me to work on it" is an EXCUSE. The PR had the needed information and it wasn't mutilated. Perhaps you think that this bug seldom occures, or, perhaps you have some other reason. 4) RAID-5 cost our company enormous down-time and cost me personally my health. This is why I think it's dangerous and I want to warn others until this bug is fixed. 5) I'm using webmail, thus I'm unable to control the format of the sent mail. Sorry. 6) If it's so hard to you to dig valuable information from PR 22103, I can do it by myself and resubmit it. Will this make any difference? 7) I appreciate your work. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 1:43:36 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 01:43:32 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 67BA037B400 for ; Tue, 2 Jan 2001 01:43:31 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 4F3F8574E4; Tue, 2 Jan 2001 03:44:08 -0600 (CST) Date: Tue, 2 Jan 2001 03:44:08 -0600 From: "Michael C . Wu" To: Roman Shterenzon Cc: Greg Lehey , freebsd-stable@FreeBSD.ORG Subject: Re: vinum malfunction! Message-ID: <20010102034408.B56810@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , Roman Shterenzon , Greg Lehey , freebsd-stable@FreeBSD.ORG References: <20001231101426.K99806@wantadilla.lemis.com> <20010102092819.K44043@wantadilla.lemis.com> <978425185.3a519561dbcdb@webmail.harmonic.co.il> <20010102193241.C40453@wantadilla.lemis.com> <978427080.3a519cc850a45@webmail.harmonic.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <978427080.3a519cc850a45@webmail.harmonic.co.il>; from roman@harmonic.co.il on Tue, Jan 02, 2001 at 11:18:00AM +0200 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 11:18:00AM +0200, Roman Shterenzon scribbled: | Quoting Greg Lehey : | To sum it up: | 1) This argument is becoming ugly. You are getting free consultancy. Greg charges a pretty price for consultancy. And you are "demanding" service. | 2) The fact is, I did my best, and _DID_ provide you with _ALL_ needed | information. | (among with some useless and some mutilated text). Probably not, see #7 of your point. | 3) I was trying to say that saying "too much text doesn't allow me to work on | it" is an EXCUSE. The PR had the needed information and it wasn't mutilated. | Perhaps you think that this bug seldom occures, or, perhaps you have some other | reason. Sarcasm does not win you free support. | 4) RAID-5 cost our company enormous down-time and cost me personally my health. | This is why I think it's dangerous and I want to warn others until this bug is | fixed. It's documented. | 5) I'm using webmail, thus I'm unable to control the format of the sent mail. | Sorry. You are a consultant, and you should be able to find a real MUA for your work. | 6) If it's so hard to you to dig valuable information from PR 22103, I can do it | by myself and resubmit it. Will this make any difference? I read PR/22103, and I don't think you did submit the necessary information. | 7) I appreciate your work. Then please do not sound demanding and make it look like you think that you "deserve" debugging help. Greg is doing this pro bono, you know? Like, your company is not paying him. If your company would pay him, I am sure this problem could be resolved via other means. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 3:11:57 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 03:11:55 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.gelrevision.nl (mail.gelrevision.nl [195.86.58.10]) by hub.freebsd.org (Postfix) with ESMTP id 04B8337B400 for ; Tue, 2 Jan 2001 03:11:55 -0800 (PST) Received: from oT.An'Era [195.86.231.176] by mail.gelrevision.nl with ESMTP (SMTPD32-6.00) id A6CE65400230; Tue, 02 Jan 2001 12:09:02 +0100 Date: Tue, 2 Jan 2001 12:11:41 +0100 (CET) From: Maarten van Schie Sender: To: Kal Torak Cc: Subject: Re: Boot ManagerQuestions In-Reply-To: <3A516E01.6A17FE3B@quake.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Obviously you have never tried to have a system use UTC... > Any playing with BIOS settings would eventually break things in one > system (eg. PnP O/S Installed, CardBuss mode, various other resource > settings) Well no, I live in Holland, 12 huors away from you, and have no reason to do so. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 3:28:25 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 03:28:23 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mailgate.abacus.co.uk (mailgate.abacus.co.uk [194.130.48.21]) by hub.freebsd.org (Postfix) with ESMTP id 96CB937B400 for ; Tue, 2 Jan 2001 03:28:21 -0800 (PST) Received: from abacus.co.uk (pcantony.bl.abacus.co.uk [194.130.48.111]) by mailgate.abacus.co.uk (8.9.3/8.9.3) with ESMTP id LAA32716; Tue, 2 Jan 2001 11:25:26 GMT Sender: antony@mailgate.abacus.co.uk Message-ID: <3A51BB48.1C2DD42E@abacus.co.uk> Date: Tue, 02 Jan 2001 11:28:08 +0000 From: Antony T Curtis Organization: Abacus Polar PLC (UK) X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Michael C . Wu" Cc: Roman Shterenzon , freebsd-stable@FreeBSD.ORG Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support References: <200012282317.PAA04405@spammie.svbug.com> <20010101133411.B51028@peorth.iteration.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Michael C . Wu" wrote: > "Fully functional" for a desktop implies a working sound card too. > This is one of of those things that does not really matter very much. > A good server admin will recompile and customize his kernel. > And a desktop user probably does not know how to compile a kernel. > Are you telling me that, in your consultancy, you just keep GENERIC? > > There is no need for this bikeshed. Whether pcm is included in GEERIC > or not does not really hurt anybody either way. I have successfully compiled the sound support as a lkm.... so it doesn't have to be in the Kernel. Just make the kernel modules available by default then people can use it should they choose to. -- ANTONY T CURTIS Tel: +44 (1635) 36222 Abacus Polar Holdings Ltd Fax: +44 (1635) 38670 > I have discovered the art of deceiving diplomats. I tell them the truth > and they never believe me. >  -- Camillo Di Cavour To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 4:32:25 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 04:32:21 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id F130A37B402 for ; Tue, 2 Jan 2001 04:32:19 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id OAA30587; Tue, 2 Jan 2001 14:29:17 +0200 To: "Michael C . Wu" Subject: Re: vinum malfunction! Message-ID: <978438556.3a51c99cea732@webmail.harmonic.co.il> Date: Tue, 02 Jan 2001 14:29:16 +0200 (IST) From: Roman Shterenzon Cc: Greg Lehey , freebsd-stable@FreeBSD.ORG References: <20001231101426.K99806@wantadilla.lemis.com> <20010102092819.K44043@wantadilla.lemis.com> <978425185.3a519561dbcdb@webmail.harmonic.co.il> <20010102193241.C40453@wantadilla.lemis.com> <978427080.3a519cc850a45@webmail.harmonic.co.il> <20010102034408.B56810@peorth.iteration.net> In-Reply-To: <20010102034408.B56810@peorth.iteration.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting "Michael C . Wu" : > On Tue, Jan 02, 2001 at 11:18:00AM +0200, Roman Shterenzon scribbled: > | Quoting Greg Lehey : > | To sum it up: > | 1) This argument is becoming ugly. > > You are getting free consultancy. Greg charges a pretty > price for consultancy. And you are "demanding" service. ..snip... > | 3) I was trying to say that saying "too much text doesn't allow me to > work on > | it" is an EXCUSE. The PR had the needed information and it wasn't > mutilated. > | Perhaps you think that this bug seldom occures, or, perhaps you have > some other > | reason. > > Sarcasm does not win you free support. > > | 4) RAID-5 cost our company enormous down-time and cost me personally > my health. > | This is why I think it's dangerous and I want to warn others until > this bug is > | fixed. > > It's documented. Where? I asked to document it, but haven't seen it documented. If it's already documented, then I'm happy. > | 5) I'm using webmail, thus I'm unable to control the format of the > sent mail. > | Sorry. > > You are a consultant, and you should be able to find a real MUA > for your work. I'm happy that you know what I should and shouldn't know better than me. > | 6) If it's so hard to you to dig valuable information from PR 22103, I > can do it > | by myself and resubmit it. Will this make any difference? > > I read PR/22103, and I don't think you did submit the necessary > information. What's missing? Be constructive, not destructive > | 7) I appreciate your work. > > Then please do not sound demanding and make it look like you think that > you "deserve" debugging help. Greg is doing this pro bono, you know? > Like, your company is not paying him. If your company would pay him, > I am sure this problem could be resolved via other means. Hello? Do you hear me? Have you read what I've written? I *never* *ever* wanted free support for vinum, I just wanted to help vinum development, and AFAIK I did my best. And I didn't bug greg about this, I submitted info and nothing was done- it was fine with me, I did what I could do about it. What did irritate me is that greg mailed the other person and told him to send a report. My and another person's reports weren't considered at all. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 5:15:25 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 05:15:24 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mcg-ct.com (mcg-ct.com [209.9.201.81]) by hub.freebsd.org (Postfix) with ESMTP id A3E1237B400 for ; Tue, 2 Jan 2001 05:15:23 -0800 (PST) Received: from mcg-ct.com (dhcp1 [192.168.1.128]) by mcg-ct.com (8.11.2/8.11.1) with ESMTP id f02DFM905943 for ; Tue, 2 Jan 2001 08:15:23 -0500 (EST) (envelope-from mcg@mcg-ct.com) Message-ID: <3A51D46A.497C72A1@mcg-ct.com> Date: Tue, 02 Jan 2001 08:15:22 -0500 From: Mike Grierson X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: Join Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Join To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 5:16: 5 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 05:16:04 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mcg-ct.com (mcg-ct.com [209.9.201.81]) by hub.freebsd.org (Postfix) with ESMTP id A599637B402 for ; Tue, 2 Jan 2001 05:16:03 -0800 (PST) Received: from mcg-ct.com (dhcp1 [192.168.1.128]) by mcg-ct.com (8.11.2/8.11.1) with ESMTP id f02DG3905951 for ; Tue, 2 Jan 2001 08:16:03 -0500 (EST) (envelope-from mcg@mcg-ct.com) Message-ID: <3A51D493.138342B6@mcg-ct.com> Date: Tue, 02 Jan 2001 08:16:03 -0500 From: Mike Grierson X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: subscribe freebsd-stable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 5:34:30 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 05:34:27 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from imo-r17.mail.aol.com (imo-r17.mx.aol.com [152.163.225.71]) by hub.freebsd.org (Postfix) with ESMTP id BA7BE37B402 for ; Tue, 2 Jan 2001 05:34:26 -0800 (PST) Received: from Matraquilla@cs.com by imo-r17.mx.aol.com (mail_out_v28.35.) id w.d6.7493e7 (4220); Tue, 2 Jan 2001 08:33:59 -0500 (EST) From: Matraquilla@cs.com Message-ID: Date: Tue, 2 Jan 2001 08:33:58 EST Subject: Re: vinum malfunction! To: "Roman Shterenzon" Cc: "Greg ehey" , freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_d6.7493e7.278332c6_boundary" Content-Disposition: Inline X-Mailer: 6.0 sub 352 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --part1_d6.7493e7.278332c6_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Mr. Lehey: For months now, I have been on the sidelines following your various postings and now this thread in particular. Unfortunately, I get a bad taste in my mouth from a lot of your responses. You are completely intolerant of others' views, deem questions or criticisms as personal attacks and some of your responses are vitriolic. Your general attitude seems to be premised on how Greg is so brilliant and [everybody else] is ignorant, or stupid, or just does not get it. To you I say enough already! I shall not detract from your intellectual ability or knowledge of FreeBSD -- although some of your theories and views are unique and not generally accepted. As to your Vinum sacred cow, when are you going to accept that Vinum shall (and could) never be more than an experimental beta that should never be relied upon fully in a production environment. If you want RAID, you get a RAID controller. If you like to play with explosives and are trying to get away with cheap or free, by all means play with Vinum or its other software siblings. Finally, as to HTML e-mail, whether you like it or not its here to stay, and even the mighty Greg Lehey cannot bully it away. Having said my piece, I return to the sidelines. --part1_d6.7493e7.278332c6_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit Mr. Lehey:

For months now, I have been on the sidelines following your various postings
and now this thread in particular.

Unfortunately, I get a bad taste in my mouth from a lot of your responses.  
You are completely intolerant of others' views, deem questions or criticisms
as personal attacks and some of your responses are vitriolic. Your general
attitude seems to be premised on how Greg is so brilliant and [everybody
else] is ignorant, or stupid, or just does not get it.

To you I say enough already!

I shall not detract from your intellectual ability or knowledge of FreeBSD --
although some of your theories and views are unique and not generally
accepted.

As to your Vinum sacred cow, when are you going to accept that Vinum shall
(and could) never be more than an experimental beta that should never be
relied upon fully in a production environment.  If you want RAID, you get a
RAID controller.  If you like to play with explosives and are trying to get
away with cheap or free, by all means play with Vinum or its other software
siblings.

Finally, as to HTML e-mail, whether you like it or not its here to stay, and
even the mighty Greg Lehey cannot bully it away.

Having said my piece, I return to the sidelines. --part1_d6.7493e7.278332c6_boundary-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 6: 6:16 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 06:06:14 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 5F2DB37B400 for ; Tue, 2 Jan 2001 06:06:14 -0800 (PST) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Tue, 2 Jan 2001 14:06:00 +0000 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 14DS4I-0007Qb-00; Tue, 02 Jan 2001 14:05:38 +0000 Date: Tue, 2 Jan 2001 14:05:38 +0000 (GMT) From: Jan Grant To: freebsd-stable@freebsd.org Subject: Re: vinum malfunction! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Jan Grant Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Jan 2001 Matraquilla@cs.com wrote: > To you I say enough already! Excellent idea. Can we take this somewhere else, like -chat*, ferinstance? jan * or anything else I'm not subscribed to. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk Usenet: The separation of content AND presentation - simultaneously. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 6: 6:32 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 06:06:29 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id AC22337B400 for ; Tue, 2 Jan 2001 06:06:28 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id AF5CA3229; Tue, 2 Jan 2001 14:06:16 +0000 (GMT) Date: Tue, 2 Jan 2001 14:06:16 +0000 From: Josef Karthauser To: Matraquilla@cs.com Cc: Roman Shterenzon , Greg Lehey , freebsd-stable@FreeBSD.ORG Subject: Re: vinum malfunction! Message-ID: <20010102140616.B1391@tao.org.uk> Mail-Followup-To: Josef Karthauser , Matraquilla@cs.com, Roman Shterenzon , Greg Lehey , freebsd-stable@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 Matraquilla@cs.com on Tue, Jan 02, 2001 at 08:33:58AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 08:33:58AM -0500, Matraquilla@cs.com wrote: [cut] > > As to your Vinum sacred cow, when are you going to accept that Vinum shall > (and could) never be more than an experimental beta that should never be > relied upon fully in a production environment. If you want RAID, you get a > RAID controller. If you like to play with explosives and are trying to get > away with cheap or free, by all means play with Vinum or its other software > siblings. > I'm going to jump in here and defend Greg for a moment. There is nothing wrong with doing RAID5 in software. It allows a quick fix without requiring the purchase of hardware for the cases where the machine in question has plenty of spare CPU available (which is most of them by todays standards). It's cool. On the other hand if it doesn't work then it's a nightmare! (Like having bad ram on your raid controller card :). The problem with vinum RAID5 in -stable is that in my experience there are some nasty bugs in it, and I don't believe that Greg has managed to reproduce these himself and so is a bit confused as to what is causing the trouble. I'm worried that he may be inclined to believe that it is only a small minority of people who are having problems with this. I would challange this view because I don't know _anyone_ who is successfully using RAID5 under vinum. They've all migrated away to using dedicated hardware and thus solved their vinum problems that way. I don't know what it's going to take for Greg to get enough information to fix the problem. I spent a week trying to extract a set of debug information for him that was useful enough that he could work from it, but it seems that my week was just wasted because it looks like I didn't capture the bug that he was expecting :(. I have tried to trust my home directory to vinum raid5 but failed. :( To summarise. The idea of software raid 5 is great, but it's got to work otherwise it is dangerous. I note that the BUGS section of the manual page doesn't exist. There should be a warning to potential users that there are known problems that can cause the data to become corrupted in some configurations. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 6:49:18 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 06:49:16 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.ost.eltele.no (relay.ost.eltele.no [195.70.164.132]) by hub.freebsd.org (Postfix) with ESMTP id BC15037B400 for ; Tue, 2 Jan 2001 06:49:15 -0800 (PST) Received: from beck (ppp-212.125.164.199.sensewave.com [212.125.164.199]) by relay.ost.eltele.no (8.9.3/8.9.3) with SMTP id PAA04876 for ; Tue, 2 Jan 2001 15:49:13 +0100 (MET) Message-ID: <000701c074cb$2f912b80$c7a47dd4@kleppst.no> Reply-To: "Rune Mossige" From: "Rune Mossige" To: Subject: ASUS A7V and promise problems Date: Tue, 2 Jan 2001 15:49:10 +0100 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.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just bought myself a Christmas present, a new ASUS A7V, Amd Athlon 750, onboard Promise, and 2 x IBM-DTLA-30745 45GB ATA100 disks. In order to install FreeBSD 4.2, I also installed an older 540MB IDE disk. FreeBSD 4.2 was CVSUP'ed and buildworld/installworld done on 31. December 2000. FreeBSD boots fine, and finds the promise and disks. But, whenever try to access the disks, the box freeze solid after 2-4 seconds....a hard reset is required. New BIOS are also installed (1005a) with no luck. I have also reduced all relevant speed settings in the bios, with no luck. The disks are connected with brand new ATA100 cables. There is a working fan on the CPU, and I do not think it is too hot. The BIOS reports MB at 33C and CPU at 41C. Both disks are primary on their own Promise channel. Is there anyone who have some hints as to what might be wrong? I have rebuilt the kernel (GENERIC) and enabled debug. Everything else is left as defaults. But, there is no core, no debug, nothing. Just solid freeze. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 6:56:25 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 06:56:23 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from brave.vnet (IP1A0468.aic.mesh.ad.jp [211.13.107.214]) by hub.freebsd.org (Postfix) with ESMTP id EA22D37B400 for ; Tue, 2 Jan 2001 06:56:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by brave.vnet (8.11.1/8.11.1) with ESMTP id f02ExCT01107 for ; Tue, 2 Jan 2001 23:59:14 +0900 (JST) (envelope-from daichi@ongs.net) Date: Tue, 2 Jan 2001 23:59:12 +0900 (JST) From: "Daichi T.GOTO" To: stable@FreeBSD.ORG Subject: FUJITSU MO (ATAPI) with FreeBSD 4.2 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Mailer: Yuzu version 1.0 Organization: ONGS Mime-Version: 1.0 Message-ID: <84775158.978447552384.JavaMail.daichi@localhost> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is a way to use FUJITSU MO (ATAPI) ? /home/daichi/work(197) dmesg | grep ata atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 29311MB [59554/16/63] at ata0-master UDMA66 acd0: CD-RW at ata1-master using PIO4 ata1-slave: optical device - NO DRIVER! /home/daichi/work(198) I'm using FreeBSD 4.2-Release. But he said "NO DRIVER!". It is rumored that you can use MO(ATAPI) in FreeBSD-current. Can I use it with FreeBSD 4.2-Release? P.S. I can use CD-RW(ATAPI) with burncd(8). That works well. Daichi T.GOTO(ONGS) http://www.ongs.net/daichi, daichi@ongs.gr.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 7: 2:12 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 07:02:09 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wormhole.bluestar.net (wormhole.bluestar.net [208.53.1.61]) by hub.freebsd.org (Postfix) with ESMTP id 6378D37B400 for ; Tue, 2 Jan 2001 07:02:09 -0800 (PST) Received: from planetwe.com (admin.planetwe.com [64.182.69.146]) by wormhole.bluestar.net (8.10.1/8.10.1) with ESMTP id f02F2C724683; Tue, 2 Jan 2001 09:02:12 -0600 (CST) Message-ID: <3A51ED6A.6060501@planetwe.com> Date: Tue, 02 Jan 2001 09:02:02 -0600 From: Drew Sanford User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.12 i386; en-GB; m18) Gecko/20001107 Netscape6/6.0 X-Accept-Language: en MIME-Version: 1.0 To: Rune Mossige Cc: freebsd-stable@freebsd.org Subject: Re: ASUS A7V and promise problems References: <000701c074cb$2f912b80$c7a47dd4@kleppst.no> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm going to take a shot at this, because I have one of these boards, and had some problems with it at first as well. Is the box actually booting all the way up and giving you a login prompt, or is it freezing during the bootup? If its freezing during the boot, give it a minute - maybe 2 minutes. If it doesn't come around and start working, try disabling the parallel port in the bios and rebooting. If this works, you're going to need to find out what is trying to use the IRQ of the parallel port and assign it a different IRQ, then you can re-enable the parallel port and you should be able to boot fine. There should (or rather will) be a pause during the boot because of some minor problems that I don't fully understand, and the pause should happen about the time the drives are detected. The board (and the drives) will work, (or at least my setup does; though I only have one DTLA-30745) and quite well with the exception of the pause during bootup. Hope this helps. Rune Mossige wrote: > I just bought myself a Christmas present, a new ASUS A7V, Amd Athlon 750, > onboard Promise, and 2 x IBM-DTLA-30745 45GB ATA100 disks. > > In order to install FreeBSD 4.2, I also installed an older 540MB IDE disk. > > FreeBSD 4.2 was CVSUP'ed and buildworld/installworld done on 31. December > 2000. > > FreeBSD boots fine, and finds the promise and disks. But, whenever try to > access the disks, the box freeze solid after 2-4 seconds....a hard reset is > required. > > New BIOS are also installed (1005a) with no luck. I have also reduced all > relevant speed settings in the bios, with no luck. > > The disks are connected with brand new ATA100 cables. > > There is a working fan on the CPU, and I do not think it is too hot. The > BIOS reports MB at 33C and CPU at 41C. Both disks are primary on their own > Promise channel. > > Is there anyone who have some hints as to what might be wrong? I have > rebuilt the kernel (GENERIC) and enabled debug. Everything else is left as > defaults. But, there is no core, no debug, nothing. Just solid freeze. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Drew Sanford Systems Administrator Planetwe.com Email: drew@planetwe.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 7:15: 6 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 07:15:03 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 3FD1737B400 for ; Tue, 2 Jan 2001 07:15:02 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for r.mossige@sensewave.com id PAA22086; Tue Jan 2 15:13:51 2001 Date: Tue, 2 Jan 2001 15:21:38 +0000 Subject: Re: ASUS A7V and promise problems Message-ID: <20010102152138.J419@freefire.psi-domain.co.uk> References: <000701c074cb$2f912b80$c7a47dd4@kleppst.no> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <000701c074cb$2f912b80$c7a47dd4@kleppst.no>; from r.mossige@sensewave.com on Tue, Jan 02, 2001 at 14:49:10 +0000 X-Mailer: Balsa 1.0.0 Lines: 55 To: Rune Mossige From: Jamie Heckford Reply-To: heckfordj@psi-domain.co.uk Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We had to send back about 50 ABit boards because they had the same problem on ATA100 - Wouldnt boot FreeBSD, Linux, Windoze anything. Maybe the problem has affected the ASUS boards as well - would be interesting to know if they use the same / v. similar firmware. The problems we had were that we were not able to boot of any IDE/ATAPI devices, we installed FreeBSD using boot floppys and Network, however when booting from an IDE device no luck. Maybe dodgy, could be a BIOS issue. J On 2001.01.02 14:49:10 +0000 Rune Mossige wrote: > I just bought myself a Christmas present, a new ASUS A7V, Amd Athlon 750, > onboard Promise, and 2 x IBM-DTLA-30745 45GB ATA100 disks. > > In order to install FreeBSD 4.2, I also installed an older 540MB IDE > disk. > > FreeBSD 4.2 was CVSUP'ed and buildworld/installworld done on 31. December > 2000. > > FreeBSD boots fine, and finds the promise and disks. But, whenever try > to > access the disks, the box freeze solid after 2-4 seconds....a hard reset > is > required. > > New BIOS are also installed (1005a) with no luck. I have also reduced all > relevant speed settings in the bios, with no luck. > > The disks are connected with brand new ATA100 cables. > > There is a working fan on the CPU, and I do not think it is too hot. The > BIOS reports MB at 33C and CPU at 41C. Both disks are primary on their > own > Promise channel. > > Is there anyone who have some hints as to what might be wrong? I have > rebuilt the kernel (GENERIC) and enabled debug. Everything else is left > as > defaults. But, there is no core, no debug, nothing. Just solid freeze. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 7:18:46 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 07:18:42 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.ost.eltele.no (relay.ost.eltele.no [195.70.164.132]) by hub.freebsd.org (Postfix) with ESMTP id AD74B37B400 for ; Tue, 2 Jan 2001 07:18:40 -0800 (PST) Received: from beck (ppp-212.125.161.42.sensewave.com [212.125.161.42]) by relay.ost.eltele.no (8.9.3/8.9.3) with SMTP id QAA14248; Tue, 2 Jan 2001 16:18:37 +0100 (MET) Message-ID: <000901c074cf$4b93bec0$2aa17dd4@kleppst.no> Reply-To: "Rune Mossige" From: "Rune Mossige" To: "Rune Mossige" , Cc: References: <000701c074cb$2f912b80$c7a47dd4@kleppst.no> Subject: Re: ASUS A7V and promise problems Date: Tue, 2 Jan 2001 16:18:34 +0100 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.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The box boot just fine, with no noticable delay. I can do all normal work. I have been able to create a small 1GB partition on each disk. I can mount this etc. When I run 'iozone' on it, it runs fine for a while....iozone completes on a small file (10-50MB), but freeze on a large (200+MB) file. I have disabled the parallel port in bios, but no change in behavior... ----- Original Message ----- From: "Rune Mossige" To: Sent: 2. januar 2001 15:49 Subject: ASUS A7V and promise problems > I just bought myself a Christmas present, a new ASUS A7V, Amd Athlon 750, > onboard Promise, and 2 x IBM-DTLA-30745 45GB ATA100 disks. > > In order to install FreeBSD 4.2, I also installed an older 540MB IDE disk. > > FreeBSD 4.2 was CVSUP'ed and buildworld/installworld done on 31. December > 2000. > > FreeBSD boots fine, and finds the promise and disks. But, whenever try to > access the disks, the box freeze solid after 2-4 seconds....a hard reset is > required. > > New BIOS are also installed (1005a) with no luck. I have also reduced all > relevant speed settings in the bios, with no luck. > > The disks are connected with brand new ATA100 cables. > > There is a working fan on the CPU, and I do not think it is too hot. The > BIOS reports MB at 33C and CPU at 41C. Both disks are primary on their own > Promise channel. > > Is there anyone who have some hints as to what might be wrong? I have > rebuilt the kernel (GENERIC) and enabled debug. Everything else is left as > defaults. But, there is no core, no debug, nothing. Just solid freeze. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 7:54:37 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 07:54:35 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from filer.fr.clara.net (filer.fr.clara.net [212.43.194.74]) by hub.freebsd.org (Postfix) with ESMTP id 2717A37B402 for ; Tue, 2 Jan 2001 07:54:31 -0800 (PST) Received: from fr.clara.net (alt.noc.fr.clara.net [212.43.195.27]) by filer.fr.clara.net (Postfix) with ESMTP id 1D4916AF5 for ; Tue, 2 Jan 2001 17:02:10 +0100 (CET) Sender: alt@filer.fr.clara.net Message-ID: <3A51F9BD.8526E2C@fr.clara.net> Date: Tue, 02 Jan 2001 16:54:37 +0100 From: Arnaud Le Taillanter X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freeBSD.org Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 8:22:54 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 08:22:51 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.ost.eltele.no (relay.ost.eltele.no [195.70.164.132]) by hub.freebsd.org (Postfix) with ESMTP id 48D5937B400 for ; Tue, 2 Jan 2001 08:22:50 -0800 (PST) Received: from beck (ppp-212.125.162.201.sensewave.com [212.125.162.201]) by relay.ost.eltele.no (8.9.3/8.9.3) with SMTP id RAA27293; Tue, 2 Jan 2001 17:22:46 +0100 (MET) Message-ID: <004101c074d8$41fe0ba0$2aa17dd4@kleppst.no> Reply-To: "Rune Mossige" From: "Rune Mossige" To: Cc: References: <000701c074cb$2f912b80$c7a47dd4@kleppst.no> <20010102152138.J419@freefire.psi-domain.co.uk> Subject: Re: ASUS A7V and promise problems Date: Tue, 2 Jan 2001 17:22:44 +0100 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.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Promise identifies itself as 'UltraDMA (tm) v2.01 (Build 33)' Prior to the BIOS upgrade earlier today from 1004d to 1005a, it identified itself as 'v2.01 (Build 28)' Is that the same version? This board boots, and dmesg output looks proper to me. ----- Original Message ----- From: "Jamie Heckford" To: "Rune Mossige" Cc: Sent: 2. januar 2001 16:21 Subject: Re: ASUS A7V and promise problems > We had to send back about 50 ABit boards because they had the same problem > on > ATA100 - Wouldnt boot FreeBSD, Linux, Windoze anything. > > Maybe the problem has affected the ASUS boards as well - would be > interesting > to know if they use the same / v. similar firmware. > > The problems we had were that we were not able to boot of any IDE/ATAPI > devices, we > installed FreeBSD using boot floppys and Network, however when booting from > an > IDE device no luck. > > Maybe dodgy, could be a BIOS issue. > > J > > On 2001.01.02 14:49:10 +0000 Rune Mossige wrote: > > I just bought myself a Christmas present, a new ASUS A7V, Amd Athlon 750, > > onboard Promise, and 2 x IBM-DTLA-30745 45GB ATA100 disks. > > > > In order to install FreeBSD 4.2, I also installed an older 540MB IDE > > disk. > > > > FreeBSD 4.2 was CVSUP'ed and buildworld/installworld done on 31. December > > 2000. > > > > FreeBSD boots fine, and finds the promise and disks. But, whenever try > > to > > access the disks, the box freeze solid after 2-4 seconds....a hard reset > > is > > required. > > > > New BIOS are also installed (1005a) with no luck. I have also reduced all > > relevant speed settings in the bios, with no luck. > > > > The disks are connected with brand new ATA100 cables. > > > > There is a working fan on the CPU, and I do not think it is too hot. The > > BIOS reports MB at 33C and CPU at 41C. Both disks are primary on their > > own > > Promise channel. > > > > Is there anyone who have some hints as to what might be wrong? I have > > rebuilt the kernel (GENERIC) and enabled debug. Everything else is left > > as > > defaults. But, there is no core, no debug, nothing. Just solid freeze. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 8:53:28 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 08:53:26 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from new.buzzit.com (unknown [206.80.217.164]) by hub.freebsd.org (Postfix) with ESMTP id 4FCCD37B400 for ; Tue, 2 Jan 2001 08:53:26 -0800 (PST) Received: from www.georgewood.net (phnxdslgw9poolC225.phnx.uswest.net [63.229.82.225]) by new.buzzit.com (8.9.3/8.9.3) with ESMTP id JAA34371 for ; Tue, 2 Jan 2001 09:52:37 -0700 (MST) (envelope-from gwood@georgewood.net) Received: from georgewood.net (localhost [127.0.0.1]) by www.georgewood.net (8.9.3/8.9.3) with ESMTP id JAA03950 for ; Tue, 2 Jan 2001 09:59:01 -0700 (MST) (envelope-from gwood@georgewood.net) Sender: gwood@www.georgewood.net Message-ID: <3A5208D5.C844BEA6@georgewood.net> Date: Tue, 02 Jan 2001 09:59:01 -0700 From: George Wood X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.org Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 8:58:37 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 08:58:36 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from new.buzzit.com (unknown [206.80.217.164]) by hub.freebsd.org (Postfix) with ESMTP id 5C71637B400 for ; Tue, 2 Jan 2001 08:58:36 -0800 (PST) Received: from localhost (gwood@localhost) by new.buzzit.com (8.9.3/8.9.3) with ESMTP id JAA34394 for ; Tue, 2 Jan 2001 09:57:58 -0700 (MST) (envelope-from gwood@georgewood.net) Date: Tue, 2 Jan 2001 09:57:58 -0700 (MST) From: George Wood X-Sender: gwood@new.buzzit.com To: stable@freebsd.org Subject: help Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 9:25:27 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 09:25:25 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from gateway.symark.com (firewall.symark.westlake.iswest.net [207.178.203.34]) by hub.freebsd.org (Postfix) with ESMTP id B081337B400 for ; Tue, 2 Jan 2001 09:25:24 -0800 (PST) Received: (from mailer@localhost) by gateway.symark.com (8.9.3/8.9.3) id JAA17250; Tue, 2 Jan 2001 09:25:18 -0800 Received: from camel.symark.com(128.1.1.97) by gateway.symark.com via smap (V2.1+anti-relay+anti-spam) id xma017239; Tue, 2 Jan 01 09:25:07 -0800 Received: by localhost with Microsoft MAPI; Tue, 2 Jan 2001 09:27:39 -0800 Message-ID: <01C0749E.401B4E40.ggross@symark.com> From: Glen Gross Reply-To: "ggross@symark.com" To: "'George Wood'" Cc: "'stable@freebsd.org'" Subject: RE: help Date: Tue, 2 Jan 2001 09:27:38 -0800 Return-Receipt-To: Glen Gross Organization: Symark Software X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can you provide more information about the problem? On Tuesday, January 02, 2001 8:58 AM, George Wood [SMTP:gwood@georgewood.net] wrote: > help > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Glen M. Gross Unix Technical Support Specialist Symark Software 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 http://www.symark.com unix-support@symark.com Main: 800-234-9072 or 818-865-6100 Main fax: 818-889-1894 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 9:32:50 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 09:32:41 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.ost.eltele.no (relay.ost.eltele.no [195.70.164.132]) by hub.freebsd.org (Postfix) with ESMTP id BA9E437B400 for ; Tue, 2 Jan 2001 09:32:40 -0800 (PST) Received: from beck (ppp-212.125.162.201.sensewave.com [212.125.162.201]) by relay.ost.eltele.no (8.9.3/8.9.3) with SMTP id SAA10469; Tue, 2 Jan 2001 18:32:37 +0100 (MET) Message-ID: <005b01c074e2$03d9a500$2aa17dd4@kleppst.no> Reply-To: "Rune Mossige" From: "Rune Mossige" To: "Rune Mossige" , Cc: References: <000701c074cb$2f912b80$c7a47dd4@kleppst.no> <20010102152138.J419@freefire.psi-domain.co.uk> <004101c074d8$41fe0ba0$2aa17dd4@kleppst.no> Subject: Re: ASUS A7V and promise problems, SOLVED Date: Tue, 2 Jan 2001 18:32:37 +0100 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.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My problems about the promise appears to have been solved....it was an IRQ conflict between the 3COM 3C905C and the onboard USB controller, both using irq5. Why this caused the disks on the promise (irq 10) to fail, I do not know.....Now I just ned to figure out how to get all adapters (SoundBlaster Live!, 3com network adapter and RIVA TNT AGP adapter) to coexist happily with their own IRQ's. ----- Original Message ----- From: "Rune Mossige" To: Cc: Sent: 2. januar 2001 17:22 Subject: Re: ASUS A7V and promise problems > The Promise identifies itself as 'UltraDMA (tm) v2.01 (Build 33)' > > Prior to the BIOS upgrade earlier today from 1004d to 1005a, it identified > itself as 'v2.01 (Build 28)' > > Is that the same version? This board boots, and dmesg output looks proper to > me. > > ----- Original Message ----- > From: "Jamie Heckford" > To: "Rune Mossige" > Cc: > Sent: 2. januar 2001 16:21 > Subject: Re: ASUS A7V and promise problems > > > > We had to send back about 50 ABit boards because they had the same problem > > on > > ATA100 - Wouldnt boot FreeBSD, Linux, Windoze anything. > > > > Maybe the problem has affected the ASUS boards as well - would be > > interesting > > to know if they use the same / v. similar firmware. > > > > The problems we had were that we were not able to boot of any IDE/ATAPI > > devices, we > > installed FreeBSD using boot floppys and Network, however when booting > from > > an > > IDE device no luck. > > > > Maybe dodgy, could be a BIOS issue. > > > > J > > > > On 2001.01.02 14:49:10 +0000 Rune Mossige wrote: > > > I just bought myself a Christmas present, a new ASUS A7V, Amd Athlon > 750, > > > onboard Promise, and 2 x IBM-DTLA-30745 45GB ATA100 disks. > > > > > > In order to install FreeBSD 4.2, I also installed an older 540MB IDE > > > disk. > > > > > > FreeBSD 4.2 was CVSUP'ed and buildworld/installworld done on 31. > December > > > 2000. > > > > > > FreeBSD boots fine, and finds the promise and disks. But, whenever try > > > to > > > access the disks, the box freeze solid after 2-4 seconds....a hard reset > > > is > > > required. > > > > > > New BIOS are also installed (1005a) with no luck. I have also reduced > all > > > relevant speed settings in the bios, with no luck. > > > > > > The disks are connected with brand new ATA100 cables. > > > > > > There is a working fan on the CPU, and I do not think it is too hot. The > > > BIOS reports MB at 33C and CPU at 41C. Both disks are primary on their > > > own > > > Promise channel. > > > > > > Is there anyone who have some hints as to what might be wrong? I have > > > rebuilt the kernel (GENERIC) and enabled debug. Everything else is left > > > as > > > defaults. But, there is no core, no debug, nothing. Just solid freeze. > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 9:59:11 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 09:59:08 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id 1865137B400 for ; Tue, 2 Jan 2001 09:59:05 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14DVgh-000J0b-00 for freebsd-stable@freebsd.org; Tue, 2 Jan 2001 20:57:32 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.16 #1) id 14DVhp-00035m-00 for freebsd-stable@freebsd.org; Tue, 02 Jan 2001 20:58:41 +0300 Date: Tue, 2 Jan 2001 20:58:40 +0300 From: Odhiambo Washington To: FBSD-STABLE Subject: Help Update Message-ID: <20010102205840.A11796@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , FBSD-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD poeza.iconnect.co.ke 3.5-STABLE FreeBSD 3.5-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: Odhiambo Washington Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I am running 4.2-STABLE. I decided to cvsup the source tree today and make world but hit a big snag. I therefore beg to take this chance to seek your advise/help on regaining the system. When I do make buildworld I end up with gibberish and this error: /usr/bin/tbl: 104: Syntax error: ";" unexpected groff: troff: Segmentation fault (core dumped) *** Error code 3 ..And I get this message so many times on the console.. n 2 20:36:57 alouette /kernel: pid 56184 (troff), uid 0: exited on signal 11 (core dumped) Jan 2 20:36:57 alouette /kernel: pid 56202 (troff), uid 0: exited on signal 11 (core dumped) Jan 2 20:36:58 alouette /kernel: pid 56220 (troff), uid 0: exited on signal 11 (core dumped) Jan 2 20:36:58 alouette /kernel: pid 56243 (troff), uid 0: exited on signal 11 (core dumped) Jan 2 20:36:58 alouette /kernel: pid 56261 (troff), uid 0: exited on signal 11 (core dumped) Jan 2 20:36:58 alouette /kernel: pid 56279 (troff), uid 0: exited on signal 11 (core dumped) Jan 2 20:36:59 alouette /kernel: pid 56297 (troff), uid 0: exited on signal 11 (core dumped) I've not changed any config in the system and I've done make build/installworld before without any problems. Could someone kindly advise me on what the cause of this could be? Is there something I have to do? On top of this, I cannot access any man pages anymore. Any attempt to man some command either just beeps and gives gibberish or gives an empty screen. alouette# uname -a FreeBSD alouette.iconnect.co.ke 4.2-STABLE FreeBSD 4.2-STABLE #0: Sat Dec 23 13:14:01 EAT 2000 wash@alouette.iconnect.co.ke:/usr/obj/usr/src/sys/ALOUETTE i 386 I've even manually deleted /usr/obj and tried redoing make buildworld and still end up at the same place with so many beeps, gibberish then the error above. All help appreciated. -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. If all mankind minus one were of one opinion, mankind would be no more justified in silencing that one person than he, if he had the power, would be justified in silencing mankind. -John Stuart Mill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 10:26:34 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 10:26:32 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wormhole.bluestar.net (wormhole.bluestar.net [208.53.1.61]) by hub.freebsd.org (Postfix) with ESMTP id B1B7437B402 for ; Tue, 2 Jan 2001 10:26:30 -0800 (PST) Received: from planetwe.com (admin.planetwe.com [64.182.69.146]) by wormhole.bluestar.net (8.10.1/8.10.1) with ESMTP id f02IQD714273; Tue, 2 Jan 2001 12:26:15 -0600 (CST) Message-ID: <3A521D3C.3090908@planetwe.com> Date: Tue, 02 Jan 2001 12:26:04 -0600 From: Drew Sanford User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.12 i386; en-GB; m18) Gecko/20001107 Netscape6/6.0 X-Accept-Language: en MIME-Version: 1.0 To: Odhiambo Washington Cc: FBSD-STABLE Subject: Re: Help Update References: <20010102205840.A11796@poeza.iconnect.co.ke> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Odhiambo Washington wrote: > > > n 2 20:36:57 alouette /kernel: pid 56184 (troff), uid 0: exited on signal > 11 (core dumped) Signal 11 usually indicates a hardware problem. Have you added any memory or changed (or overclocked?) your processor since you last did a make world? -- Drew Sanford Systems Administrator Planetwe.com Email: drew@planetwe.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 10:32:16 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 10:32:14 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id CCB6537B402 for ; Tue, 2 Jan 2001 10:32:10 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14DWCb-000Jw5-00; Tue, 2 Jan 2001 21:30:30 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.16 #1) id 14DWDw-0003DF-00; Tue, 02 Jan 2001 21:31:52 +0300 Date: Tue, 2 Jan 2001 21:31:52 +0300 From: Odhiambo Washington To: Drew Sanford Cc: FBSD-STABLE Subject: Re: Help Update Message-ID: <20010102213152.A12306@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , Drew Sanford , FBSD-STABLE References: <20010102205840.A11796@poeza.iconnect.co.ke> <3A521D3C.3090908@planetwe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A521D3C.3090908@planetwe.com>; from "Drew Sanford" on Tue, Jan 02, 2001 at 12:26:04PM -0600 X-Operating-System: FreeBSD poeza.iconnect.co.ke 3.5-STABLE FreeBSD 3.5-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: Odhiambo Washington Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Drew Sanford [20010102 21:26]: writing on the subject 'Re: Help Update' =>Odhiambo Washington wrote: => =>> =>> =>> n 2 20:36:57 alouette /kernel: pid 56184 (troff), uid 0: exited on signal =>> 11 (core dumped) => =>Signal 11 usually indicates a hardware problem. Have you added any =>memory or changed (or overclocked?) your processor since you last did a =>make world? Nope! I haven't changed anything on the machine. I have no idea how to overclock a processor ;-) - I just run FreeBSD on this box and that is all. What hardware could this be? The only option I remember changing in the kernel is for high resolution support. options VESA. The kernel compile was successful. I've not changed anything else. Thanks for the prompt response. => =>-- =>Drew Sanford =>Systems Administrator =>Planetwe.com =>Email: drew@planetwe.com => -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. If we spoke a different language, we would perceive a somewhat different world. -Wittgenstein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 11:10:49 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 11:10:47 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id 27C6437B400 for ; Tue, 2 Jan 2001 11:10:47 -0800 (PST) Received: (qmail 64098 invoked from network); 2 Jan 2001 19:10:36 -0000 Received: from unknown (HELO prydn.tacni.net) (207.55.167.31) by 216.178.136.168 with SMTP; 2 Jan 2001 19:10:36 -0000 Received: (qmail 1940 invoked by uid 1001); 2 Jan 2001 19:10:13 -0000 Date: Tue, 2 Jan 2001 13:10:12 -0600 From: Erich Zigler To: freebsd-stable@freebsd.org Subject: Threaded C++ Question Message-ID: <20010102131012.A1922@superhero.org> Mail-Followup-To: Erich Zigler , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: needo@prydn.tacni.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reading through the archives I have seen several emails regarding the problems people have experienced with MySQL, and Mozilla on 4.2 systems. I was wondering if these problems have been resolved in the main source tree yet. -- Erich Zigler What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against? -- Lary Wall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 11:29:50 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 11:29:48 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from math.uic.edu (galois.math.uic.edu [131.193.178.114]) by hub.freebsd.org (Postfix) with SMTP id 2F91F37B400 for ; Tue, 2 Jan 2001 11:29:48 -0800 (PST) Received: (qmail 15333 invoked by uid 31415); 2 Jan 2001 19:29:05 -0000 Date: Tue, 2 Jan 2001 13:29:05 -0600 From: "Vladimir V. Egorin" To: freebsd-stable@freebsd.org Subject: fetch problem Message-ID: <20010102132905.A15311@math.uic.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear -STABLE Users, I ran into some problems with the ports collection (the system is 4.2-STABLE, built on Dec 21). My machine is sitting behind a proxy server (proxying http/ftp requests). I've set export FTP_PROXY=ftp://proxy_address:1080/ export HTTP_PROXY=ftp://proxy_address:1080/ I've also tried setting FTP_PASSIVE_MODE. Fetch fails with the messages: >> libtool-1.3.4.tar.gz doesn't seem to exist in /usr/ports/distfiles/. >> Attempting to fetch from ftp://ftp.gnu.org/gnu/libtool/. fetch: libtool-1.3.4.tar.gz: Protocol error Does anyone know why this is happening? Many thanks, -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 11:57: 7 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 11:57:04 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from math.uic.edu (galois.math.uic.edu [131.193.178.114]) by hub.freebsd.org (Postfix) with SMTP id 6C69037B400 for ; Tue, 2 Jan 2001 11:57:04 -0800 (PST) Received: (qmail 15489 invoked by uid 31415); 2 Jan 2001 19:56:49 -0000 Date: Tue, 2 Jan 2001 13:56:48 -0600 From: "Vladimir V. Egorin" To: "James L. Skidmore" Cc: freebsd-stable@freebsd.org Subject: Re: fetch problem Message-ID: <20010102135648.A15479@math.uic.edu> References: <20010102132905.A15311@math.uic.edu> <20010102133550.A5828@linux-guy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010102133550.A5828@linux-guy.com>; from james@linux-guy.com on Tue, Jan 02, 2001 at 01:35:50PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James, thanks for your answer. I have these lines in /etc/host.conf. Vladimir On Tue, Jan 02, 2001 at 01:35:50PM -0600, James L. Skidmore wrote: > Make sure that your /etc/host.conf file looks like this - > > order hosts, bind > multi on > > -- > ============================================================ > James L. Skidmore james@linux-guy.com > http://linux-guy.com helpline: metro 817-516-7170 > Linux - Consulting - Training - Security - Networks > ============================================================ > > On Tue, Jan 02, 2001 at 01:29:05PM -0600, Vladimir V. Egorin wrote: > > Dear -STABLE Users, > > > > I ran into some problems with the ports collection (the system is > > 4.2-STABLE, built on Dec 21). My machine is sitting behind > > a proxy server (proxying http/ftp requests). > > > > I've set > > export FTP_PROXY=ftp://proxy_address:1080/ > > export HTTP_PROXY=ftp://proxy_address:1080/ > > I've also tried setting FTP_PASSIVE_MODE. > > > > Fetch fails with the messages: > > > > >> libtool-1.3.4.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > > >> Attempting to fetch from ftp://ftp.gnu.org/gnu/libtool/. > > fetch: libtool-1.3.4.tar.gz: Protocol error > > > > Does anyone know why this is happening? > > Many thanks, > > > > -- > > Vladimir > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 12:22: 2 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 12:21:57 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.6.9.33]) by hub.freebsd.org (Postfix) with ESMTP id 138AA37B400 for ; Tue, 2 Jan 2001 12:21:57 -0800 (PST) Received: from msgrel1.and.agilent.com (msgrel1.and.agilent.com [130.30.33.104]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id EDF07265 for ; Tue, 2 Jan 2001 13:21:55 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.and.agilent.com (Postfix) with ESMTP id C69C1147 for ; Tue, 2 Jan 2001 15:21:54 -0500 (EST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id MAA16583 for ; Tue, 2 Jan 2001 12:21:46 -0800 (PST) Message-Id: <200101022021.MAA16583@mina.soco.agilent.com> To: freebsd-stable@FreeBSD.ORG Subject: tcp wrappers, inetd, & setproctitle() ??? Reply-To: Darryl Okahata Mime-Version: 1.0 (generated by tm-edit 1.6) Content-Type: multipart/mixed; boundary="Multipart_Tue_Jan__2_12:21:45_2001-1" Content-Transfer-Encoding: 7bit Date: Tue, 02 Jan 2001 12:21:46 -0800 From: Darryl Okahata Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Tue_Jan__2_12:21:45_2001-1 Content-Type: text/plain; charset=US-ASCII Hi, Are there any known problems with tcp wrappers in FreeBSD 4.2-RELEASE? (Yes, I've looked through the archives and dejanews and can't find anything.) If tcp wrappers are enabled, I'm having a problem where I can't connect to a 4.2-RELEASE system via telnet (or any other inetd-managed service, from the local or a remote system (I have verified that /etc/hosts.{allow,deny} are correct). Strangely enough, syslog doesn't show any errors or connection attempts (failed or successful), even with maximum logging. Being desperate, I tried ktrace'ing inetd, and it appears that, with tcp wrapping enabled, inetd is failing to spawn child processes (e.g., telnetd) because setproctitle() can't be found by ld-elf.so.1 (see attached inetd.ktrace file). $ nm -D /usr/sbin/inetd | grep setproc U setproctitle $ ldd /usr/sbin/inetd /usr/sbin/inetd: libutil.so.3 => /usr/lib/libutil.so.3 (0x2806b000) libwrap.so.3 => /usr/lib/libwrap.so.3 (0x28074000) libipsec.so.1 => /usr/lib/libipsec.so.1 (0x2807c000) libc.so.4 => /usr/lib/libc.so.4 (0x28082000) $ nm -D /usr/lib/libutil.so.3 | grep setproc $ nm -D /usr/lib/libwrap.so.3 | grep setproc $ nm -D /usr/lib/libipsec.so.1 | grep setproc $ nm -D /usr/lib/libc.so.4 | grep setproc I haven't done a buildworld (I upgraded via the 4.2-RELEASE CDROM), but it seems that setproctitle() should be in libc, but it isn't. Any comments? -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. --Multipart_Tue_Jan__2_12:21:45_2001-1 Content-Type: text/plain; charset=US-ASCII Content-Disposition: attachment; filename="inetd.ktrace" Content-Transfer-Encoding: quoted-printable 11746 inetd RET select 1 11746 inetd CALL ioctl(0x7,FIONBIO,0xbfbff5c4) 11746 inetd RET ioctl 0 11746 inetd CALL accept(0x7,0,0) 11746 inetd RET accept 13/0xd 11746 inetd CALL ioctl(0x7,FIONBIO,0xbfbff5c4) 11746 inetd RET ioctl 0 11746 inetd CALL ioctl(0xd,FIONBIO,0xbfbff5c4) 11746 inetd RET ioctl 0 11746 inetd CALL sigprocmask(0x1,0xbfbff570,0xbfbff560) 11746 inetd RET sigprocmask 0 11746 inetd CALL gettimeofday(0x805c3c8,0) 11746 inetd RET gettimeofday 0 11746 inetd CALL fork 11746 inetd RET fork 11753/0x2de9 11746 inetd CALL sigprocmask(0x3,0xbfbff570,0xbfbff560) 11746 inetd RET sigprocmask 0 11746 inetd CALL close(0xd) 11746 inetd RET close 0 11746 inetd CALL select(0xd,0xbfbff604,0,0,0) 11753 inetd RET fork 0 11753 inetd CALL sigprocmask(0x3,0xbfbff570,0xbfbff560) 11753 inetd RET sigprocmask 0 11753 inetd CALL close(0xc) 11753 inetd RET close 0 11753 inetd CALL close(0xb) 11753 inetd RET close 0 11753 inetd CALL close(0xa) 11753 inetd RET close 0 11753 inetd CALL close(0x9) 11753 inetd RET close 0 11753 inetd CALL close(0x8) 11753 inetd RET close 0 11753 inetd CALL close(0x7) 11753 inetd RET close 0 11753 inetd CALL close(0x6) 11753 inetd RET close 0 11753 inetd CALL close(0x5) 11753 inetd RET close 0 11753 inetd CALL close(0x4) 11753 inetd RET close 0 11753 inetd CALL close(0x3) 11753 inetd RET close 0 11753 inetd CALL sigaction(0xe,0xbfbffb40,0) 11753 inetd RET sigaction 0 11753 inetd CALL sigaction(0x14,0xbfbffb28,0) 11753 inetd RET sigaction 0 11753 inetd CALL sigaction(0x1,0xbfbffb10,0) 11753 inetd RET sigaction 0 11753 inetd CALL getpeername(0xd,0xbfbff500,0xbfbff47c) 11753 inetd RET getpeername 0 11753 inetd CALL write(0x2,0xbfbfec84,0x1a) 11753 inetd GIO fd 2 wrote 26 bytes "/usr/libexec/ld-elf.so.1: " 11753 inetd RET write 26/0x1a 11753 inetd CALL write(0x2,0xbfbfecb4,0x26) 11753 inetd GIO fd 2 wrote 38 bytes "inetd: Undefined symbol "setproctitle"" 11753 inetd RET write 38/0x26 11753 inetd CALL write(0x2,0xbfbfec84,0x1) 11753 inetd GIO fd 2 wrote 1 byte " " 11753 inetd RET write 1 11753 inetd CALL exit(0x1) 11746 inetd PSIG SIGCHLD caught handler=3D0x804abbc mask=3D0x0 code=3D= 0x0 11746 inetd RET select -1 errno 4 Interrupted system call 11746 inetd CALL write(0xc,0xbfbff3b3,0x1) 11746 inetd GIO fd 12 wrote 1 byte "C" 11746 inetd RET write 1 11746 inetd CALL sigreturn(0xbfbff3f0) 11746 inetd RET sigreturn JUSTRETURN 11746 inetd CALL select(0xd,0xbfbff604,0,0,0) 11746 inetd RET select 1 11746 inetd CALL ioctl(0x3,FIONREAD,0xbfbff5cc) 11746 inetd RET ioctl 0 11746 inetd CALL read(0x3,0xbfbff5cb,0x1) 11746 inetd GIO fd 3 read 1 byte "C" 11746 inetd RET read 1 11746 inetd CALL wait4(0xffffffff,0xbfbff58c,0x1,0) 11746 inetd RET wait4 11753/0x2de9 11746 inetd CALL wait4(0xffffffff,0xbfbff58c,0x1,0) 11746 inetd RET wait4 -1 errno 10 No child processes 11746 inetd CALL select(0xd,0xbfbff604,0,0,0) --Multipart_Tue_Jan__2_12:21:45_2001-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 12:38:32 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 12:38:29 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from prince.kattare.com (prince.kattare.com [198.68.22.33]) by hub.freebsd.org (Postfix) with ESMTP id 2344C37B400 for ; Tue, 2 Jan 2001 12:38:29 -0800 (PST) Received: from RNJ.mail.veetvision.com ([202.9.134.163]) by prince.kattare.com (8.9.3/8.9.3) with ESMTP id MAA03263; Tue, 2 Jan 2001 12:38:15 -0800 Message-Id: <5.0.2.1.2.20010103020936.08932118@mail.veetvision.com> X-Sender: ravi.vvc@mail.veetvision.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 03 Jan 2001 02:10:47 +0530 To: "Vladimir V. Egorin" , freebsd-stable@FreeBSD.ORG From: Ravi Jethani Subject: Re: fetch problem In-Reply-To: <20010102132905.A15311@math.uic.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Vlad, At 01:29 PM 1/2/2001 -0600, Vladimir V. Egorin wrote: >Dear -STABLE Users, > >I ran into some problems with the ports collection (the system is >4.2-STABLE, built on Dec 21). My machine is sitting behind >a proxy server (proxying http/ftp requests). > >I've set >export FTP_PROXY=ftp://proxy_address:1080/ >export HTTP_PROXY=ftp://proxy_address:1080/ >I've also tried setting FTP_PASSIVE_MODE. just wondering how you can run an http and a ftp proxy on the same port ? cu Ravi >Fetch fails with the messages: > > >> libtool-1.3.4.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > >> Attempting to fetch from ftp://ftp.gnu.org/gnu/libtool/. >fetch: libtool-1.3.4.tar.gz: Protocol error > >Does anyone know why this is happening? >Many thanks, > >-- >Vladimir > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message ________________________________________________ VeetVision Communications (P) Ltd. Bungalow C-3, Moghul Gardens, 411001 Pune, India Tel. 91-20-6113056, 6051597, 6051598 / Fax 91-20-6050652 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 12:45:58 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 12:45:56 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id BF4F637B400 for ; Tue, 2 Jan 2001 12:44:47 -0800 (PST) Received: (qmail 9481 invoked from network); 2 Jan 2001 20:44:38 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 2 Jan 2001 20:44:38 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id CAA01209; Wed, 3 Jan 2001 02:43:49 +0600 Date: Wed, 3 Jan 2001 02:43:48 +0600 (NOVT) From: Alexey Dokuchaev To: Ravi Jethani Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fetch problem In-Reply-To: <5.0.2.1.2.20010103020936.08932118@mail.veetvision.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Jan 2001, Ravi Jethani wrote: > just wondering how you can run an http and a ftp proxy on the same port ? > Huh? What's wrong with proxy server processing both HTTP and FTP requests? Squid can do this, for instance. Nowadays, I would be pretty suprised to see two servers running on different ports (one for HTTP and another for FTP). ./danfe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 12:55: 7 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 12:55:05 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from math.uic.edu (galois.math.uic.edu [131.193.178.114]) by hub.freebsd.org (Postfix) with SMTP id 5C89737B400 for ; Tue, 2 Jan 2001 12:55:05 -0800 (PST) Received: (qmail 15721 invoked by uid 31415); 2 Jan 2001 20:54:49 -0000 Date: Tue, 2 Jan 2001 14:54:49 -0600 From: "Vladimir V. Egorin" To: Ravi Jethani Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fetch problem Message-ID: <20010102145448.A15700@math.uic.edu> References: <20010102132905.A15311@math.uic.edu> <5.0.2.1.2.20010103020936.08932118@mail.veetvision.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.2.1.2.20010103020936.08932118@mail.veetvision.com>; from ravi@veetvision.com on Wed, Jan 03, 2001 at 02:10:47AM +0530 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 02:10:47AM +0530, Ravi Jethani wrote: > Hi Vlad, > > At 01:29 PM 1/2/2001 -0600, Vladimir V. Egorin wrote: > >Dear -STABLE Users, > > > >I ran into some problems with the ports collection (the system is > >4.2-STABLE, built on Dec 21). My machine is sitting behind > >a proxy server (proxying http/ftp requests). > > > >I've set > >export FTP_PROXY=ftp://proxy_address:1080/ > >export HTTP_PROXY=ftp://proxy_address:1080/ > >I've also tried setting FTP_PASSIVE_MODE. > > just wondering how you can run an http and a ftp proxy on the same port ? > I made a typo here; the variables should read export FTP_PROXY=ftp://proxy_address:1080/ export HTTP_PROXY=http://proxy_address:1080/ This doesn't answer your question though. I am not sure how the proxy works (and I have no access to the machine that runs it), but I bet the local machine connects to the proxy on port 1080 and talks to it via some protocol (e.g. specifies the type of request involved (ftp or http)). -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 13:10:20 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 13:10:17 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail5.svr.pol.co.uk (mail5.svr.pol.co.uk [195.92.193.20]) by hub.freebsd.org (Postfix) with ESMTP id E7BD237B400 for ; Tue, 2 Jan 2001 13:10:16 -0800 (PST) Received: from modem-235.sulfur.dialup.pol.co.uk ([62.136.15.235] helo=omega.my.domain) by mail5.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14DYhC-0004Ze-00 for stable@freebsd.org; Tue, 02 Jan 2001 21:10:15 +0000 Received: from freeloader.freeserve.co.uk (alpha.my.domain [192.168.0.2]) by omega.my.domain (8.11.1/8.11.1) with ESMTP id f02LAP623853; Tue, 2 Jan 2001 21:10:31 GMT (envelope-from ianjhart@freeloader.freeserve.co.uk) Sender: ianjhart@omega.my.domain Message-ID: <3A5243C1.4314EDCB@freeloader.freeserve.co.uk> Date: Tue, 02 Jan 2001 21:10:25 +0000 From: ian j hart X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Vladimir V. Egorin" Cc: "stable@freebsd.org" Subject: Re: fetch problem References: <20010102132905.A15311@math.uic.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Vladimir V. Egorin" wrote: > > Dear -STABLE Users, > > I ran into some problems with the ports collection (the system is > 4.2-STABLE, built on Dec 21). My machine is sitting behind > a proxy server (proxying http/ftp requests). > > I've set > export FTP_PROXY=ftp://proxy_address:1080/ > export HTTP_PROXY=ftp://proxy_address:1080/ > I've also tried setting FTP_PASSIVE_MODE. > > Fetch fails with the messages: > > >> libtool-1.3.4.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > >> Attempting to fetch from ftp://ftp.gnu.org/gnu/libtool/. > fetch: libtool-1.3.4.tar.gz: Protocol error > > Does anyone know why this is happening? > Many thanks, > > -- > Vladimir Don't set FTP_PROXY. Set HTTP_PROXY something like this username:password@hostname.domain:port eg. setenv HTTP_PROXY proxy_address:1080 The prococol part of the URL is the problem I think. See man 3 fetch -- ian j hart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 13:34:32 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 13:34:30 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from saturn.home.ben.com (c1058885-a.bvrtn1.or.home.com [24.12.186.106]) by hub.freebsd.org (Postfix) with ESMTP id 5C86837B400 for ; Tue, 2 Jan 2001 13:34:30 -0800 (PST) Received: (from bjj@localhost) by saturn.home.ben.com (8.11.1/8.9.3) id f02LYJP86014; Tue, 2 Jan 2001 13:34:19 -0800 (PST) From: Ben Jackson Message-Id: <200101022134.f02LYJP86014@saturn.home.ben.com> Subject: another fetch quirk (was: fetch problem) In-Reply-To: <20010102132905.A15311@math.uic.edu> from "Vladimir V. Egorin" at "Jan 2, 2001 01:29:05 pm" To: "Vladimir V. Egorin" Date: Tue, 2 Jan 2001 13:34:19 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> libtool-1.3.4.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > >> Attempting to fetch from ftp://ftp.gnu.org/gnu/libtool/. > fetch: libtool-1.3.4.tar.gz: Protocol error Speaking of fetch, I think it should give more details in those error messages. One I hit from time to time is 'fetch: foo.tar.gz: Permission denied' which could be on the FTP server or it could just mean you can't write to /usr/ports/distfiles... --Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 13:37:53 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 13:37:51 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from math.uic.edu (galois.math.uic.edu [131.193.178.114]) by hub.freebsd.org (Postfix) with SMTP id 2E74137B400 for ; Tue, 2 Jan 2001 13:37:51 -0800 (PST) Received: (qmail 15866 invoked by uid 31415); 2 Jan 2001 21:37:22 -0000 Date: Tue, 2 Jan 2001 15:37:22 -0600 From: "Vladimir V. Egorin" To: ian j hart Cc: "stable@freebsd.org" Subject: Re: fetch problem Message-ID: <20010102153722.A15840@math.uic.edu> References: <20010102132905.A15311@math.uic.edu> <3A5243C1.4314EDCB@freeloader.freeserve.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A5243C1.4314EDCB@freeloader.freeserve.co.uk>; from ianjhart@freeloader.freeserve.co.uk on Tue, Jan 02, 2001 at 09:10:25PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 09:10:25PM +0000, ian j hart wrote: > "Vladimir V. Egorin" wrote: > > > > Dear -STABLE Users, > > > > I ran into some problems with the ports collection (the system is > > 4.2-STABLE, built on Dec 21). My machine is sitting behind > > a proxy server (proxying http/ftp requests). > > > > I've set > > export FTP_PROXY=ftp://proxy_address:1080/ > > export HTTP_PROXY=ftp://proxy_address:1080/ > > I've also tried setting FTP_PASSIVE_MODE. > > > > Fetch fails with the messages: > > > > >> libtool-1.3.4.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > > >> Attempting to fetch from ftp://ftp.gnu.org/gnu/libtool/. > > fetch: libtool-1.3.4.tar.gz: Protocol error > > > > Does anyone know why this is happening? > > Many thanks, > > > > -- > > Vladimir > > Don't set FTP_PROXY. Set HTTP_PROXY something like this > > username:password@hostname.domain:port > > eg. > setenv HTTP_PROXY proxy_address:1080 > > The prococol part of the URL is the problem I think. > > See man 3 fetch > > -- > ian j hart > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message This solves it. fetch works if FTP_PROXY is not set. Many thanks to everyone for your replies and help. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 13:49:19 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 13:49:15 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from prince.kattare.com (prince.kattare.com [198.68.22.33]) by hub.freebsd.org (Postfix) with ESMTP id 5A07F37B402 for ; Tue, 2 Jan 2001 13:49:14 -0800 (PST) Received: from RNJ.mail.veetvision.com ([202.9.134.163]) by prince.kattare.com (8.9.3/8.9.3) with ESMTP id NAA09820; Tue, 2 Jan 2001 13:48:43 -0800 Message-Id: <5.0.2.1.2.20010103031548.00aeeeb8@mail.veetvision.com> X-Sender: ravi.vvc@mail.veetvision.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 03 Jan 2001 03:20:57 +0530 To: Alexey Dokuchaev From: Ravi Jethani Subject: Re: fetch problem Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: References: <5.0.2.1.2.20010103020936.08932118@mail.veetvision.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:43 AM 1/3/2001 +0600, Alexey Dokuchaev wrote: >On Wed, 3 Jan 2001, Ravi Jethani wrote: > > > just wondering how you can run an http and a ftp proxy on the same port ? > > > >Huh? What's wrong with proxy server processing both HTTP and FTP >requests? Squid can do this, for instance. Nowadays, I would be pretty >suprised to see two servers running on different ports (one for HTTP and >another for FTP). Probably nothing. This input / question came out of curiosity and common logic, not experience. cu Ravi >./danfe > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message ________________________________________________ VeetVision Communications (P) Ltd. Bungalow C-3, Moghul Gardens, 411001 Pune, India Tel. 91-20-6113056, 6051597, 6051598 / Fax 91-20-6050652 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 13:53:25 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 13:53:22 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with SMTP id 1435C37B400 for ; Tue, 2 Jan 2001 13:53:21 -0800 (PST) Received: (qmail 57670 invoked by uid 501); 2 Jan 2001 21:53:17 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Jan 2001 21:53:17 -0000 Date: Tue, 2 Jan 2001 19:53:17 -0200 (EDT) From: Paulo Fragoso To: freebsd-stable@freebsd.org Subject: wi0 or isab0 trouble? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We was using FreeBSD and WaveLAN without problems. But now we are trying to use 4.2-20001219-STABLE and we are found some problems. We have got one PII 350MHz (chiset 440 BX motherboard) working fine, but using some old motherboards we get this error: wi0: device timeout wi0: failed to allocate 1594 bytes on NIC wi0: tx buffer allocation failed wi0: failed to alloacte 1594 bytes on NIC wi0: mgmt. buffer allocation failed That old motherboard has got the chipset VIA VT82C576M with a Pentium 100MHz. Looking at result from dmesg there is a little difference: work-> there are isab0 and isa0 at motherboard that works: isab0: at device 7.0 on pci0 isa0: on isab0 don't work-> there isn't isab0!!!: isa0: on isab0 We've got another older motherboard (chipset intel TX) working fine with FreeBSD 4.2-RELEASE, and we can found isab0 on dmesg: isab0: at device 7.0 on pci0 isa0: on isab0 Likely the wi0 require a isab0 (I think). Why when are we using FreeBSD 4.2-STABLE we can't found a isab0 on old motherboard? Why don't wi0 works? We've installed FreeBSD 4.1-RELEASE on same VIA motherboard to test and all works fine. But on that motherboard we can't found a isab0 with dmesg, too. Are we thinking wrong? When we are using same motherboard (VIA VT82C576M) with FBSD 4.1-RELEASE are all working fine? We've tested FBSD 4.2-RELEASE and 4.2-20001219-STABLE and both don't work on this motherboard. Finally: Why are all versions tested of FreeBSD working fine using a 440BX motherboard? Thanks, Paulo Fragoso. -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 13:59:43 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 13:59:41 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from public.ndh.com (public.ndh.net [195.94.90.21]) by hub.freebsd.org (Postfix) with ESMTP id 0032137B400 for ; Tue, 2 Jan 2001 13:59:40 -0800 (PST) Received: from localhost (port1104.duesseldorf.ndh.net [62.40.8.104]) by public.ndh.com (8.9.3/8.8.0) with ESMTP id WAA02816 for ; Tue, 2 Jan 2001 22:59:31 +0100 (MET) Received: from tmseck by localhost with local (Exim 3.20 #1) id 14DZUR-00009s-00 for freebsd-stable@freebsd.org; Tue, 02 Jan 2001 23:01:07 +0100 Date: Tue, 2 Jan 2001 23:01:07 +0100 From: Thomas Seck To: freebsd-stable@freebsd.org Subject: Vinum safe to use for raid 0? Message-ID: <20010102230107.A559@basildon.homerun> Mail-Followup-To: Thomas Seck , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Die Teilchenbeschleuniger Sender: Thomas Seck Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, sorry if this is OT for -stable, but I followed the discussion about vinum in here and got a bit worried. I am currently deploying a proxy server for our company. It shall use squid on 4.2-STABLE. I would like to put the cache data on a vinum RAID 0, made of three U160 disks. As I understood the discussion so far, there are some unresolved problems with the raid 5 code. Could someone tell me whether I can safely use vinum for building a raid 0 system (despite the fact that the HW may be a point of failure of course)? Thanks in advance and best regards from Germany -Thomas Seck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 14: 1:58 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 14:01:56 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from redsheriff.com (eagle.imrworldwide.com [203.89.243.235]) by hub.freebsd.org (Postfix) with ESMTP id B04A637B400 for ; Tue, 2 Jan 2001 14:01:54 -0800 (PST) Received: from skua.burren.cx (devfw.imrworldwide.com [203.89.243.232]) by redsheriff.com (8.9.3/8.9.3) with ESMTP id JAA32980 for ; Wed, 3 Jan 2001 09:01:42 +1100 (EST) (envelope-from david@burren.cx) Received: (qmail 596 invoked from network); 2 Jan 2001 22:01:15 -0000 Received: from localhost.local2 (HELO burren.cx) (127.0.0.1) by localhost.local2 with SMTP; 2 Jan 2001 22:01:15 -0000 Sender: davidb@redsheriff.com Message-ID: <3A524FAB.77C814C0@burren.cx> Date: Wed, 03 Jan 2001 09:01:15 +1100 From: David Burren X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Vladimir V. Egorin" Cc: ian j hart , "stable@freebsd.org" Subject: Re: fetch problem References: <20010102132905.A15311@math.uic.edu> <3A5243C1.4314EDCB@freeloader.freeserve.co.uk> <20010102153722.A15840@math.uic.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Vladimir V. Egorin" wrote: >>> I've set >>> export FTP_PROXY=ftp://proxy_address:1080/ >>> export HTTP_PROXY=http://proxy_address:1080/ >>> I've also tried setting FTP_PASSIVE_MODE. > ian j hart wrote: >> setenv HTTP_PROXY proxy_address:1080 > This solves it. fetch works if FTP_PROXY is not set. Many thanks to > everyone for your replies and help. Unfortunately, over time different programs have looked for different env vars to control this. The setup I use that seems to work for everything is (translated to your example): export HTTP_PROXY=proxy_address:1080 export http_proxy=http://$HTTP_PROXY/ export ftp_proxy=$http_proxy If you were specifying $ftp_proxy to point to a joint FTP/HTTP proxy, you would typically specify that it should use "http" to talk to it. As you said, fetch works with just HTTP_PROXY. I think it's lynx which uses the other variables. I set them up a long time ago and everything just works. __ David Burren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 14:11:54 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 14:11:52 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.6.9.33]) by hub.freebsd.org (Postfix) with ESMTP id 04F7237B400 for ; Tue, 2 Jan 2001 14:11:52 -0800 (PST) Received: from msgrel1.and.agilent.com (msgrel1.and.agilent.com [130.30.33.104]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id 04277275 for ; Tue, 2 Jan 2001 15:11:50 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.and.agilent.com (Postfix) with ESMTP id AD6692D6 for ; Tue, 2 Jan 2001 17:07:41 -0500 (EST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id OAA19078 for ; Tue, 2 Jan 2001 14:07:40 -0800 (PST) Message-Id: <200101022207.OAA19078@mina.soco.agilent.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: tcp wrappers, inetd, & setproctitle() ??? Reply-To: Darryl Okahata In-Reply-To: Your message of "Tue, 02 Jan 2001 12:21:46 PST." <200101022021.MAA16583@mina.soco.agilent.com> Mime-Version: 1.0 (generated by tm-edit 1.6) Content-Type: text/plain; charset=US-ASCII Date: Tue, 02 Jan 2001 14:07:40 -0800 From: Darryl Okahata Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > Are there any known problems with tcp wrappers in FreeBSD > 4.2-RELEASE? (Yes, I've looked through the archives and dejanews and > can't find anything.) Never mind. The install is really screwed up. How, I don't know, but I can fix this. Sorry for the false alarm. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 14:13:26 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 14:13:24 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id D15C537B400 for ; Tue, 2 Jan 2001 14:13:23 -0800 (PST) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.1/8.11.1) with ESMTP id f02MDGB79386 for ; Tue, 2 Jan 2001 17:13:17 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.1.4.0.20010102140958.01c61700@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Tue, 02 Jan 2001 16:56:12 -0500 To: stable@freebsd.org From: Mike Tancsa Subject: sendmail and bind resolver options strangeness on STABLE Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure if this is specifically a sendmail or bind issue or a FreeBSD issue. But when sending email to a domain that is LAME (e.g. supercom.ca) where the 2 authoritative name servers are giving non authoritative answers, I want to send mail to it anyways. Using the same rev of sendmail on a lINUX box works in conjunction with asking the FreeBSD nameserver. Any idea why sendmail 8.11 on FreeBSD would be more strict than the same rev on Linux ? # name resolver options #O ResolverOptions=+AAONLY ResolverOptions=-AAONLY or ResolverOptions= Does not seem to have any effect. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 14:38: 7 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 14:38:04 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from math.uic.edu (galois.math.uic.edu [131.193.178.114]) by hub.freebsd.org (Postfix) with SMTP id 4255537B400 for ; Tue, 2 Jan 2001 14:38:04 -0800 (PST) Received: (qmail 15973 invoked by uid 31415); 2 Jan 2001 22:37:46 -0000 Date: Tue, 2 Jan 2001 16:37:46 -0600 From: "Vladimir V. Egorin" To: David Burren Cc: ian j hart , "stable@freebsd.org" Subject: Re: fetch problem Message-ID: <20010102163746.A15961@math.uic.edu> References: <20010102132905.A15311@math.uic.edu> <3A5243C1.4314EDCB@freeloader.freeserve.co.uk> <20010102153722.A15840@math.uic.edu> <3A524FAB.77C814C0@burren.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A524FAB.77C814C0@burren.cx>; from david@burren.cx on Wed, Jan 03, 2001 at 09:01:15AM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 09:01:15AM +1100, David Burren wrote: > "Vladimir V. Egorin" wrote: > > >>> I've set > >>> export FTP_PROXY=ftp://proxy_address:1080/ > >>> export HTTP_PROXY=http://proxy_address:1080/ > >>> I've also tried setting FTP_PASSIVE_MODE. > > > ian j hart wrote: > > >> setenv HTTP_PROXY proxy_address:1080 > > > This solves it. fetch works if FTP_PROXY is not set. Many thanks to > > everyone for your replies and help. > > Unfortunately, over time different programs have looked for different > env vars to control this. The setup I use that seems to work for > everything is (translated to your example): > > export HTTP_PROXY=proxy_address:1080 > export http_proxy=http://$HTTP_PROXY/ > export ftp_proxy=$http_proxy > > If you were specifying $ftp_proxy to point to a joint FTP/HTTP proxy, > you would typically specify that it should use "http" to talk to it. > > As you said, fetch works with just HTTP_PROXY. I think it's lynx which > uses the other variables. I set them up a long time ago and everything The other variables (http_proxy and ftp_proxy) are also used by ftp. Here is another problem: I cannot use /usr/bin/ftp with this setup. For lynx, fetch, the proxy does DNS resolution, but ftp calls gethostbyname(), which fails for any addresses that are not a part of internal network. > just works. > __ > David Burren -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 15:21:16 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 15:21:12 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3C11E37B400 for ; Tue, 2 Jan 2001 15:21:12 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f02NLAi06074; Tue, 2 Jan 2001 15:21:10 -0800 (PST) Date: Tue, 2 Jan 2001 15:21:10 -0800 From: Alfred Perlstein To: Thomas Seck Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? Message-ID: <20010102152109.D19572@fw.wintelcom.net> References: <20010102230107.A559@basildon.homerun> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010102230107.A559@basildon.homerun>; from tmseck@web.de on Tue, Jan 02, 2001 at 11:01:07PM +0100 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Thomas Seck [010102 14:00] wrote: > Hi all, > > sorry if this is OT for -stable, but I followed the discussion about > vinum in here and got a bit worried. > > I am currently deploying a proxy server for our company. It shall use > squid on 4.2-STABLE. I would like to put the cache data on a vinum RAID > 0, made of three U160 disks. As I understood the discussion so far, > there are some unresolved problems with the raid 5 code. Could someone > tell me whether I can safely use vinum for building a raid 0 system > (despite the fact that the HW may be a point of failure of course)? > > Thanks in advance and best regards from Germany We've been using RAID-0 and RAID-1 with vinum here for a long time, the only problem we had was during a 3.x->4.x upgrade, we were able to recover from it after freaking out for a bit though. So yes, it is stable. I still wouldn't trust the RAID-5, but if you want to get RAID-5 working you could take a shot on getting some reproducable corruption/panics and let Greg know. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 15:38:44 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 15:38:42 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 66C1D37B400 for ; Tue, 2 Jan 2001 15:38:42 -0800 (PST) Received: from bluto.jimking.net (root@bluto.jimking.net [216.54.255.8]) by cgi.sstar.com (8.11.1/8.11.1) with ESMTP id f02NccE65340 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Tue, 2 Jan 2001 17:38:41 -0600 (CST) (envelope-from jim@jimking.net) Received: from marble (marble.lgc.com [134.132.228.4]) by bluto.jimking.net (8.11.1/8.11.1) with SMTP id f02NcYo87567; Tue, 2 Jan 2001 17:38:35 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <004101c07515$206f9340$04e48486@marble> From: "Jim King" To: "Erich Zigler" , References: <20010102131012.A1922@superhero.org> Subject: Re: Threaded C++ Question Date: Tue, 2 Jan 2001 17:38:33 -0600 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Erich Zigler" wrote: > In reading through the archives I have seen several emails regarding the > problems people have experienced with MySQL, and Mozilla on 4.2 systems. I > was wondering if these problems have been resolved in the main source tree > yet. I'd like to know too. I plan on tackling Mozilla this weekend; it would be nice if it was a no-brainer. :-) Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 15:51: 3 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 15:51:00 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id 51C5C37B400 for ; Tue, 2 Jan 2001 15:51:00 -0800 (PST) Received: (qmail 83933 invoked from network); 2 Jan 2001 23:50:58 -0000 Received: from unknown (HELO prydn.tacni.net) (207.55.167.31) by 216.178.136.168 with SMTP; 2 Jan 2001 23:50:58 -0000 Received: (qmail 44023 invoked by uid 1001); 2 Jan 2001 23:50:34 -0000 Date: Tue, 2 Jan 2001 17:50:34 -0600 From: Erich Zigler To: freebsd-stable@FreeBSD.ORG Subject: Re: Threaded C++ Question Message-ID: <20010102175034.B43962@superhero.org> Mail-Followup-To: Erich Zigler , freebsd-stable@FreeBSD.ORG References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004101c07515$206f9340$04e48486@marble>; from jim@jimking.net on Tue, Jan 02, 2001 at 05:38:33PM -0600 X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: needo@prydn.tacni.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 05:38:33PM -0600, Jim King wrote: > > In reading through the archives I have seen several emails regarding the > > problems people have experienced with MySQL, and Mozilla on 4.2 systems. I > > was wondering if these problems have been resolved in the main source tree > > yet. > I'd like to know too. I plan on tackling Mozilla this weekend; it would be > nice if it was a no-brainer. :-) To my knowledge they modified the Mozilla port to work around it. But I am in the process of porting several C++ apps that are exhibiting truely strange behavior. And I was wondering if this could be the cause. -- Erich Zigler You're asking a bunch of sysadmins if anyone remembers how to tie hangman's noose, and _not_ expecting positive responses? -Anthony DeBoer in the SDM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 16: 6:30 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 16:06:27 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id A4B2937B400 for ; Tue, 2 Jan 2001 16:06:25 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id AA3296A911; Wed, 3 Jan 2001 10:36:21 +1030 (CST) Date: Wed, 3 Jan 2001 10:36:21 +1030 From: Greg Lehey To: Josef Karthauser , Matraquilla@cs.com, Roman Shterenzon , freebsd-stable@FreeBSD.ORG Subject: RAID-5 reliability (was: vinum malfunction!) Message-ID: <20010103103621.G40453@wantadilla.lemis.com> References: <20010102140616.B1391@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010102140616.B1391@tao.org.uk>; from joe@tao.org.uk on Tue, Jan 02, 2001 at 02:06:16PM +0000 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 2 January 2001 at 14:06:16 +0000, Josef Karthauser wrote: > > The problem with vinum RAID5 in -stable is that in my experience > there are some nasty bugs in it, Well, one nasty bug. > and I don't believe that Greg has managed to reproduce these himself > and so is a bit confused as to what is causing the trouble. Well, I don't know if I'd use the word "confused". More "uninformed". > I'm worried that he may be inclined to believe that it is only a > small minority of people who are having problems with this. I would > challange this view because I don't know _anyone_ who is > successfully using RAID5 under vinum. They've all migrated away to > using dedicated hardware and thus solved their vinum problems that > way. Yes, I do believe it's a small minority of people. I have had exactly four reports of this problem, yours included. In none of the cases have I been able to get enough information to reproduce it. On the other hand, I know plenty of people who are successfully using RAID-5. > I don't know what it's going to take for Greg to get enough > information to fix the problem. I spent a week trying to extract a > set of debug information for him that was useful enough that he > could work from it, but it seems that my week was just wasted > because it looks like I didn't capture the bug that he was expecting > :(. Well, it's not wasted, but it didn't help enough. As I said, it's elusive. If anybody else out there has experienced the following problem, please contact me: The system runs fine most of the time, but under heavy load it dies with a trap 12 (page fault in kernel mode). The dump shows the system is trying to call the specific iodone routine from biodone. More careful analysis shows that the buffer header in question has had some fields zeroed out. > To summarise. The idea of software raid 5 is great, but it's got to > work otherwise it is dangerous. Like anything else. Note that a large number of these comments could apply equally well to soft updates: it worked fine for most people, but a small minority of people have had trouble with it. > I note that the BUGS section of the manual page doesn't exist. > There should be a warning to potential users that there are known > problems that can cause the data to become corrupted in some > configurations. It looks as if you have missed it: BUGS 1. vinum is a new product. Bugs can be expected. The configuration mechanism is not yet fully functional. If you have difficulties, please look at the section DEBUGGING PROBLEMS WITH VINUM before re- porting problems. 2. Kernels with the vinum pseudo-device appear to work, but are not supported. If you have trouble with this configuration, please first replace the kernel with a non-Vinum kernel and test with the kld module. 3. Detection of differences between the version of the kernel and the kld is not yet implemented. 4. The RAID-5 functionality is new in FreeBSD 3.3. Some problems have been reported with vinum in combination with soft updates, but these are not reproducible on all systems. If you are planning to use vinum in a production environment, please test carefully. Looking at this, I suppose it should be updated. But the section definitely exists. 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-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 16:17:32 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 16:17:29 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 1FD0137B400 for ; Tue, 2 Jan 2001 16:17:27 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id B7F7C6A911; Wed, 3 Jan 2001 10:47:24 +1030 (CST) Date: Wed, 3 Jan 2001 10:47:24 +1030 From: Greg Lehey To: Roman Shterenzon Cc: "Michael C . Wu" , freebsd-stable@FreeBSD.ORG Subject: Re: vinum malfunction! Message-ID: <20010103104724.H40453@wantadilla.lemis.com> References: <20001231101426.K99806@wantadilla.lemis.com> <20010102092819.K44043@wantadilla.lemis.com> <978425185.3a519561dbcdb@webmail.harmonic.co.il> <20010102193241.C40453@wantadilla.lemis.com> <978427080.3a519cc850a45@webmail.harmonic.co.il> <20010102034408.B56810@peorth.iteration.net> <978438556.3a51c99cea732@webmail.harmonic.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <978438556.3a51c99cea732@webmail.harmonic.co.il>; from roman@harmonic.co.il on Tue, Jan 02, 2001 at 02:29:16PM +0200 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] On Tuesday, 2 January 2001 at 14:29:16 +0200, Roman Shterenzon wrote: > Quoting "Michael C . Wu" : >> On Tue, Jan 02, 2001 at 11:18:00AM +0200, Roman Shterenzon scribbled: >>> Quoting Greg Lehey : >>> 3) I was trying to say that saying "too much text doesn't allow me >>> to work on it" is an EXCUSE. The PR had the needed information and >>> it wasn't mutilated. Perhaps you think that this bug seldom >>> occures, or, perhaps you have some other reason. Well, I've explained this already. Yes, it's relatively rare. And your PR is really as good as illegible. >>> 4) RAID-5 cost our company enormous down-time and cost me >>> personally my health. This is why I think it's dangerous and I >>> want to warn others until this bug is fixed. Under those circumstances, wouldn't it have been more appropriate to supply the information I've asked for. >> It's documented. > > Where? I asked to document it, but haven't seen it documented. If > it's already documented, then I'm happy. In the man page, where it belongs. I posted it in answer to Joe Karthauser's message >>> 5) I'm using webmail, thus I'm unable to control the format of the >>> sent mail. >>> Sorry. >> >> You are a consultant, and you should be able to find a real MUA for >> your work. > > I'm happy that you know what I should and shouldn't know better than > me. As Michael says, sarcasm doesn't help, especially when you use it to make up for any real reason. It certainly doesn't say much for your professionalism if you use toy mailers. I have spent about 5 minutes recovering this message to make it legible again. Have you considered what people think when they receive such badly prepared documentation? Normally I just throw away that kind of message unread, but I still have hope that I might be able to get some information out of this affair. >>> 6) If it's so hard to you to dig valuable information from PR >>> 22103, I can do it by myself and resubmit it. Will this make any >>> difference? Yes, assuming the information is there. >> I read PR/22103, and I don't think you did submit the necessary >> information. > > What's missing? Be constructive, not destructive Well, I have told you several times. For a least the third time: take a look at http://www.vinumvm.org/vinum/how-to-debug.html and supply the information I ask for, no more, no less. Ensure that it is legible. > What did irritate me is that greg mailed the other person and told > him to send a report. My and another person's reports weren't > considered at all. Well, an obvious reason for that is that the problems had nothing to do with each other. The other guy didn't have any crashes, any data corruption, and he wasn't using RAID-5. He just couldn't start Vinum, and he didn't give any information. Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html 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-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 16:29:42 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 16:29:41 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from harumscarum.mr.itd.umich.edu (harumscarum.mr.itd.umich.edu [141.211.125.17]) by hub.freebsd.org (Postfix) with ESMTP id DBF7F37B400 for ; Tue, 2 Jan 2001 16:29:40 -0800 (PST) Received: from tim.elnsng1.mi.home.com (c1129767-a.elnsng1.mi.home.com [24.183.248.20]) by harumscarum.mr.itd.umich.edu (8.9.3/3.3s) with SMTP id TAA00632; Tue, 2 Jan 2001 19:29:19 -0500 (EST) From: Tim McMillen To: Greg Lehey , Josef Karthauser , Matraquilla@cs.com, Roman Shterenzon , freebsd-stable@FreeBSD.ORG Subject: Re: RAID-5 reliability (was: vinum malfunction!) Date: Tue, 2 Jan 2001 19:33:02 -0500 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" References: <20010102140616.B1391@tao.org.uk> <20010103103621.G40453@wantadilla.lemis.com> In-Reply-To: <20010103103621.G40453@wantadilla.lemis.com> MIME-Version: 1.0 Message-Id: <0101021933020E.19598@tim.elnsng1.mi.home.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday January 02, 2001 19:06, Greg Lehey wrote: > > I note that the BUGS section of the manual page doesn't exist. > > There should be a warning to potential users that there are known > > problems that can cause the data to become corrupted in some > > configurations. > > It looks as if you have missed it: Hmm. This bugs section is only in vinum(4), but not in vinum(8) I did not even realize vinum(4) existed and it seems others did not either because man vinum takes one to vinum(8) Perhaps the bugs section could be updated and added to vinum(8)? Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 16:48:54 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 16:48:53 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 0E9A437B400 for ; Tue, 2 Jan 2001 16:48:52 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f030kut71102; Tue, 2 Jan 2001 20:46:56 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 2 Jan 2001 20:46:55 -0400 (AST) From: The Hermit Hacker To: Tim McMillen Cc: Greg Lehey , Josef Karthauser , , Roman Shterenzon , Subject: Re: RAID-5 reliability (was: vinum malfunction!) In-Reply-To: <0101021933020E.19598@tim.elnsng1.mi.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ummmm, at the bottom of 'vinum(8)', it states in the 'See Also' section 'vinum(4)' ... On Tue, 2 Jan 2001, Tim McMillen wrote: > On Tuesday January 02, 2001 19:06, Greg Lehey wrote: > > > > I note that the BUGS section of the manual page doesn't exist. > > > There should be a warning to potential users that there are known > > > problems that can cause the data to become corrupted in some > > > configurations. > > > > It looks as if you have missed it: > > > Hmm. This bugs section is only in vinum(4), but not in vinum(8) > I did not even realize vinum(4) existed and it seems others did not > either because man vinum takes one to vinum(8) Perhaps the bugs > section could be updated and added to vinum(8)? > > > Tim > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 16:55:51 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 16:55:50 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id B8F2037B400 for ; Tue, 2 Jan 2001 16:55:49 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id tsmsaaaa for ; Wed, 3 Jan 2001 12:03:53 +1100 Message-ID: <3A5278C0.9042B414@quake.com.au> Date: Wed, 03 Jan 2001 11:56:32 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-stable@FreeBSD.ORG Subject: Re: RAID-5 reliability (was: vinum malfunction!) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > > Ummmm, at the bottom of 'vinum(8)', it states in the 'See Also' section > 'vinum(4)' ... > > > Hmm. This bugs section is only in vinum(4), but not in vinum(8) > > I did not even realize vinum(4) existed and it seems others did not > > either because man vinum takes one to vinum(8) Perhaps the bugs > > section could be updated and added to vinum(8)? Yes its usually a good idea to read the pages listed in the "See Also" section... Its not like its a rare thing that a man page exists under the same name in different sections... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 16:57:40 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 16:57:38 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158]) by hub.freebsd.org (Postfix) with ESMTP id 1353B37B400 for ; Tue, 2 Jan 2001 16:57:37 -0800 (PST) Received: (from wkt@localhost) by henry.cs.adfa.edu.au (8.11.1/8.9.3) id f03143902756 for stable@freebsd.org; Wed, 3 Jan 2001 12:04:03 +1100 (EST) (envelope-from wkt) From: Warren Toomey Message-Id: <200101030104.f03143902756@henry.cs.adfa.edu.au> Subject: kldload: Exec format error, is 4.2 problem? To: stable@freebsd.org Date: Wed, 3 Jan 2001 12:04:02 +1100 (EST) Reply-To: wkt@cs.adfa.edu.au X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Just did a CVS on 4.x src-sys, make buildworld, make buildkernel, make installkernel, reboot, make installworld, mergemaster, reboot. I'm trying to load the modules required for vmware2 after building from the 4.2 port of vmware2 and rtc after rebooting to 4.2-STABLE. I see: # kldload /usr/local/modules/rtc.ko kldload: can't load /usr/local/modules/rtc.ko: Exec format error Fortunately, I kept a copy of rtc.ko from before the rebuild, and it loads fine. -r-xr-xr-x 1 root wheel 6087 Jan 3 12:00 good_rtc.ko -r-xr-xr-x 1 root wheel 6095 Jan 3 12:02 rtc.ko I also can't load vmmon.ko nor vmnet.ko, same problem. Is this a 4.2-thing, or have I just done something wrong? I've searched the FreeBSD mail lists for clues, with no luck. Feel free to point out an act of gross stupidity on my part :-) Warren P.S I also see this message during the compile of rtc.ko: dev2unit() not found in sys/kern/kern_conf.c. Using lminor() instead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 17:21:26 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 17:21:24 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id CEA8B37B400 for ; Tue, 2 Jan 2001 17:21:23 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f031L2p00435; Tue, 2 Jan 2001 19:21:07 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101030121.f031L2p00435@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Rune Mossige" Cc: heckfordj@psi-domain.co.uk, freebsd-stable@FreeBSD.ORG From: David Kelly Subject: Re: ASUS A7V and promise problems, SOLVED In-reply-to: Message from "Rune Mossige" of "Tue, 02 Jan 2001 18:32:37 +0100." <005b01c074e2$03d9a500$2aa17dd4@kleppst.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Jan 2001 19:21:02 -0600 Sender: dkelly@grumpy.dyndns.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rune Mossige" writes: > My problems about the promise appears to have been solved....it was an IRQ > conflict between the 3COM 3C905C and the onboard USB controller, both using > irq5. Why this caused the disks on the promise (irq 10) to fail, I do not > know.....Now I just ned to figure out how to get all adapters (SoundBlaster > Live!, 3com network adapter and RIVA TNT AGP adapter) to coexist happily > with their own IRQ's. Yeah, but! PCI stuff isn't supposed to have problems sharing IRQ's. Apparently this isn't completely true in practice. Then again there is too much stuff in there not to. Two UHCI controllers and 3 UHCI hubs. I bought a Maxtor 45G ATA-100 7200 RPM drive in December when Staples offered it for $180 with an external USB Zip 100 drive thrown in for free. Then took Maxtor up on their ATA-100 PCI card rebate of $50 resulting in a net cost of sales tax, time, and postage. For my PPro-200 which had only an ATA-16 on the MB. Lasted about a week before being nuked by lightning. But didn't take long to find out the Promise controller and/or FreeBSD 4.2-stable didn't like fxp0, sym0, ahc0, and the Promise/Maxtor ATA-100 card all on the same IRQ. So I moved the ATA-100 off and resulted in a happy system. Now I too have an Asus A7V with built-in Promise. I boot off SCSI. Left a couple of blank 4G partitions at the start of the 45G disk that I could play with if your problems persist. The Award BIOS does the darndest things in assigning IRQ's. Sym0 on IRQ 3? Have not managed to get the SB128 where FreeBSD could assign its register space until I disabled "PnP OS" in the BIOS so that the cards are now configured prior to the handoff to the FreeBSD kernel. Now FreeBSD completely sees the SB card! Soon to be making noise! And I'm back to playing the Booting For Interupts Game(tm) where one randomly does things in the BIOS, boots, notes what changed, reboots and repeats until its right. Want to get that Promise controller off of any one else's IRQ. Other than the IRQ stuff and SB card, the only issue with my 1004D BIOS is that only last night did I finally convince myself the chipset does not support ECC SDRAM. At least a little put off as I paid for same. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 17:30:20 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 17:30:18 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id A80EF37B400 for ; Tue, 2 Jan 2001 17:30:16 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id C37736A911; Wed, 3 Jan 2001 12:00:13 +1030 (CST) Date: Wed, 3 Jan 2001 12:00:13 +1030 From: Greg Lehey To: Tim McMillen Cc: Josef Karthauser , Matraquilla@cs.com, Roman Shterenzon , freebsd-stable@FreeBSD.ORG Subject: Re: RAID-5 reliability (was: vinum malfunction!) Message-ID: <20010103120013.C15003@wantadilla.lemis.com> References: <20010102140616.B1391@tao.org.uk> <20010103103621.G40453@wantadilla.lemis.com> <0101021933020E.19598@tim.elnsng1.mi.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <0101021933020E.19598@tim.elnsng1.mi.home.com>; from timcm@umich.edu on Tue, Jan 02, 2001 at 07:33:02PM -0500 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 2 January 2001 at 19:33:02 -0500, Tim McMillen wrote: > On Tuesday January 02, 2001 19:06, Greg Lehey wrote: > >>> I note that the BUGS section of the manual page doesn't exist. >>> There should be a warning to potential users that there are known >>> problems that can cause the data to become corrupted in some >>> configurations. >> >> It looks as if you have missed it: > > > Hmm. This bugs section is only in vinum(4), but not in > vinum(8) Correct. Vinum *is* vinum(4). > I did not even realize vinum(4) existed and it seems others did not > either because man vinum takes one to vinum(8) Perhaps the bugs > section could be updated and added to vinum(8)? No, as the man page says: vinum(4): vinum - Logical Volume Manager vinum(8): vinum - Logical Volume Manager control program What we're talking about here is vinum(4), not vinum(8). On each page, the SEE ALSO points at the other page. I can appreciate that some people miss one of the pages, but that doesn't mean that we should break the structure of the manual. 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-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 17:42:18 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 17:42:10 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hand.dotat.at (sfo-gw.covalent.net [207.44.198.62]) by hub.freebsd.org (Postfix) with ESMTP id 66C8C37B400; Tue, 2 Jan 2001 17:42:09 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 14DcwK-000DDW-00; Wed, 03 Jan 2001 01:42:08 +0000 Date: Wed, 3 Jan 2001 01:42:08 +0000 From: Tony Finch To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ESS Sound Driver Message-ID: <20010103014208.A45748@hand.dotat.at> References: <20001219031420.D30096@hand.dotat.at> <200012261447.eBQEl6j86193@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200012261447.eBQEl6j86193@mass.osd.bsdi.com> Organization: Covalent Technologies, Inc Sender: fanf@dotat.at Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: >> >> And on some machines it prevents the mouse from working properly >> because if it is listed by PNP before the keyboard controller, FreeBSD >> marks the mouse's bus resources as in use by an unknown device so when >> the mouse driver later tries to get IRQ 12 it fails. No one has a fix >> for this problem. > >Er, this doesn't make any sense. I can see there's a potential for a >conflict in this scenario because the keyboard controller driver is not >properly PnP-aware (it needs hints because it has to be up and running >early), but what you're saying doesn't seem to make sense. My reasoning is based on the bootverbose output from dmesg (included below from a system that doesn't exhibit the problem). On a Dell Optiplex GX110 which does have the problem, the PNP0f13 lines come before the PNP0303 lines (in the first section) and the keyboard probe messages (in the second section), and in the latter case (after "probing PnP devices") the PNP0f13 device grabs irq 12 before psm gets a look in. I don't have an Optiplex with FreeBSD on at the moment, sorry. [...] pnpbios: 13 devices, largest 118 bytes PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x2 PNP0a03: end config pnpbios: handle 0 device ID PNP0a03 (030ad041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0x100000-0x7ffffff, size=0x7f00000 PNP0c01: adding fixed memory32 range 0xf0000-0xfffff, size=0x10000 PNP0c01: adding fixed memory32 range 0xfffe0000-0xffffffff, size=0x20000 PNP0c01: adding fixed memory32 range 0x100a0000-0x100fffff, size=0x60000 PNP0c01: adding io range 0x800-0x83f, size=0x40, align=0x1 PNP0c01: adding io range 0x840-0x84f, size=0x10, align=0x1 PNP0c01: adding io range 0x880-0x88f, size=0x10, align=0x1 PNP0c01: adding io range 0x3f0-0x3f1, size=0x2, align=0x1 PNP0c01: adding io range 0xe0-0xe1, size=0x2, align=0x1 PNP0c01: end config pnpbios: handle 1 device ID PNP0c01 (010cd041) PNP0c01: adding fixed memory32 range 0xed000000-0xedffffff, size=0x1000000 PNP0c01: adding io range 0xf400-0xf4fe, size=0xff, align=0x1 PNP0c01: end config pnpbios: handle 2 device ID PNP0c01 (010cd041) PNP0000: adding irq mask 00x4 PNP0000: adding io range 0x20-0x3f, size=0x20, align=0x1 PNP0000: adding io range 0xa0-0xbf, size=0x20, align=0x1 PNP0000: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0000: end config pnpbios: handle 3 device ID PNP0000 (0000d041) PNP0100: adding irq mask 00x1 PNP0100: adding io range 0x40-0x5f, size=0x20, align=0x1 PNP0100: end config pnpbios: handle 4 device ID PNP0100 (0001d041) PNP0200: adding io range 0x80-0x9f, size=0x20, align=0x1 PNP0200: adding io range 0-0x1f, size=0x20, align=0x1 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 PNP0200: adding dma mask 0x10 PNP0200: end config pnpbios: handle 5 device ID PNP0200 (0002d041) PNP0303: adding irq mask 00x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 PNP0303: end config pnpbios: handle 6 device ID PNP0303 (0303d041) PNP0f13: adding irq mask 0x1000 PNP0f13: end config pnpbios: handle 7 device ID PNP0f13 (130fd041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 PNP0800: end config pnpbios: handle 8 device ID PNP0800 (0008d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x7f, size=0x10, align=0x1 PNP0b00: end config pnpbios: handle 9 device ID PNP0b00 (000bd041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: end config pnpbios: handle 10 device ID PNP0c04 (040cd041) PNP0e03: adding irq mask 0x200 PNP0e03: adding io range 0x3e0-0x3e1, size=0x2, align=0x1 PNP0e03: end config pnpbios: handle 11 device ID PNP0e03 (030ed041) PNP0700: adding irq mask 0x40 PNP0700: adding io range 0x3f2-0x3f5, size=0x4, align=0x2 PNP0700: adding io range 0x3f7-0x3f7, size=0x1, align=0x8 PNP0700: adding dma mask 0x4 PNP0700: end config pnpbios: handle 15 device ID PNP0700 (0007d041) [...] isa_probe_children: probing PnP devices unknown: failed to probe at port 0xcf8-0xcff on isa0 unknown: failed to probe at port 0x800-0x83f,0x840-0x84f,0x880-0x88f,0x3f0-0x3f1,0xe0-0xe1 iomem unknown: failed to probe at port 0xf400-0xf4fe iomem 0xed000000-0xedffffff on isa0 unknown: can't assign resources unknown: at port 0x20-0x3f,0xa0-0xbf,0x4d0-0x4d1 irq 2 on isa0 unknown: failed to probe at port 0x40-0x5f irq 0 on isa0 unknown: failed to probe at port 0x80-0x9f,0-0x1f,0xc0-0xdf drq 4 on isa0 atkbdc0: at port 0x60,0x64 irq 1 on isa0 atkbd0: irq 1 on atkbdc0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 00 00 psm: status 22 02 14 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0-00, 2 buttons psm0: config:00006000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 unknown: can't assign resources unknown: at irq 12 on isa0 unknown: failed to probe at port 0x61 on isa0 unknown: failed to probe at port 0x70-0x7f irq 8 on isa0 unknown: failed to probe at port 0xf0-0xff irq 13 on isa0 pcic0: at port 0x3e0-0x3e1 irq 9 on isa0 pcic0: management irq 9 stat is 0 stat is 0 pccard0: on pcic0 pccard1: on pcic0 unknown: failed to probe at port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on isa0 BIOS Geometries: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. [...] Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at "And remember my friend, future events such as these will affect you in the future." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 18:31:15 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 18:31:12 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shalimar.net.au (shalimar.net.au [198.142.161.98]) by hub.freebsd.org (Postfix) with ESMTP id 8C87037B400 for ; Tue, 2 Jan 2001 18:31:10 -0800 (PST) Received: from shalimar.net.au (localhost [127.0.0.1]) by shalimar.net.au (8.11.1/8.11.1) with SMTP id f032Up803984; Wed, 3 Jan 2001 13:30:51 +1100 (EST) (envelope-from count@shalimar.net.au) From: Zero Sum Organization: Tobacco Chewers and Body Painters Association. Date: Wed, 3 Jan 2001 13:30:50 +1100 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" Cc: freebsd-stable@FreeBSD.ORG To: Alfred Perlstein , Thomas Seck References: <20010102230107.A559@basildon.homerun> <20010102152109.D19572@fw.wintelcom.net> In-Reply-To: <20010102152109.D19572@fw.wintelcom.net> Subject: Re: Vinum safe to use for raid 0? MIME-Version: 1.0 Message-Id: <01010313305000.03936@shalimar.net.au> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday 03 January 2001 10:21, Alfred Perlstein wrote: >* Thomas Seck [010102 14:00] wrote: >> Hi all, >> >> sorry if this is OT for -stable, but I followed the discussion about >> vinum in here and got a bit worried. >> >> I am currently deploying a proxy server for our company. It shall use >> squid on 4.2-STABLE. I would like to put the cache data on a vinum RAID >> 0, made of three U160 disks. As I understood the discussion so far, >> there are some unresolved problems with the raid 5 code. Could someone >> tell me whether I can safely use vinum for building a raid 0 system >> (despite the fact that the HW may be a point of failure of course)? >> >> Thanks in advance and best regards from Germany > >We've been using RAID-0 and RAID-1 with vinum here for a long time, >the only problem we had was during a 3.x->4.x upgrade, we were able >to recover from it after freaking out for a bit though. > I know it is a bit off topic and if it has been discussed to death befire, I apologise. But for the lfe of me I can't see why anyone would use RAID 5 as other than an acadaemic exercise. If this seems like a troll, I'm sorry, but I have had this argument so many time in RL. In the past I have always managed to get better performance by throwing RAID 5 out. >So yes, it is stable. I still wouldn't trust the RAID-5, but if >you want to get RAID-5 working you could take a shot on getting >some reproducable corruption/panics and let Greg know. > The lack of data may be because of it's lack of use as a general practice. Geoff -- count@shalimar.net.au Vescere bracis meis http://www.hack.gr/jargon/html/D/disclaimer.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 18:40:13 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 18:40:11 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 056E737B400 for ; Tue, 2 Jan 2001 18:40:11 -0800 (PST) Received: from bluto.jimking.net (root@bluto.jimking.net [216.54.255.8]) by cgi.sstar.com (8.11.1/8.11.1) with ESMTP id f032e7E73241 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Tue, 2 Jan 2001 20:40:09 -0600 (CST) (envelope-from jim@jimking.net) Received: from marble (marble.lgc.com [134.132.228.4]) by bluto.jimking.net (8.11.1/8.11.1) with SMTP id f032e0o88770; Tue, 2 Jan 2001 20:40:00 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <00e301c0752e$7ba65e60$04e48486@marble> From: "Jim King" To: "Zero Sum" , "Alfred Perlstein" , "Thomas Seck" Cc: References: <20010102230107.A559@basildon.homerun> <20010102152109.D19572@fw.wintelcom.net> <01010313305000.03936@shalimar.net.au> Subject: Re: Vinum safe to use for raid 0? Date: Tue, 2 Jan 2001 20:40:00 -0600 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I know it is a bit off topic and if it has been discussed to death befire, > I apologise. But for the lfe of me I can't see why anyone would use RAID 5 > as other than an acadaemic exercise. Economics. If performance isn't a top priority and I need some fault tolerance I'd prefer to use RAID 5 and make more efficient use of the disk space. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 18:47:51 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 18:47:48 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 1745137B400 for ; Tue, 2 Jan 2001 18:47:46 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 5B2C46A913; Wed, 3 Jan 2001 13:17:42 +1030 (CST) Date: Wed, 3 Jan 2001 13:17:42 +1030 From: Greg Lehey To: Zero Sum Cc: Alfred Perlstein , Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? Message-ID: <20010103131742.F15003@wantadilla.lemis.com> References: <20010102230107.A559@basildon.homerun> <20010102152109.D19572@fw.wintelcom.net> <01010313305000.03936@shalimar.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01010313305000.03936@shalimar.net.au>; from count@shalimar.net.au on Wed, Jan 03, 2001 at 01:30:50PM +1100 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 3 January 2001 at 13:30:50 +1100, Zero Sum wrote: > On Wednesday 03 January 2001 10:21, Alfred Perlstein wrote: >> * Thomas Seck [010102 14:00] wrote: >>> Hi all, >>> >>> sorry if this is OT for -stable, but I followed the discussion about >>> vinum in here and got a bit worried. >>> >>> I am currently deploying a proxy server for our company. It shall use >>> squid on 4.2-STABLE. I would like to put the cache data on a vinum RAID >>> 0, made of three U160 disks. As I understood the discussion so far, >>> there are some unresolved problems with the raid 5 code. Could someone >>> tell me whether I can safely use vinum for building a raid 0 system >>> (despite the fact that the HW may be a point of failure of course)? >>> >>> Thanks in advance and best regards from Germany >> >> We've been using RAID-0 and RAID-1 with vinum here for a long time, >> the only problem we had was during a 3.x->4.x upgrade, we were able >> to recover from it after freaking out for a bit though. > > I know it is a bit off topic and if it has been discussed to death befire, > I apologise. But for the lfe of me I can't see why anyone would use RAID 5 > as other than an acadaemic exercise. > > If this seems like a troll, I'm sorry, but I have had this argument so many > time in RL. In the past I have always managed to get better performance by > throwing RAID 5 out. There are many reasons for using RAID. If you're looking for good read/write performance, you won't use RAID-5. But if you have a web server, for example, where 99% of all accesses are reads, then RAID-5 is quite a good choice. I do tend to agree that a lot of people use RAID-5 where RAID-1 would be a better choice. >> So yes, it is stable. I still wouldn't trust the RAID-5, but if >> you want to get RAID-5 working you could take a shot on getting >> some reproducable corruption/panics and let Greg know. >> > The lack of data may be because of it's lack of use as a general > practice. No, I don't think so. I'm surprised to hear how many people use it. I'm reasonably sure that the problems people have reported are due to a bug in Vinum, but I suspect it needs something else in combination in order to make it appear. For a while there was a theory that you need an fxp0 Ethernet card in the system, for example. 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-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 18:50:18 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 18:50:17 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id EEA3737B400 for ; Tue, 2 Jan 2001 18:50:12 -0800 (PST) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 14De02-0001WK-00; Tue, 02 Jan 2001 18:50:02 -0800 Date: Tue, 2 Jan 2001 18:49:57 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Zero Sum Cc: Alfred Perlstein , Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? In-Reply-To: <01010313305000.03936@shalimar.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Jan 2001, Zero Sum wrote: > I know it is a bit off topic and if it has been discussed to death befire, > I apologise. But for the lfe of me I can't see why anyone would use RAID 5 > as other than an acadaemic exercise. > > If this seems like a troll, I'm sorry, but I have had this argument so many > time in RL. In the past I have always managed to get better performance by > throwing RAID 5 out. But you don't use RAID 5 for performance. RAID is about reliablity. If you want reliability and performance, RAID10 wins. If you are operating on a budget use RAID5, or if you are putting toghether a lot of storage, RAID50. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 19: 2:52 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 19:02:49 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id E061637B400 for ; Tue, 2 Jan 2001 19:02:47 -0800 (PST) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id OAA40366 for ; Wed, 3 Jan 2001 14:02:43 +1100 (EST) (envelope-from carl@xena.ipaustralia.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma040363; Wed, 3 Jan 01 14:02:30 +1100 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.11.1/8.11.0) with ESMTP id f0332Uk78256 for ; Wed, 3 Jan 2001 14:02:30 +1100 (EST) (envelope-from carl@xena.ipaustralia.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Wed, 3 Jan 2001 14:02:29 +1100 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: stable@freebsd.org Subject: Is make release broken? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to roll a -stable snapshot using "make release" and it's dying consistantly when it tries to run mkwhatis across the /usr/share/man directories. Is anyone else having problems with make release at the moment? Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 19:51:30 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 19:51:28 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mage.trollkarl.net (fw.trollkarl.net [207.167.5.66]) by hub.freebsd.org (Postfix) with ESMTP id 9C0AA37B699 for ; Tue, 2 Jan 2001 19:51:27 -0800 (PST) Received: from trollkarl.skafte.org (root@trollkarl [192.168.100.16]) by mage.trollkarl.net (8.11.1/8.11.1) with ESMTP id f033pHC13470 for ; Tue, 2 Jan 2001 20:51:22 -0700 (MST) (envelope-from skafte@trollkarl.net) Received: (from skafte@localhost) by trollkarl.skafte.org (8.11.1/8.11.1) id f033pGW13367 for freebsd-stable@FreeBSD.ORG; Tue, 2 Jan 2001 20:51:16 -0700 (MST) (envelope-from skafte) Date: Tue, 2 Jan 2001 20:51:16 -0700 From: Greg Skafte To: freebsd-stable@FreeBSD.ORG Subject: Re: vinum malfunction! Message-ID: <20010102205116.A13254@trollkarl.skafte.org> References: <20001231101426.K99806@wantadilla.lemis.com> <20010102092819.K44043@wantadilla.lemis.com> <978425185.3a519561dbcdb@webmail.harmonic.co.il> <20010102193241.C40453@wantadilla.lemis.com> <978427080.3a519cc850a45@webmail.harmonic.co.il> <20010102034408.B56810@peorth.iteration.net> <978438556.3a51c99cea732@webmail.harmonic.co.il> <20010103104724.H40453@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010103104724.H40453@wantadilla.lemis.com>; from grog@lemis.com on Wed, Jan 03, 2001 at 10:47:24AM +1030 Organization: Gregs Hidey Hole Sender: skafte@trollkarl.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the past when I've had vinum problems, if I followed Greg's instructions, he has been very helpful. As he has stated numerous times he _needs_ the information he's asked for in the format he asked for, or he won't be able to help. I've yet to have vinum cause data loss, but I'm not running raid 5 either, just mirroring. If I've needed raid 5 or raid 50 then I've needed the whole machine to be raid 5/50 including the root/boot partition. As has been pointed out, this is young, and experimental software not nearly the milage that veritas has, or hp's lvm, or the aix equivalent. Its maintained on a volunteer pro-bono basis. Also, any opensource or even closed source solution need to be tested and verified for their suitability. Software Raid works well if you've tested it in your enviorment, Suns disk suite comes to mind on my sparcs, I've had hardware raid cards fail and eat everything also. In a _mission_ critical enviroment you need to have a recovery plan. Not having one is poor practice. Not have proper backs is even poorer practice. Free software does not imply no cost. If the expertise aren't availible to support this free stuff then there is going to be a substantial cost in lost productivity and lost data. I now return you to your regularily scheduled noise..... -- Email: skafte@trollkarl.net ICQ: 93234105 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 20: 4:26 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 20:04:23 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id 68A3237B400 for ; Tue, 2 Jan 2001 20:04:22 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f0343wp03856; Tue, 2 Jan 2001 22:03:59 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101030403.f0343wp03856@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Greg Lehey Cc: Josef Karthauser , Matraquilla@cs.com, Roman Shterenzon , freebsd-stable@FreeBSD.ORG From: David Kelly Subject: Re: RAID-5 reliability (was: vinum malfunction!) In-reply-to: Message from Greg Lehey of "Wed, 03 Jan 2001 10:36:21 +1030." <20010103103621.G40453@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Jan 2001 22:03:58 -0600 Sender: dkelly@grumpy.dyndns.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > On Tuesday, 2 January 2001 at 14:06:16 +0000, Josef Karthauser wrote: [...] > > > I don't know what it's going to take for Greg to get enough > > information to fix the problem. I spent a week trying to extract a > > set of debug information for him that was useful enough that he > > could work from it, but it seems that my week was just wasted > > because it looks like I didn't capture the bug that he was expecting > > :(. > > Well, it's not wasted, but it didn't help enough. As I said, it's > elusive. A point I'd like to make is that efforts to hunt down a problem (you don't know its a bug until you find it) are never wasted. Even if you don't find the problem. The only time such an effort is wasted is when all the effort is directed at (say) software, and you find the cleaning lady was unplugging your disc array every night. One day Greg may be looking at yet another stack trace without enough evidence to locate the problem, but something about the stack traces from Josef and others may click (light bulb appears over Greg's head) and provide the final clue. May be related, may not, but last month I found my new Promise ATA-100 card did not like to share interupts with my other toys. Had to be stressed to fail. And failed in the stangest ways with xterms disappearing, sometimes tcsh core dumped. About 15 minutes later the whole system rolled over on its back. How robust is PCI IRQ sharing? I would never have expected such a problem. But I moved that card to an IRQ of its own and was never able to repeat the problem. Another point I'd like to make is that its a myth that "hardware" is immune to such problems. "Hardware RAID" isn't really hardware so much as its a dedicated embedded CPU. Limited tasks to perform with total control of the environment. By comparison the FreeBSD kernel has a lot of things going on. Anyway, if "hardware" were immune to such problems then there would be little need for FLASH memory, BIOS updates, HD firmware updates, or even RAID firmware updates. Then again the advantage of the embedded system is the limited scope of outside influences, which should result in a stable and reliable system easier than one with higher limits. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 20:28:34 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 20:28:31 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shalimar.net.au (shalimar.net.au [198.142.161.98]) by hub.freebsd.org (Postfix) with ESMTP id D98E437B400 for ; Tue, 2 Jan 2001 20:28:28 -0800 (PST) Received: from shalimar.net.au (localhost [127.0.0.1]) by shalimar.net.au (8.11.1/8.11.1) with SMTP id f034Rn804542; Wed, 3 Jan 2001 15:27:51 +1100 (EST) (envelope-from count@shalimar.net.au) From: Zero Sum Organization: Tobacco Chewers and Body Painters Association. Date: Wed, 3 Jan 2001 15:27:49 +1100 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" Cc: To: "Jim King" , "Alfred Perlstein" , "Thomas Seck" References: <20010102230107.A559@basildon.homerun> <01010313305000.03936@shalimar.net.au> <00e301c0752e$7ba65e60$04e48486@marble> In-Reply-To: <00e301c0752e$7ba65e60$04e48486@marble> Subject: Re: Vinum safe to use for raid 0? MIME-Version: 1.0 Message-Id: <01010315274900.04373@shalimar.net.au> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Jan 2001, I (Zero Sum) wrote: >> I know it is a bit off topic and if it has been discussed to death >> before, I apologise. But for the lfe of me I can't see why anyone would >> use RAID as other than an acadaemic exercise. On Wednesday 03 January 2001 13:40, Jim King wrote in reponse: >Economics. If performance isn't a top priority and I need some fault >tolerance I'd prefer to use RAID 5 and make more efficient use of the disk >space. On Wednesday 03 January 2001 13:47, Greg Lehey wrote in reponse: >There are many reasons for using RAID. If you're looking for good >read/write performance, you won't use RAID-5. But if you have a web >server, for example, where 99% of all accesses are reads, then RAID-5 >is quite a good choice. I do tend to agree that a lot of people use >RAID-5 where RAID-1 would be a better choice. On Wednesday 03 January 2001 13:49, Tom wrote in reponse: > But you don't use RAID 5 for performance. RAID is about reliablity. If >you want reliability and performance, RAID10 wins. If you are operating >on a budget use RAID5, or if you are putting toghether a lot of storage, >RAID50. Jim and Tom mention the factor of expense. In Australia, I think we pay about five times the price that Americans seem to (this is not a price/currency conversion) but I still can't take that factor seriously. Disk space is *cheap*. As Tom says, for reliability and performance RAID1/0 wins. Using RAID 5 is "spoiling the ship for a pennyworth of tar", or so it seems to me. Hardware RAID is expensive. If you make that investment, the price of more disk should not be important. Software RAID gets slower the more complex it is. RAID 5 is considerably more complex than 0/1. Wouldn't you be better off spending money on a less capable processor and more disk? I haven't done any measurements here. I am only going from (limited) experience. But I can't see 'expense' as a justifying factor here. Not in a professional arena. Greg mentioned a situation (web server) where there are many reads (99%). I think that for RAID 5 to help matters much, you would have to have a very high hit rate on an immense number of different static pages. The read performance of 5 vs 1/0 is there, but it is marginal. Whether it gives you any improvement or not (how much, if any) is very dependant on what is going on in bufferspace. Thanks for your responses, but I still can't see a good argument for RAID5. Hope I haven't trod on too many toes. -- count@shalimar.net.au Vescere bracis meis http://www.hack.gr/jargon/html/D/disclaimer.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 20:37: 0 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 20:36:58 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cowpie.acm.vt.edu (cowpie.acm.vt.edu [128.173.42.253]) by hub.freebsd.org (Postfix) with ESMTP id 1676937B400 for ; Tue, 2 Jan 2001 20:36:58 -0800 (PST) Received: (from dlacroix@localhost) by cowpie.acm.vt.edu (8.9.3/8.9.3) id XAA04894 for freebsd-stable@freebsd.org; Tue, 2 Jan 2001 23:36:20 -0500 (EST) From: David La Croix Message-Id: <200101030436.XAA04894@cowpie.acm.vt.edu> Subject: 4.2-STABLE broken build? (Recent commit) To: freebsd-stable@freebsd.org Date: Tue, 2 Jan 2001 22:36:19 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just CVSupped 4.2-STABLE this evening, and tried to build a new kernel on the following system: FreeBSD narf.suddendeceleration.com 4.2-BETA FreeBSD 4.2-BETA #21: Mon Nov 20 19:02:11 CST 2000 dlacroix@narf.suddendeceleration.com:/usr/local/src/sys/compile/narf i386 gcc version 2.95.2 19991024 (release) Make depend fails with the following message: mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/include /usr/local/src/sys/modules/ray/../../dev/ray/if_ray.c /usr/local/src/sys/modules/ray/../../dev/ray/if_ray.c:268: dev/ray/if_raymib.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/local/src/sys/modules/ray. *** Error code 1 Stop in /usr/local/src/sys/modules. *** Error code 1 Sorry if someone already noticed this and fixed it ... I don't subscribe to -stable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 21:42: 6 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 21:42:04 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id E0C5937B400 for ; Tue, 2 Jan 2001 21:42:03 -0800 (PST) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 14DggE-0007dv-00; Tue, 02 Jan 2001 21:41:46 -0800 Date: Tue, 2 Jan 2001 21:41:41 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Zero Sum Cc: Jim King , Alfred Perlstein , Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? In-Reply-To: <01010315274900.04373@shalimar.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Jan 2001, Zero Sum wrote: ... > Jim and Tom mention the factor of expense. In Australia, I think we pay > about five times the price that Americans seem to (this is not a > price/currency conversion) but I still can't take that factor seriously. > Disk space is *cheap*. As Tom says, for reliability and performance > RAID1/0 wins. Using RAID 5 is "spoiling the ship for a pennyworth of tar", > or so it seems to me. Disk seems cheap. It is much more expensive than you realize, one you factor in enclosures, interfaces, power supplies, cabling, cooling, etc. Then factor in downtime if you use poor quality components at any point in the system. Also, factor in downtime if any part of the system is non-redundant. Then factor in management devices (SAF-TE), so you can determine whether your disks, power supplies, and fans are still working or not. If you've ever worked on large storage systems in a 24x7, you'd have a better appreciation of the TCO of disk space. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 22: 8:47 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 22:08:43 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from pinky.plambert.net (pinky.plambert.net [205.219.88.225]) by hub.freebsd.org (Postfix) with ESMTP id D5A4737B402 for ; Tue, 2 Jan 2001 22:08:42 -0800 (PST) Received: (from plambert@localhost) by pinky.plambert.net (8.11.1/8.9.3) id f0368KN16835; Tue, 2 Jan 2001 22:08:20 -0800 (PST) (envelope-from plambert) Date: Tue, 2 Jan 2001 22:08:20 -0800 From: "Paul M . Lambert" To: David La Croix Cc: stable@freebsd.org Subject: Re: 4.2-STABLE broken build? (Recent commit) Message-ID: <20010102220820.E86614@pinky.plambert.net> References: <200101030436.XAA04894@cowpie.acm.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101030436.XAA04894@cowpie.acm.vt.edu> Sender: plambert@pinky.plambert.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am seeing the same thing, on a newly-installed 4.2-RELEASE system. About to cvsup again, maybe something is fixed. --plambert On Tue, 02 Jan 2001, David La Croix wrote: > > Just CVSupped 4.2-STABLE this evening, and tried to build a new > kernel on the following system: > > FreeBSD narf.suddendeceleration.com 4.2-BETA FreeBSD 4.2-BETA #21: Mon Nov 20 19:02:11 CST 2000 dlacroix@narf.suddendeceleration.com:/usr/local/src/sys/compile/narf i386 > gcc version 2.95.2 19991024 (release) > > > Make depend fails with the following message: > > mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/include /usr/local/src/sys/modules/ray/../../dev/ray/if_ray.c /usr/local/src/sys/modules/ray/../../dev/ray/if_ray.c:268: dev/ray/if_raymib.h: > No such file or directory > mkdep: compile failed > *** Error code 1 > > Stop in /usr/local/src/sys/modules/ray. > *** Error code 1 > > Stop in /usr/local/src/sys/modules. > *** Error code 1 > > > Sorry if someone already noticed this and fixed it ... > I don't subscribe to -stable. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- I hate bombs, terrorism, fear, plans, future and past injustices, manifestos, popular sentiment, ignition, timetables, meetings, and poorly adjusted weasels. A warm hello to my friends and fans in domestic surveillance! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 22:21:27 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 22:21:24 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from klement.dstorm.net (ip-216-145-173-163.idcnet.com [216.145.173.163]) by hub.freebsd.org (Postfix) with ESMTP id 4185F37B402 for ; Tue, 2 Jan 2001 22:21:23 -0800 (PST) Received: from localhost (scotty@localhost) by klement.dstorm.net (8.11.1/8.11.1) with ESMTP id f036LwA85943 for ; Wed, 3 Jan 2001 00:21:58 -0600 (CST) (envelope-from scotty@klement.dstorm.net) Date: Wed, 3 Jan 2001 00:21:58 -0600 (CST) From: scotty@klement.dstorm.net To: freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? In-Reply-To: <20010102230107.A559@basildon.homerun> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been using vinum to mirror some 20gb UDMA66 IDE drives for about 8 months now. I've even had a drive failure in that time (my 2nd western digital 20gb drive to die within a year -- I bought a Seagate this time!) When I bought my seagate drive as a replacement, the size of the drive was slightly smaller, and I had to figure out how to reduce the size of the plex without losing the data. (making the new drive a standard UFS drive, copy the data to it, delete/create the old drive with a smaller plex, copy the data back, make the plex on the new drive, and make the drives sync up) I have to say: 1) vinum is a life saver. 2) once you're able to keep all the terminology straight in your head, vinum is a very powerful tool. 3) vinum has been very stable for me. (no failures) 4) it has greatly increased read performance when the system is under load I don't know if my input is helpful, since I'm not doing striping at all, but I thought I'd give my 2 cents. :) On Tue, 2 Jan 2001, Thomas Seck wrote: > Hi all, > > sorry if this is OT for -stable, but I followed the discussion about > vinum in here and got a bit worried. > > I am currently deploying a proxy server for our company. It shall use > squid on 4.2-STABLE. I would like to put the cache data on a vinum RAID > 0, made of three U160 disks. As I understood the discussion so far, > there are some unresolved problems with the raid 5 code. Could someone > tell me whether I can safely use vinum for building a raid 0 system > (despite the fact that the HW may be a point of failure of course)? > > Thanks in advance and best regards from Germany > > -Thomas Seck > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 22:51:43 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 22:51:39 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 978BB37B400 for ; Tue, 2 Jan 2001 22:51:36 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 021F36A911; Wed, 3 Jan 2001 17:21:32 +1030 (CST) Date: Wed, 3 Jan 2001 17:21:32 +1030 From: Greg Lehey To: Zero Sum Cc: Jim King , Alfred Perlstein , Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: RAID costs (was: Vinum safe to use for raid 0?) Message-ID: <20010103172132.T4336@wantadilla.lemis.com> References: <20010102230107.A559@basildon.homerun> <01010313305000.03936@shalimar.net.au> <00e301c0752e$7ba65e60$04e48486@marble> <01010315274900.04373@shalimar.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01010315274900.04373@shalimar.net.au>; from count@shalimar.net.au on Wed, Jan 03, 2001 at 03:27:49PM +1100 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 3 January 2001 at 15:27:49 +1100, Zero Sum wrote: > On Wed, 3 Jan 2001, I (Zero Sum) wrote: > On Wednesday 03 January 2001 13:49, Tom wrote in reponse: > >> But you don't use RAID 5 for performance. RAID is about reliablity. If >> you want reliability and performance, RAID10 wins. If you are operating >> on a budget use RAID5, or if you are putting toghether a lot of storage, >> RAID50. > > Jim and Tom mention the factor of expense. In Australia, I think we pay > about five times the price that Americans seem to (this is not a > price/currency conversion) Either I'm misunderstanding you, or you're paying too much. > but I still can't take that factor seriously. Disk space is > *cheap*. As Tom says, for reliability and performance RAID1/0 wins. > Using RAID 5 is "spoiling the ship for a pennyworth of tar", or so > it seems to me. For a certain definition of "cheap", sure. Let's assume you want a 10 TB web server. Never mind the cost of enclosures, just using relatively cheap disks like the IBM DTLA-307075, 75 GB a throw and available for about AUD 800, you're talking 130 drives, or a little over AUD 100K. And that with no redundancy. Add RAID-5, and you may pay $20K more. Use RAID-1 instead and your costs have gone up by $100K instead of $20K. What do you have to show for it? Increased power consumption, increased likelihood of a drive failure. But hardly any difference in performance. > Hardware RAID is expensive. If you make that investment, the price > of more disk should not be important. By comparison, hardware RAID is cheap. Software RAID is cheaper, of course, and what we've seen indicates that the performance is significantly better. > Software RAID gets slower the more complex it is. RAID 5 is > considerably more complex than 0/1. Wouldn't you be better off > spending money on a less capable processor and more disk? I haven't > done any measurements here. I am only going from (limited) > experience. You're also being rather vague. There's a more detailed explanation at http://www.vinumvm.org/vinum/intro.html. > But I can't see 'expense' as a justifying factor here. Not in a > professional arena. Precisely there. $80K for no particular purpose is not commercially justifiable. > Greg mentioned a situation (web server) where there are many reads > (99%). I think that for RAID 5 to help matters much, you would have > to have a very high hit rate on an immense number of different > static pages. The read performance of 5 vs 1/0 is there, but it is > marginal. Whether it gives you any improvement or not (how much, if > any) is very dependant on what is going on in bufferspace. No, in real life you can assume that you're not going to have very much cached. And RAID-5 is no faster than RAID-1 on reads, but it's also not measurably slower. 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-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 22:59:43 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 22:59:41 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from smtp.bmi.net (smtp.bmi.net [204.57.191.31]) by hub.freebsd.org (Postfix) with ESMTP id 96AF437B400 for ; Tue, 2 Jan 2001 22:59:40 -0800 (PST) Received: from WARP-BORG (dsl-154.bmi.net [207.173.60.230]) by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with SMTP id WAA22931 for ; Tue, 2 Jan 2001 22:59:38 -0800 From: jmcoopr@webmail.bmi.net Message-Id: <200101030659.WAA22931@smtp.bmi.net> Date: Tue, 02 Jan 2001 22:59:35 -0800 To: freebsd-stable@FreeBSD.org In-Reply-To: <200101030436.XAA04894@cowpie.acm.vt.edu> Subject: Re: 4.2-STABLE broken build? (Recent commit) X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v2.21/21 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <200101030436.XAA04894@cowpie.acm.vt.edu>, on 01/02/2001 at 10:36 PM, David La Croix said: >Just CVSupped 4.2-STABLE this evening, and tried to build a new kernel >on the following system: >FreeBSD narf.suddendeceleration.com 4.2-BETA FreeBSD 4.2-BETA #21: Mon >Nov 20 19:02:11 CST 2000 >dlacroix@narf.suddendeceleration.com:/usr/local/src/sys/compile/narf >i386 gcc version 2.95.2 19991024 (release) >Make depend fails with the following message: >mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ >-I@/../include -I/usr/include >/usr/local/src/sys/modules/ray/../../dev/ray/if_ray.c >/usr/local/src/sys/modules/ray/../../dev/ray/if_ray.c:268: >dev/ray/if_raymib.h: No such file or directory >mkdep: compile failed >*** Error code 1 >Stop in /usr/local/src/sys/modules/ray. >*** Error code 1 >Stop in /usr/local/src/sys/modules. >*** Error code 1 >Sorry if someone already noticed this and fixed it ... >I don't subscribe to -stable. >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message Same here. Tried to build it with both a custom kernel config and GENERIC. Fails identically (with above) each time. jmc ------------------------------------------------------ jmcoopr@webmail.bmi.net Using OS/2 since 1.0 ------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 23: 0:33 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 23:00:32 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from jhb-imta.mweb.co.za (jhb-imta.mweb.co.za [196.2.48.244]) by hub.freebsd.org (Postfix) with ESMTP id 72E7A37B400 for ; Tue, 2 Jan 2001 23:00:31 -0800 (PST) Received: from wheelerz.mweb.co.za ([196.30.184.137]) by jhb-imta.mweb.co.za (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0G6K00B2URD2ZJ@jhb-imta.mweb.co.za> for freebsd-stable@freebsd.org; Wed, 3 Jan 2001 08:58:16 +0200 (GMT-2) Received: (from gramroam@localhost) by wheelerz.mweb.co.za (8.11.1/8.11.1) id f0370ge11931 for freebsd-stable@freebsd.org; Wed, 03 Jan 2001 09:00:42 +0200 (SAST envelope-from gramster@mweb.co.za) Date: Wed, 03 Jan 2001 08:59:06 +0200 (SAST) From: Graham Wheeler Subject: /dev/ad* versus /dev/wd* To: freebsd-stable@freebsd.org Message-id: <200101030700.f0370ge11931@wheelerz.mweb.co.za> MIME-version: 1.0 X-Mailer: ELM [version 2.4ME+ PL68 (25)] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all The other day I wanted to try get my IDE CD-R drive working on FreeBSD 4-S. I noticed that the old /dev/wd* drivers have been replaced it seems with a new ATAPI driver, /dev/ad*, which doesn't seem to support IDE CD-Rs; however, the wd driver is still present but disabled. Questions: * what are the pros and cons of these two drivers? * is it possible to use the new ad driver with an IDE CD-R drive to record? Sorry if this is old hat. Please reply directly as well as CC the list, as I am sitting at home on the far end of a slow dialup link today. regards (and happy new year, everyone!) Graham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 23: 0:47 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 23:00:46 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.clones.com (unknown [216.70.178.182]) by hub.freebsd.org (Postfix) with ESMTP id 5464137B400 for ; Tue, 2 Jan 2001 23:00:45 -0800 (PST) Received: from localhost (gross@localhost) by mail.clones.com (8.9.3/8.9.3) with ESMTP id XAA10936 for ; Tue, 2 Jan 2001 23:02:03 -0800 Date: Tue, 2 Jan 2001 23:02:03 -0800 (PST) From: Glendon Gross To: stable@freebsd.org Subject: Cyrix M-II support? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Cyrix M-II processor that I was given as a gift. When I boot the machine, which runs fine with a Pentium-166 MMX, it errors out when trying to load the shell with the following error: init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: Although it will run in single-user, I would like to know if anyone has successfully compiled a kernel on the M-II. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 23:12:30 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 23:12:28 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id F117637B400 for ; Tue, 2 Jan 2001 23:12:27 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id dxmsaaaa for ; Wed, 3 Jan 2001 18:20:28 +1100 Message-ID: <3A52D0F7.2D89F1E7@quake.com.au> Date: Wed, 03 Jan 2001 18:12:55 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Graham Wheeler Cc: freebsd-stable@freebsd.org Subject: Re: /dev/ad* versus /dev/wd* References: <200101030700.f0370ge11931@wheelerz.mweb.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Graham Wheeler wrote: > > Hi all > > The other day I wanted to try get my IDE CD-R drive working on FreeBSD 4-S. > I noticed that the old /dev/wd* drivers have been replaced it seems with a > new ATAPI driver, /dev/ad*, which doesn't seem to support IDE CD-Rs; however, > the wd driver is still present but disabled. > > Questions: > > * what are the pros and cons of these two drivers? > > * is it possible to use the new ad driver with an IDE CD-R drive to record? Yes ad is the new driver and has been used since 4.0 or maybe earlier... IDE CD-R's work fine... Have you tried writing a cd? man burncd is your answer I think... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 23:42:45 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 23:42:43 2001 Return-Path: Delivered-To: freebsd-stable@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 9286B37B400 for ; Tue, 2 Jan 2001 23:42:42 -0800 (PST) Received: from [195.11.243.26] (helo=Debug) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14DiZF-000L7o-00; Wed, 03 Jan 2001 07:42:41 +0000 To: Greg Skafte , freebsd-stable@FreeBSD.ORG From: Cliff Sarginson Subject: Re: vinum malfunction! Date: Wed, 3 Jan 2001 07:42:41 GMT X-Mailer: www.webmail.nl.demon.net X-Sender: postmaster@btvs.demon.nl X-Originating-IP: 192.250.24.58 Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In the past when I've had vinum problems, if I followed Greg's > instructions, he has been very helpful. As he has stated numerous > times he _needs_ the information he's asked for in the format he > asked for, or he won't be able to help. > > I've yet to have vinum cause data loss, but I'm not running raid 5 > either, just mirroring. If I've needed raid 5 or raid 50 then I've > needed the whole machine to be raid 5/50 including the root/boot > partition. > > As has been pointed out, this is young, and experimental software > not nearly the milage that veritas has, or hp's lvm, or the aix > equivalent. Its maintained on a volunteer pro-bono basis. > > Also, any opensource or even closed source solution need to be > tested and verified for their suitability. Software Raid works > well if you've tested it in your enviorment, Suns disk suite > comes to mind on my sparcs, I've had hardware raid cards fail > and eat everything also. > > In a _mission_ critical enviroment you need to have a recovery > plan. Not only that you should also do what manufacturers rather quaintly call "a proof of concept" before sailing the boat out onto the high seas. > Not having one is poor practice. Not have proper backs > is even poorer practice. Free software does not imply no cost. > If the expertise aren't availible to support this free stuff then > there is going to be a substantial cost in lost productivity and > lost data. > Without going into the wrongs and rights of this seemingly endless debate just give the software author/maintainer the information he asks for in the format he wants it. Doesn't seem unreasonable to me. If his instructions are not clear then ask for clarification. Cliff > > I now return you to your regularily scheduled noise..... > > > -- > Email: skafte@trollkarl.net ICQ: 93234105 > #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 > -- -- > When things can't get any worse, they simplify themselves by getting a > whole lot worse then complicated. A complete and utter disaster is the > simplest thing in the world; it's preventing one that's complex. > (Janet Morris) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 2 23:58:57 2001 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 2 23:58:55 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id CEB7737B400 for ; Tue, 2 Jan 2001 23:58:54 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f037wQZ45135; Tue, 2 Jan 2001 23:58:26 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Jan 2001 23:58:26 -0800 (PST) From: Matt Dillon Message-Id: <200101030758.f037wQZ45135@earth.backplane.com> To: Greg Lehey Cc: Zero Sum , Jim King , Alfred Perlstein , Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: Re: RAID costs (was: Vinum safe to use for raid 0?) References: <20010102230107.A559@basildon.homerun> <01010313305000.03936@shalimar.net.au> <00e301c0752e$7ba65e60$04e48486@marble> <01010315274900.04373@shalimar.net.au> <20010103172132.T4336@wantadilla.lemis.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Like everything, topologies have their strengths and weaknesses. RAID-5 is excellent for read-centric operations (which large data stores tend to be, I will note) and, as Poul reminded me a few days ago... stripe-sized block-write operations can be made optimal. RAID-5 is pretty aweful for random-write operations. Of course, it has to be reliable to be useable, which is really the crux of the current thread. Someone needs to buy Greg some faster machines to play with :-), as the current vinum issues appear to be related to timing. There are other big differences between software and black-box RAID solutions. For example, what happens when the machine crashes right smack in the middle of a write? Hardware RAID (e.g. RAID-5) solutions have NVRAM to hold the log. Software RAID either has to be extremely careful in the sequencing of the data, play serial number tricks (which is why you sometimes see disks with weird physical sector sizes), or write a separate log and delay the actual disk updates until the log write has been confirmed. There are other solutions as well.. distributed data replication, for example. What use is a RAID-5 disk array if a lightning hit takes out the whole machine room? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 0: 4:15 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 00:04:13 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hk.sina.com.hk (unknown [202.85.139.109]) by hub.freebsd.org (Postfix) with SMTP id 5800137B400 for ; Wed, 3 Jan 2001 00:04:12 -0800 (PST) Received: (qmail 18104 invoked by uid 99); 3 Jan 2001 08:08:15 -0000 Message-ID: <20010103080815.18103.qmail@hk.sina.com.hk> X-Mailer: SinaMail 3.0Beta (FireToad) From: shizuka00 To: jmcoopr@webmail.bmi.net, freebsd-stable@FreeBSD.org Subject: RE: Re: 4.2-STABLE broken build? (Recent commit) Date: Wed Jan 3 16:08:15 HKT 2001 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <200101030436.XAA04894@cowpie.acm.vt.edu>, on 01/02/2001 > at 10:36 PM, David La Croix said: > > >>Just CVSupped 4.2-STABLE this evening, and tried to build a new kernel >>on the following system: > >>FreeBSD narf.suddendeceleration.com 4.2-BETA FreeBSD 4.2-BETA #21: Mon >>Nov 20 19:02:11 CST 2000 >>dlacroix@narf.suddendeceleration.com:/usr/local/src/sys/compile/narf >>i386 gcc version 2.95.2 19991024 (release) > > >>Make depend fails with the following message: > >>mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ >>-I@/../include -I/usr/include >>/usr/local/src/sys/modules/ray/../../dev/ray/if_ray.c >>/usr/local/src/sys/modules/ray/../../dev/ray/if_ray.c:268: >>dev/ray/if_raymib.h: No such file or directory >>mkdep: compile failed >>*** Error code 1 > >>Stop in /usr/local/src/sys/modules/ray. >>*** Error code 1 > >>Stop in /usr/local/src/sys/modules. >>*** Error code 1 > > >>Sorry if someone already noticed this and fixed it ... >>I don't subscribe to -stable. > > >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-stable" in the body of the message > >Same here. Tried to build it with both a custom kernel config and >GENERIC. Fails identically (with above) each time. > >jmc > >------------------------------------------------------ >jmcoopr@webmail.bmi.net > >Using OS/2 since 1.0 >------------------------------------------------------ > > > A New driver, ray, was added lately and a file was missed. You can try MODULES_WITH_WORLD=true when building the kernel to skip moudles. Note: I have not tried yet. If it doesn't work, try to delete "ray" modules in the Makefile. =================================================================== ·s®ö§K¶O¹q¤l¶l½c http://sinamail.sina.com.hk ·s®ö¦³¼úEcard"íb"¨Î¸` http://ecards1.sina.com.hk/info.cgi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 0: 6:36 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 00:06:35 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1F9AB37B400; Wed, 3 Jan 2001 00:06:34 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id f0386TU28016; Wed, 3 Jan 2001 01:06:33 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.8.3) with ESMTP id f0386S110373; Wed, 3 Jan 2001 01:06:28 -0700 (MST) Message-Id: <200101030806.f0386S110373@harmony.village.org> To: jmcoopr@webmail.bmi.net Subject: Re: 4.2-STABLE broken build? (Recent commit) Cc: freebsd-stable@FreeBSD.ORG, Duncan Barclay In-reply-to: Your message of "Tue, 02 Jan 2001 22:59:35 PST." <200101030659.WAA22931@smtp.bmi.net> References: <200101030659.WAA22931@smtp.bmi.net> Date: Wed, 03 Jan 2001 01:06:28 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ray was MFC'd earlier today. Looks like a problem. Duncan, I'm sure, will fix it when he realizes what is going on (if he hasn't done so alread). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 0:50:14 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 00:50:12 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 3068937B400 for ; Wed, 3 Jan 2001 00:50:12 -0800 (PST) Received: from dmlb.org ([62.253.135.85]) by mta02-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20010103085010.OKAJ23225.mta02-svc.ntlworld.com@dmlb.org>; Wed, 3 Jan 2001 08:50:10 +0000 Received: from dmlb by dmlb.org with local (Exim 3.03 #1) id 14DjcY-0002uS-00; Wed, 03 Jan 2001 08:50:10 +0000 Content-Length: 497 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 In-Reply-To: <200101030806.f0386S110373@harmony.village.org> Date: Wed, 03 Jan 2001 08:50:09 -0000 (GMT) From: Duncan Barclay To: Warner Losh Subject: Re: 4.2-STABLE broken build? (Recent commit) Cc: freebsd-stable@FreeBSD.ORG, jmcoopr@webmail.bmi.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I'm on the case. I went to bed straight after the commit. Duncan On 03-Jan-01 Warner Losh wrote: > ray was MFC'd earlier today. Looks like a problem. Duncan, I'm sure, > will fix it when he realizes what is going on (if he hasn't done so > alread). > > Warner > --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@dmlb.org | the alcoholics, and the permanently stoned. dmlb@freebsd.org| Steven King To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 0:54:45 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 00:54:43 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 79A0237B400 for ; Wed, 3 Jan 2001 00:54:41 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 301586A90D; Wed, 3 Jan 2001 19:24:39 +1030 (CST) Date: Wed, 3 Jan 2001 19:24:39 +1030 From: Greg Lehey To: Matt Dillon Cc: Zero Sum , Jim King , Alfred Perlstein , Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: Re: RAID costs (was: Vinum safe to use for raid 0?) Message-ID: <20010103192438.V4336@wantadilla.lemis.com> References: <20010102230107.A559@basildon.homerun> <01010313305000.03936@shalimar.net.au> <00e301c0752e$7ba65e60$04e48486@marble> <01010315274900.04373@shalimar.net.au> <20010103172132.T4336@wantadilla.lemis.com> <200101030758.f037wQZ45135@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101030758.f037wQZ45135@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Jan 02, 2001 at 11:58:26PM -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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 2 January 2001 at 23:58:26 -0800, Matt Dillon wrote: > Like everything, topologies have their strengths and weaknesses. > RAID-5 is excellent for read-centric operations (which large data stores > tend to be, I will note) and, as Poul reminded me a few days ago... > stripe-sized block-write operations can be made optimal. Well, they can be optimized, which isn't quite the same thing. That's a wish list item for Vinum. > Of course, it has to be reliable to be useable, which is really > the crux of the current thread. Someone needs to buy Greg some > faster machines to play with :-), as the current vinum issues > appear to be related to timing. I'm not sure about that, though it's possible. The real issue with my test setup is that the disks I have are all ancient. I'm getting some more modern ones Real Soon Now, but of course the optimum way to solve this particular problem would be if somebody sent me exactly the machine that was having trouble. > There are other big differences between software and black-box > RAID solutions. For example, what happens when the machine > crashes right smack in the middle of a write? Hardware RAID > (e.g. RAID-5) solutions have NVRAM to hold the log. Software > RAID either has to be extremely careful in the sequencing of the > data, play serial number tricks (which is why you sometimes see > disks with weird physical sector sizes), or write a separate log > and delay the actual disk updates until the log write has been > confirmed. Indeed. Vinum cheats a little here, but even then it seem to be too finicky for many people. Theoretically, after a crash you need to synchronize the volumes. I'm thinking of a volume manager logging facility which will keep track of the last n operations. This would enable recovery code to confirm that they had been performed. 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-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 1:24:39 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 01:24:35 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from sal1.yamalinfo.ru (sal1.yamalinfo.ru [195.133.157.9]) by hub.freebsd.org (Postfix) with ESMTP id 02EE437B404 for ; Wed, 3 Jan 2001 01:24:29 -0800 (PST) Received: from vorob (mabalozi.yamalinfo.ru [195.133.157.7]) by sal1.yamalinfo.ru (8.11.1/8.11.1) with ESMTP id f039OMv13606 for ; Wed, 3 Jan 2001 14:24:26 +0500 (YEKT) (envelope-from vorob@yamalinfo.ru) Date: Wed, 3 Jan 2001 14:24:22 +0500 From: Yuri Vorobyev X-Mailer: The Bat! (v1.48f) Reply-To: Yuri Vorobyev X-Priority: 3 (Normal) Message-ID: <15420124096.20010103142422@yamalinfo.ru> To: freebsd-stable@FreeBSD.ORG Subject: can't build kernel Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Make world pass normal, but then i try build kernel i got this error: ===> bktr/bktr_mem ===> coff ===> fpu ===> gnufpu ===> ibcs2 ===> linprocfs ===> mly ===> ray rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include /usr/src/sys/modules/ray/../../dev/ray/if_ray.c /usr/src/sys/modules/ray/../../dev/ray/if_ray.c:268: dev/ray/if_raymib.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/ray. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 -- Yuri Vorobyev vorob@yamalinfo.ru www.yamalinfo.ru +7-34922-47791 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 1:35:12 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 01:35:08 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by hub.freebsd.org (Postfix) with ESMTP id 0222D37B400 for ; Wed, 3 Jan 2001 01:35:08 -0800 (PST) Received: from dmlb.org ([62.253.135.85]) by mta03-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20010103093506.GWOZ10171.mta03-svc.ntlworld.com@dmlb.org>; Wed, 3 Jan 2001 09:35:06 +0000 Received: from dmlb by dmlb.org with local (Exim 3.03 #1) id 14DkK2-00031I-00; Wed, 03 Jan 2001 09:35:06 +0000 Content-Length: 1258 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 In-Reply-To: <15420124096.20010103142422@yamalinfo.ru> Date: Wed, 03 Jan 2001 09:35:05 -0000 (GMT) From: Duncan Barclay To: Yuri Vorobyev Subject: RE: can't build kernel - if_raymib.h missing Cc: freebsd-stable@FreeBSD.ORG Sender: "Duncan Barclay,Cambridge - United Kingdon,,+44 1223 871245" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've just added the missing header file to the CVS repository. Please cvsup. Duncan On 03-Jan-01 Yuri Vorobyev wrote: > Hello! > > Make world pass normal, but then i try build kernel i got this > error: > > ===> bktr/bktr_mem > ===> coff > ===> fpu > ===> gnufpu > ===> ibcs2 > ===> linprocfs > ===> mly > ===> ray > rm -f .depend > mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ > -I@/../include /usr/src/sys/modules/ray/../../dev/ray/if_ray.c > /usr/src/sys/modules/ray/../../dev/ray/if_ray.c:268: dev/ray/if_raymib.h: No > such file or directory > mkdep: compile failed > *** Error code 1 > > Stop in /usr/src/sys/modules/ray. > *** Error code 1 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > -- > Yuri Vorobyev vorob@yamalinfo.ru > www.yamalinfo.ru +7-34922-47791 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@dmlb.org | the alcoholics, and the permanently stoned. dmlb@freebsd.org| Steven King To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 1:36:51 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 01:36:48 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from subnet.sub.net (subnet.sub.net [212.227.14.21]) by hub.freebsd.org (Postfix) with ESMTP id 1BD7E37B400 for ; Wed, 3 Jan 2001 01:36:47 -0800 (PST) Received: from lyxys.ka.sub.org (uucp@localhost) by subnet.sub.net (8.8.8/8.8.8/1.2subnet-linux) with bsmtp id KAA00553; Wed, 3 Jan 2001 10:36:43 +0100 Received: from localhost (1096 bytes) by lyxys.ka.sub.org via sendmail with P:stdio/R:smart_host/T:inet_uusmtp (sender: ) (ident using unix) id for ; Wed, 3 Jan 2001 10:34:59 +0100 (CET) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Aug-23) Message-Id: From: wolfgang@lyxys.ka.sub.org (Wolfgang Zenker) Subject: Re: Help Update In-Reply-To: <3A521D3C.3090908@planetwe.com> "from Drew Sanford at Jan 2, 2001 12:26:04 pm" To: Drew Sanford Date: Wed, 3 Jan 2001 10:34:59 +0100 (CET) Cc: Odhiambo Washington , FBSD-STABLE X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Odhiambo Washington wrote: > > n 2 20:36:57 alouette /kernel: pid 56184 (troff), uid 0: exited on signal > > 11 (core dumped) > Signal 11 usually indicates a hardware problem. Have you added any > memory or changed (or overclocked?) your processor since you last did a > make world? another possibility would be that something is wrong with your troff binary. You could try to rebuild troff and see if this fixes your problem; to rebuild troff something like cd /usr/src/gnu/usr.bin/groff/troff ; make install should probably work. Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 2:28:34 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 02:28:32 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 9777537B402 for ; Wed, 3 Jan 2001 02:28:32 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 576A7315F; Wed, 3 Jan 2001 10:29:44 +0000 (GMT) Date: Wed, 3 Jan 2001 10:29:44 +0000 From: Josef Karthauser To: Thomas Seck Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? Message-ID: <20010103102943.A770@tao.org.uk> Mail-Followup-To: Josef Karthauser , Thomas Seck , freebsd-stable@FreeBSD.ORG References: <20010102230107.A559@basildon.homerun> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010102230107.A559@basildon.homerun>; from tmseck@web.de on Tue, Jan 02, 2001 at 11:01:07PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 11:01:07PM +0100, Thomas Seck wrote: > Hi all, > > sorry if this is OT for -stable, but I followed the discussion about > vinum in here and got a bit worried. > > I am currently deploying a proxy server for our company. It shall use > squid on 4.2-STABLE. I would like to put the cache data on a vinum RAID > 0, made of three U160 disks. As I understood the discussion so far, > there are some unresolved problems with the raid 5 code. Could someone > tell me whether I can safely use vinum for building a raid 0 system > (despite the fact that the HW may be a point of failure of course)? As far as I'm aware there are no problems using vinum for raid 0. As far as I understand from Greg he's not aware of many people who are having problems with raid 5. As one of the small minority who was having problems I'd advice you to soaktest any vinum raid 5 installation before committing important data to it. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 3:18:36 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 03:18:33 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 28ED737B402 for ; Wed, 3 Jan 2001 03:18:32 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id AEA806A911; Wed, 3 Jan 2001 21:48:29 +1030 (CST) Date: Wed, 3 Jan 2001 21:48:29 +1030 From: Greg Lehey To: Josef Karthauser Cc: Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? Message-ID: <20010103214829.X4336@wantadilla.lemis.com> References: <20010102230107.A559@basildon.homerun> <20010103102943.A770@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010103102943.A770@tao.org.uk>; from joe@tao.org.uk on Wed, Jan 03, 2001 at 10:29:44AM +0000 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 3 January 2001 at 10:29:44 +0000, Josef Karthauser wrote: > On Tue, Jan 02, 2001 at 11:01:07PM +0100, Thomas Seck wrote: >> Hi all, >> >> sorry if this is OT for -stable, but I followed the discussion about >> vinum in here and got a bit worried. >> >> I am currently deploying a proxy server for our company. It shall use >> squid on 4.2-STABLE. I would like to put the cache data on a vinum RAID >> 0, made of three U160 disks. As I understood the discussion so far, >> there are some unresolved problems with the raid 5 code. Could someone >> tell me whether I can safely use vinum for building a raid 0 system >> (despite the fact that the HW may be a point of failure of course)? > > As far as I'm aware there are no problems using vinum for raid 0. > > As far as I understand from Greg he's not aware of many people who > are having problems with raid 5. Probably. If you know of somebody I don't know of, please let me know. > As one of the small minority who was having problems I'd advice you > to soaktest any vinum raid 5 installation before committing > important data to it. That's what vinum(4) says. 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-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 4: 9:22 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 04:09:21 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from gw2.dnepr.net (CoreGW2-TBone.dnepr.net [195.24.156.97]) by hub.freebsd.org (Postfix) with ESMTP id 5EBD337B400 for ; Wed, 3 Jan 2001 04:09:17 -0800 (PST) Received: from dnepr.net (dnepr.net [195.24.156.98]) by gw2.dnepr.net (8.8.8/8.6.18/01) with ESMTP id OAA14501 for ; Wed, 3 Jan 2001 14:08:58 +0200 (EET) Received: (from land@localhost) by dnepr.net (8.8.8/8.8.8) id OAA18824 for stable@freebsd.org; Wed, 3 Jan 2001 14:08:51 +0200 (EET) X-POP3-RCPT: stable@freebsd.org Date: Wed, 3 Jan 2001 14:08:51 +0200 From: Andrey Lakhno To: stable@freebsd.org Subject: 3.1 -> 4-S via NFS Message-ID: <20010103140851.A17817@dnepr.net> Mail-Followup-To: stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! I have two boxes running FreeBSD 3.1-RELEASE and 4.X-STABLE. I want to build world on 4.X system and then install it over NFS to 3.1 system. Is there any pitfalls in this process ? Caveats ? -- Best regards, Andrey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 4:29: 3 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 04:28:50 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from jamus.xpert.com (jamus.xpert.com [199.203.132.17]) by hub.freebsd.org (Postfix) with ESMTP id 1138A37B400 for ; Wed, 3 Jan 2001 04:28:47 -0800 (PST) Received: from roman by jamus.xpert.com with local (Exim 3.12 #5) id 14Dmp0-00006m-00; Wed, 03 Jan 2001 14:15:14 +0200 Date: Wed, 3 Jan 2001 14:15:14 +0200 From: Roman Shterenzon To: Greg Lehey , Daniel Lang , freebsd-stable@freebsd.org Subject: Vinum saga continues Message-ID: <20010103141514.A381@jamus.xpert.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="fdj2RfSjLxBAspz7" Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i Sender: Roman Shterenzon Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, Attached is the most valuable information that was in my pr 22103. I've read the vinumdebug and the other guy's PR. I'm still not getting what is missing. You told the other guy to submit the backtrace, but it was in fact submitted! It's as well in my PR as well. Your responses are very brief - "please read vinumdebug", but in fact, if there's something that is missing, you can be more specific. Alfred Perlstein looked it my PR once and he thinks that it's due to stack smashing. However, he wasn't able to find where it happends. It may be in fact interaction with some other driver, like you said, for example - fxp. This is why I submitted the dmesg output. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=koi8-r Content-Disposition: attachment; filename="kdb-session.txt" Content-Transfer-Encoding: 8bit Script started on Sun Oct 22 10:00:33 2000 matrix# gdb -k /usr/src/sys/compile/MATRIX/kernel.debug vmcore.0 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 "i386-unknown-freebsd"... IdlePTD 3219456 initial pcb at 29a720 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x54 fault code = supervisor write, page not present instruction pointer = 0x8:0xc150fc67 stack pointer = 0x10:0xc0277394 frame pointer = 0x10:0xc02773b0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01e2e50 stack pointer = 0x10:0xc02771cc frame pointer = 0x10:0xc02771d0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio trap number = 12 panic: page fault Uptime: 6m22s Fatal trap 12: page fault while in kernel mode fault virtual address = 0x54 fault code = supervisor write, page not present instruction pointer = 0x8:0xc150fc67 stack pointer = 0x10:0xc0276ab0 frame pointer = 0x10:0xc0276acc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio cam trap number = 12 panic: page fault Uptime: 6m22s Fatal trap 12: page fault while in kernel mode fault virtual address = 0x54 fault code = supervisor write, page not present instruction pointer = 0x8:0xc150fc67 stack pointer = 0x10:0xc0276394 frame pointer = 0x10:0xc02763b0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio cam trap number = 12 panic: page fault Uptime: 6m22s Fatal trap 12: page fault while in kernel mode fault virtual address = 0x54 fault code = supervisor write, page not present instruction pointer = 0x8:0xc150fc67 stack pointer = 0x10:0xc0275c78 frame pointer = 0x10:0xc0275c94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio cam trap number = 12 panic: page fault Uptime: 6m22s Fatal trap 12: page fault while in kernel mode fault virtual address = 0x54 fault code = supervisor write, page not present instruction pointer = 0x8:0xc150fc67 stack pointer = 0x10:0xc027555c frame pointer = 0x10:0xc0275578 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio cam trap number = 12 panic: page fault Uptime: 6m22s dumping to dev #da/0x20001, offset 774 dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 4 93 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 43 4 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 4 14 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 38 5 384 383 382 381 380 379 378 377 376 37 5 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 3 55 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 29 6 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 2 76 275 274 273 272 271 270 269 268 267 266 26! 5 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 20 6 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 1 86 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 1 37 136 135 134 133 132 131 130 129 128 1 27 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 3 1 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:302 302 dumppcb.pcb_cr3 = rcr3(); (kgdb) f 1 #1 0xc0153d38 in poweroff_wait (junk=0xc026f22f, howto=0x0) at ../../kern/ker n_shutdown.c:552 552 boot(bootopt); (kgdb) bt #0 boot (howto=0x104) at ../../kern/kern_shutdown.c:302 #1 0xc0153d38 in poweroff_wait (junk=0xc026f22f, howto=0x0) at ../../kern/ker n_shutdown.c:552 #2 0xc0236d35 in trap_fatal (frame=0xc027551c, eva=0x54) at ../../i386/i386/t rap.c:927 #3 0xc0236a0d in trap_pfault (frame=0xc027551c, usermode=0x0, eva=0x54) at .. /../i386/i386/trap.c:820 #4 0xc023660b in trap (frame={tf_fs = 0xc0270010, tf_es = 0xc0150010, tf_ds = 0x6c0010, tf_edi = 0xc16e6420, tf_esi = 0xc16e6400, tf_ebp = 0xc0275578, tf_isp = 0xc0275548, tf_ebx = 0xc208e040, tf_edx = 0x0, tf_ecx = 0x56e0001, tf_eax = 0xff9373bf, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0xc150fc67, tf_cs = 0x8, tf_eflags = 0x10246, tf_esp = 0xc16e6420, tf_ss = 0xc14bd000}) at ../../ i386/i386/trap.c:426 During symbol reading, inner block (0xc1505000-0xc150500a) not inside outer bl ock (0xc150bc0c-0xc150c3c2). During symbol reading, block at 0xc15050d4 out of order. #5 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../dev/vinu m/vinuminterrupt.c:199 #6 0xc0178d6b in biodone (bp=0xc16e6420) at ../../kern/vfs_bio.c:2637 #7 0xc0126bb9 in dadone (periph=0xc14ca700, done_ccb=0xc183ac00) at ../../cam /scsi/scsi_da.c:1246 #8 0xc0122aff in camisr (queue=0xc0298690) at ../../cam/cam_xpt.c:6319 #9 0xc0122911 in swi_cambio () at ../../cam/cam_xpt.c:6222 #10 0xc011fd10 in xpt_polled_action (start_ccb=0xc027590c) at ../../cam/cam_xp t.c:3389 #11 0xc0127081 in dashutdown (arg=0x0, howto=0x104) at ../../cam/scsi/scsi_da. c:1538 #12 0xc0153984 in boot (howto=0x104) at ../../kern/kern_shutdown.c:297 #13 0xc0153d38 in poweroff_wait (junk=0xc026f22f, howto=0x0) at ../../kern/ker n_shutdown.c:552 #14 0xc0236d35 in trap_fatal (frame=0xc0275c38, eva=0x54) at ../../i386/i386/t rap.c:927 #15 0xc0236a0d in trap_pfault (frame=0xc0275c38, usermode=0x0, eva=0x54) at .. /../i386/i386/trap.c:820 #16 0xc023660b in trap (frame={tf_fs = 0x10, tf_es = 0xc0150010, tf_ds = 0x6c0 010, tf_edi = 0xc16e7820, tf_esi = 0xc16e7800, tf_ebp = 0xc0275c94, tf_isp = 0xc0275c64, tf_ebx = 0xc208e100, tf_edx = 0x0, tf_ecx = 0x56b0001, tf_eax = 0xff9373bf, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0xc150fc67, tf_cs = 0x8, tf_eflags = 0x10246, tf_esp = 0xc16e7820, tf_ss = 0xc14bd000}) at ../../ i386/i386/trap.c:426 #17 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../dev/vinu m/vinuminterrupt.c:199 #18 0xc0178d6b in biodone (bp=0xc16e7820) at ../../kern/vfs_bio.c:2637 #19 0xc0126bb9 in dadone (periph=0xc14ca700, done_ccb=0xc14dc000) at ../../cam /scsi/scsi_da.c:1246 #20 0xc0122aff in camisr (queue=0xc0298690) at ../../cam/cam_xpt.c:6319 #21 0xc0122911 in swi_cambio () at ../../cam/cam_xpt.c:6222 #22 0xc011fd10 in xpt_polled_action (start_ccb=0xc0276028) at ../../cam/cam_xp t.c:3389 #23 0xc0127081 in dashutdown (arg=0x0, howto=0x104) at ../../cam/scsi/scsi_da. c:1538 #24 0xc0153984 in boot (howto=0x104) at ../../kern/kern_shutdown.c:297 #25 0xc0153d38 in poweroff_wait (junk=0xc026f22f, howto=0x0) at ../../kern/ker n_shutdown.c:552 #26 0xc0236d35 in trap_fatal (frame=0xc0276354, eva=0x54) at ../../i386/i386/t rap.c:927 #27 0xc0236a0d in trap_pfault (frame=0xc0276354, usermode=0x0, eva=0x54) at .. /../i386/i386/trap.c:820 #28 0xc023660b in trap (frame={tf_fs = 0xc0270010, tf_es = 0xc0150010, tf_ds = 0x6c0010, tf_edi = 0xc16e8c20, tf_esi = 0xc16e8c00, tf_ebp = 0xc02763b0, tf_isp = 0xc0276380, tf_ebx = 0xc208e1c0, tf_edx = 0x0, tf_ecx = 0x5680001, tf_eax = 0xff9373bf, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0xc150fc67, tf_cs = 0x8, tf_eflags = 0x10246, tf_esp = 0xc16e8c20, tf_ss = 0xc14bd000}) at ../../ i386/i386/trap.c:426 #29 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../dev/vinu m/vinuminterrupt.c:199 #30 0xc0178d6b in biodone (bp=0xc16e8c20) at ../../kern/vfs_bio.c:2637 #31 0xc0126bb9 in dadone (periph=0xc14ca700, done_ccb=0xc1835800) at ../../cam /scsi/scsi_da.c:1246 #32 0xc0122aff in camisr (queue=0xc0298690) at ../../cam/cam_xpt.c:6319 #33 0xc0122911 in swi_cambio () at ../../cam/cam_xpt.c:6222 #34 0xc011fd10 in xpt_polled_action (start_ccb=0xc0276744) at ../../cam/cam_xp t.c:3389 #35 0xc0127081 in dashutdown (arg=0x0, howto=0x104) at ../../cam/scsi/scsi_da. c:1538 #36 0xc0153984 in boot (howto=0x104) at ../../kern/kern_shutdown.c:297 #37 0xc0153d38 in poweroff_wait (junk=0xc026f22f, howto=0x0) at ../../kern/ker n_shutdown.c:552 #38 0xc0236d35 in trap_fatal (frame=0xc0276a70, eva=0x54) at ../../i386/i386/t rap.c:927 #39 0xc0236a0d in trap_pfault (frame=0xc0276a70, usermode=0x0, eva=0x54) at .. /../i386/i386/trap.c:820 #40 0xc023660b in trap (frame={tf_fs = 0xc0270010, tf_es = 0xc0150010, tf_ds = 0x6c0010, tf_edi = 0xc16e8020, tf_esi = 0xc16e8000, tf_ebp = 0xc0276acc, tf_isp = 0xc0276a9c, tf_ebx = 0xc208e280, tf_edx = 0x0, tf_ecx = 0x5650001, tf_eax = 0xff9373bf, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0xc150fc67, tf_cs = 0x8, tf_eflags = 0x10246, tf_esp = 0xc16e8020, tf_ss = 0xc14bd000}) at ../../ i386/i386/trap.c:426 #41 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../dev/vinu m/vinuminterrupt.c:199 #42 0xc0178d6b in biodone (bp=0xc16e8020) at ../../kern/vfs_bio.c:2637 #43 0xc0126bb9 in dadone (periph=0xc14ca700, done_ccb=0xc1658c00) at ../../cam /scsi/scsi_da.c:1246 #44 0xc0122aff in camisr (queue=0xc0298690) at ../../cam/cam_xpt.c:6319 #45 0xc0122911 in swi_cambio () at ../../cam/cam_xpt.c:6222 #46 0xc011fd10 in xpt_polled_action (start_ccb=0xc0276e60) at ../../cam/cam_xp t.c:3389 #47 0xc0127081 in dashutdown (arg=0x0, howto=0x104) at ../../cam/scsi/scsi_da. c:1538 #48 0xc0153984 in boot (howto=0x104) at ../../kern/kern_shutdown.c:297 #49 0xc0153d38 in poweroff_wait (junk=0xc026f22f, howto=0x0) at ../../kern/ker n_shutdown.c:552 #50 0xc0236d35 in trap_fatal (frame=0xc027718c, eva=0x30) at ../../i386/i386/t rap.c:927 #51 0xc0236a0d in trap_pfault (frame=0xc027718c, usermode=0x0, eva=0x30) at .. /../i386/i386/trap.c:820 #52 0xc023660b in trap (frame={tf_fs = 0x680010, tf_es = 0x680010, tf_ds = 0xc 0140010, tf_edi = 0x0, tf_esi = 0xc02af7e0, tf_ebp = 0xc02771d0, tf_isp = 0xc02771b8, tf_ebx = 0xc028959c, tf_edx = 0x688440, tf_ecx = 0x3, tf_eax = 0x0, tf_trapno = 0xc, tf_err = 0x0, tf_eip = 0xc0 1e2e50, tf_cs = 0x8, ---Type to continue, or q to quit--- tf_eflags = 0x10202, tf_esp = 0x0, tf_ss = 0xc02771ec}) at ../../i386/i3 86/trap.c:426 #53 0xc01e2e50 in acquire_lock (lk=0xc028959c) at ../../ufs/ffs/ffs_softdep.c: 265 #54 0xc01e7012 in softdep_fsync_mountdev (vp=0xd41c0000) at ../../ufs/ffs/ffs_ softdep.c:3788 #55 0xc01eb04a in ffs_fsync (ap=0xc0277244) at ../../ufs/ffs/ffs_vnops.c:134 #56 0xc01e9d72 in ffs_sync (mp=0xc14cc000, waitfor=0x2, cred=0xc10c0680, p=0xc 02af7e0) at vnode_if.h:537 #57 0xc018092f in sync (p=0xc02af7e0, uap=0x0) at ../../kern/vfs_syscalls.c:54 4 #58 0xc0153787 in boot (howto=0x100) at ../../kern/kern_shutdown.c:224 #59 0xc0153d38 in poweroff_wait (junk=0xc026f22f, howto=0x0) at ../../kern/ker n_shutdown.c:552 #60 0xc0236d35 in trap_fatal (frame=0xc0277354, eva=0x54) at ../../i386/i386/t rap.c:927 #61 0xc0236a0d in trap_pfault (frame=0xc0277354, usermode=0x0, eva=0x54) at .. /../i386/i386/trap.c:820 #62 0xc023660b in trap (frame={tf_fs = 0xc0270010, tf_es = 0xc0150010, tf_ds = 0x680010, tf_edi = 0xc16e9588, tf_esi = 0xc16e9400, tf_ebp = 0xc02773b0, tf_isp = 0xc0277380, tf_ebx = 0xc208e340, tf_edx = 0x0, tf_ecx = 0x5610001, tf_eax = 0xff9773bf, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0xc150fc67, tf_cs = 0x8, tf_eflags = 0x10246, tf_esp = 0xc16e9588, tf_ss = 0xc14bd000}) at ../../ i386/i386/trap.c:426 #63 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../dev/vinu m/vinuminterrupt.c:199 #64 0xc0178d6b in biodone (bp=0xc16e9588) at ../../kern/vfs_bio.c:2637 #65 0xc0126bb9 in dadone (periph=0xc14ca700, done_ccb=0xc1808400) at ../../cam /scsi/scsi_da.c:1246 #66 0xc0122aff in camisr (queue=0xc0298690) at ../../cam/cam_xpt.c:6319 #67 0xc0122911 in swi_cambio () at ../../cam/cam_xpt.c:6222 #68 0xc022d0e0 in splz_swi () (kgdb) up 63 #64 0xc0178d6b in biodone (bp=0xc16e9588) at ../../kern/vfs_bio.c:2637 2637 (*bp->b_iodone) (bp); (kgdb) print bp $1 = (struct buf *) 0xc16e9588 (kgdb) print *bp->b_iodone $2 = {void ()} 0xc150f6ac (kgdb) down #63 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../dev/vinu m/vinuminterrupt.c:199 199 } (kgdb) list 194 VOL[rq->volplex.volno].active--; /* another request finished */ 195 biodone(ubp); /* top leve l buffer completed */ 196 freerq(rq); /* return t he request storage */ 197 } 198 } 199 } 200 201 /* Free a request block and anything hanging off it */ 202 void 203 freerq(struct request *rq) (kgdb) down #62 0xc023660b in trap (frame={tf_fs = 0xc0270010, tf_es = 0xc0150010, tf_ds = 0x680010, tf_edi = 0xc16e9588, tf_esi = 0xc16e9400, tf_ebp = 0xc02773b0, tf_isp = 0xc0277380, tf_ebx = 0xc208e340, tf_edx = 0x0, tf_ecx = 0x5610001, tf_eax = 0xff9773bf, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0xc150fc67, tf_cs = 0x8, tf_eflags = 0x10246, tf_esp = 0xc16e9588, tf_ss = 0xc14bd000}) at ../../ i386/i386/trap.c:426 426 (void) trap_pfault(&frame, FALSE, eva); (kgdb) up 2 #64 0xc0178d6b in biodone (bp=0xc16e9588) at ../../kern/vfs_bio.c:2637 2637 (*bp->b_iodone) (bp); (kgdb) up #65 0xc0126bb9 in dadone (periph=0xc14ca700, done_ccb=0xc1808400) at ../../cam /scsi/scsi_da.c:1246 1246 biodone(bp); (kgdb) print bp $3 = (struct buf *) 0xc16e9588 (kgdb) print *bp $4 = { b_hash = { le_next = 0x0, le_prev = 0x0 }, b_vnbufs = { tqe_next = 0x0, tqe_prev = 0x0 }, b_freelist = { tqe_next = 0x0, tqe_prev = 0x0 }, b_act = { tqe_next = 0xc16e9820, tqe_prev = 0xc14bd000 }, b_flags = 0x204, b_qindex = 0x0, b_xflags = 0x0, b_lock = { lk_interlock = { lock_data = 0x0 }, lk_flags = 0x400, lk_sharecount = 0x0, lk_waitcount = 0x0, lk_exclusivecount = 0x1, lk_prio = 0x14, lk_wmesg = 0xc0257a24 "bufwait", lk_timo = 0x0, lk_lockholder = 0x5 }, b_error = 0x0, b_bufsize = 0x2000, b_bcount = 0x2000, b_resid = 0x0, b_dev = 0xc15cd880, b_data = 0xcbdcc000 "ÀA\002", b_kvabase = 0x0, b_kvasize = 0x0, b_lblkno = 0x0, b_blkno = 0x2b08149, b_offset = 0x0, b_iodone = 0xc150f6ac , b_iodone_chain = 0x0, b_vp = 0x0, b_dirtyoff = 0x0, b_dirtyend = 0x0, b_rcred = 0xffffffff, b_wcred = 0xffffffff, b_pblkno = 0x2f07c0e, b_saveaddr = 0x0, b_driver1 = 0x0, b_driver2 = 0x0, b_caller1 = 0x0, b_caller2 = 0x0, b_pager = { pg_spc = 0x0, pg_reqpage = 0x0 }, b_cluster = { cluster_head = { tqh_first = 0x0, tqh_last = 0x0 }, cluster_entry = { tqe_next = 0x0, tqe_prev = 0x0 ---Type to continue, or q to quit--- } }, b_pages = {0x0 }, b_npages = 0x0, b_dep = { lh_first = 0x0 }, b_chain = { parent = 0x0, count = 0x0 } } (kgdb) quit matrix# ^Dexit Script done on Sun Oct 22 10:02:36 2000 From: Roman Shterenzon To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/22103: 4.1-R with Adaptec and Vinum crashes on periodic daily Date: Mon, 30 Oct 2000 12:12:30 +0200 (IST) I took another dump today, it crashed in the same place: #63 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../dev/vinu m/vinuminterrupt.c:199 #64 0xc0178d6b in biodone (bp=0xc1caf820) at ../../kern/ vfs_bio.c:2637 #65 0xc0126bb9 in dadone (periph=0xc14ca700, done_ccb=0xc184c800) at ../../cam /scsi/scsi_da.c:1246 --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] From: Daniel Lang To: freebsd-gnats-submit@FreeBSD.org, roman@xpert.com Cc: Subject: Re: kern/22103: 4.1-R with Adaptec and Vinum crashes on periodic daily Date: Fri, 10 Nov 2000 13:57:38 +0000 Hi, See also PR kern/21148 I ran into very similar problems. I could track the crash in periodic daily to the /etc/security script and the find statement within, checking for files with setuid bit set. I could crash the machine reproducable, just by calling find /the/vinum/fs/mountpoint It, too, happened as soon as there has been a bit of data on the fs (~ 70 GB). Best regards, Daniel -- IRCnet: Mr-Spock - Soon I will be free, then hungry. - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* --fdj2RfSjLxBAspz7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 4:32:44 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 04:32:42 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id D1F3D37B400 for ; Wed, 3 Jan 2001 04:32:41 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id OAA00680; Wed, 3 Jan 2001 14:29:58 +0200 To: Thomas Seck Subject: Re: Vinum safe to use for raid 0? Message-ID: <978524998.3a531b460566f@webmail.harmonic.co.il> Date: Wed, 03 Jan 2001 14:29:58 +0200 (IST) From: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG References: <20010102230107.A559@basildon.homerun> In-Reply-To: <20010102230107.A559@basildon.homerun> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Thomas Seck : > Hi all, > > sorry if this is OT for -stable, but I followed the discussion about > vinum in here and got a bit worried. > > I am currently deploying a proxy server for our company. It shall use > squid on 4.2-STABLE. I would like to put the cache data on a vinum RAID > 0, made of three U160 disks. As I understood the discussion so far, > there are some unresolved problems with the raid 5 code. Could someone > tell me whether I can safely use vinum for building a raid 0 system > (despite the fact that the HW may be a point of failure of course)? > > Thanks in advance and best regards from Germany > > -Thomas Seck But why would you want to use it for squid? Just define multiple cachedirs. It's surely more simple to deploy and maintain, and it may even be better in performance. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 5:26:59 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 05:26:56 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with SMTP id 63ADF37B400 for ; Wed, 3 Jan 2001 05:26:50 -0800 (PST) Received: (qmail 16906 invoked by uid 501); 3 Jan 2001 13:26:43 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Jan 2001 13:26:43 -0000 Date: Wed, 3 Jan 2001 11:26:43 -0200 (EDT) From: Paulo Fragoso To: freebsd-stable@freebsd.org Subject: Re: wi0 or isab0 trouble? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've comited a little mistake. I've got a script install and its was changed one line: wicontrol -i wi0 -t 6 to wicontrol -t wi0 -t 6 Our suggestion is "wicontrol" report "invalid option" in cases like this. Excuse-me, Paulo. On Tue, 2 Jan 2001, Paulo Fragoso wrote: > Hi, > > We was using FreeBSD and WaveLAN without problems. But now we are trying > to use 4.2-20001219-STABLE and we are found some problems. We have got > one PII 350MHz (chiset 440 BX motherboard) working fine, but using some > old motherboards we get this error: > > wi0: device timeout > wi0: failed to allocate 1594 bytes on NIC > wi0: tx buffer allocation failed > wi0: failed to alloacte 1594 bytes on NIC > wi0: mgmt. buffer allocation failed > > That old motherboard has got the chipset VIA VT82C576M with a Pentium > 100MHz. Looking at result from dmesg there is a little difference: > > work-> there are isab0 and isa0 at motherboard that works: > isab0: at device 7.0 on pci0 > isa0: on isab0 > > don't work-> there isn't isab0!!!: > isa0: on isab0 > > We've got another older motherboard (chipset intel TX) working fine with > FreeBSD 4.2-RELEASE, and we can found isab0 on dmesg: > isab0: at device 7.0 on pci0 > isa0: on isab0 > > Likely the wi0 require a isab0 (I think). Why when are we using FreeBSD > 4.2-STABLE we can't found a isab0 on old motherboard? Why don't wi0 works? > > We've installed FreeBSD 4.1-RELEASE on same VIA motherboard to test and > all works fine. But on that motherboard we can't found a isab0 with dmesg, > too. Are we thinking wrong? > > When we are using same motherboard (VIA VT82C576M) with FBSD 4.1-RELEASE > are all working fine? We've tested FBSD 4.2-RELEASE and > 4.2-20001219-STABLE and both don't work on this motherboard. > > Finally: Why are all versions tested of FreeBSD working fine using a 440BX > motherboard? > > Thanks, > Paulo Fragoso. > > -- > __O > _-\<,_ Why drive when you can bike? > (_)/ (_) > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 5:52:58 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 05:52:53 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 51FDB37B400; Wed, 3 Jan 2001 05:52:53 -0800 (PST) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: postfix [port 1553]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <111581-223>; Wed, 3 Jan 2001 14:52:44 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 179F513631; Wed, 3 Jan 2001 14:52:33 +0100 (CET) From: Daniel Lang To: grog@FreeBSD.org Cc: Andy Newman , Roman Shterenzon , Daniel Lang , freebsd-gnats-submit@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kern/21148: multiple crashes while using vinum Message-ID: <20010103145232.B10169@atrbg11.informatik.tu-muenchen.de> References: <200101012239.f01MdiH40906@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101012239.f01MdiH40906@freefall.freebsd.org>; from grog@FreeBSD.org on Mon, Jan 01, 2001 at 11:41:19PM +0000 X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Sender: langd@informatik.tu-muenchen.de Date: Wed, 3 Jan 2001 14:52:35 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Greg, Andy, Roman, grog@FreeBSD.org wrote on Mon, Jan 01, 2001 at 11:41:19PM +0000: > Synopsis: multiple crashes while using vinum [..] > State-Changed-Why: > No feedback from submitter. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=21148 Well, I've sent you stack-traces, with (and alas as well without) debugging symbols, I am perfectly aware of your instruction page about debugging vinum, and not an ignorant moron, who complains without reading. Unfortunately you don't seem to trust me or other people in this matter. If you look at my stack-traces again you will notice, that no stack-frame is part of the vinum module, so your .gdb-debugging scripts cannot apply. The reason is, that _some code_ writes into unallocated memory, in my case overwriting a data-structure of an ata-request with a few zero bytes, causing the panic. The stack trace allows me to trace the problem back to this point, but not further. I later experienced a similar problem on a scsi-only system. The reason, why I filed this pr unter 'vinum' is, that it only occured on boxes using vinum, and perfectly reproducable via simple operations like a 'find /vinum/file/system -print' on a larger and moderately filled vinum-filesystem. Perfectly reproducable means: each night, periodic daily caused the panic (traceable to the find call in /etc/security, finding files with setuid bits). As far as I know, the only way to trace this writing into unallocated/otherallocated memory resp. buffer overrun would be to set a watchpoint to the overwritten data-structure within the kernel-debugger. My stack-traces showed that this memory region stays the same on the same machine with the same kernel (although I can't tell how reliable this is). My experiences with kernel code and kernel-debugging with ddb are very limited. So is my time (I know this applies to anyone). Therefore I ceased spending time to set up remote-gdb sessions and sending you stack traces trying to be helpful, since you obviously didn't seem to be interested. I further decided not to use vinum any more. We spent some cash on a few hardware RAIDs, and the boxes run smooth now, since. I am just writing this to state: a) I did respond to your requests, trying to be as helpful as I could. You could blame me for not knowing or willing to learn how to set up a ddb/gdb session using watchpoints and waiting for the next crash in an environmen that should be productive (and now is). b) I still believe, that there is a problem somewhere in the vinum code (probably within raid5 routines, since a mirror setup worked fine). And in fact, I wouldn't have bothered if there weren't any other people like Roman Shterenzon and Andy Newman, who seem to have the same problems. Best regards, Daniel Lang P.S.: I don't use vinum anymore, nor can I take my boxes out of production. The debugging kernels and crash-dumps are no longer present, sorry. -- IRCnet: Mr-Spock - Der Schatten von Hasenfuss ist ziemlich dunkel - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 5:55:57 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 05:55:54 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id F0CC337B402 for ; Wed, 3 Jan 2001 05:55:52 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.11.1/8.11.1) with ESMTP id f03DtLa95126; Wed, 3 Jan 2001 19:55:23 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 3 Jan 2001 19:55:21 +0600 (NS) From: Max Khon To: Erich Zigler Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Threaded C++ Question In-Reply-To: <20010102175034.B43962@superhero.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! > > > In reading through the archives I have seen several emails regarding the > > > problems people have experienced with MySQL, and Mozilla on 4.2 systems. I > > > was wondering if these problems have been resolved in the main source tree > > > yet. > > I'd like to know too. I plan on tackling Mozilla this weekend; it would be > > nice if it was a no-brainer. :-) > > To my knowledge they modified the Mozilla port to work around it. But I am > in the process of porting several C++ apps that are exhibiting truely > strange behavior. And I was wondering if this could be the cause. no fixes has been committed to main source tree so far. David O'Brien posted one workaround for this problem to -stable about two weeks ago. That patch has one problem described here: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21983 I have made another patch available at http://iclub.nsu.ru/~fjoe/libgcc-patch This patch should solve problems with threaded C++ programs and does not break fixes for PR/21983 Your feedback is appreciated (does it work for you or not, does it break backwards compatibility for you or not etc.) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 6:24:54 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 06:24:51 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id CAB7737B402 for ; Wed, 3 Jan 2001 06:24:50 -0800 (PST) Received: (qmail 4304 invoked from network); 3 Jan 2001 14:24:44 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 3 Jan 2001 14:24:44 -0000 Sender: robin@FreeBSD.ORG Message-ID: <3A533618.FFCF985D@gactr.uga.edu> Date: Wed, 03 Jan 2001 09:24:24 -0500 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: buildworld problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i've been having this problem since some time before shortly before christmas: ===> ../secure/lib/libcrypt sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/usr/src/i386/mk usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /usr/src/secure/lib/libcrypt. *** Error code 1 that's been with regular cvs updates done, total removal of /usr/src & /usr/obj -- all to no avail. any idea as to what's up? -- ------------------------------------ Robin P. Blanchard Network Engineering & Support Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 6:40: 5 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 06:40:01 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from tepid.osl.fast.no (tepid.osl.fast.no [213.188.9.130]) by hub.freebsd.org (Postfix) with ESMTP id AB74C37B404 for ; Wed, 3 Jan 2001 06:39:58 -0800 (PST) Received: from raw.grenland.fast.no (fw-oslo.fast.no [213.188.9.129]) by tepid.osl.fast.no (8.9.3/8.9.1) with ESMTP id OAA41342; Wed, 3 Jan 2001 14:53:55 GMT (envelope-from raw@fast.no) Received: (from raw@localhost) by raw.grenland.fast.no (8.11.0/8.11.0) id f03EehZ10115; Wed, 3 Jan 2001 15:40:43 +0100 (CET) (envelope-from raw) From: Raymond Wiker MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14931.14823.208291.448237@raw.grenland.fast.no> Date: Wed, 3 Jan 2001 15:40:39 +0100 (CET) To: "Robin P. Blanchard" Cc: stable@FreeBSD.ORG Subject: buildworld problem In-Reply-To: <3A533618.FFCF985D@gactr.uga.edu> References: <3A533618.FFCF985D@gactr.uga.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: raw@fast.no Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robin P. Blanchard writes: > i've been having this problem since some time before shortly before > christmas: > > ===> ../secure/lib/libcrypt > sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 bsd.README > bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk > bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk > bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk > bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/usr/src/i386/mk > usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] > file1 file2 > install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] > file1 ... > fileN directory > install -d [-v] [-g group] [-m mode] [-o owner] directory ... > *** Error code 64 > > Stop in /usr/src/secure/lib/libcrypt. > *** Error code 1 > > > that's been with regular cvs updates done, total removal of /usr/src & > /usr/obj -- > all to no avail. any idea as to what's up? It's possible that you have several versions of "install" in your path - for example, under /usr/local/bin as well as under /usr/bin. You can check this by typing "which install" or "type install", depending on what shell you're using. Tip: I almost always use "su -" instead of just "su" when I want to become root. Specifying the "-" flag makes su simulate a full login; among other things, this changes your working directory to root's home directory, and gets rid of any path settings that are in effect for your "normal" (i.e, non-root) login. I suspect that install.sh should specify a full path to install (i.e, "/usr/bin/install" instead of just "install"). //Raymond. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 6:44:22 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 06:44:18 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id A6C3137B400 for ; Wed, 3 Jan 2001 06:44:18 -0800 (PST) Received: (qmail 6155 invoked from network); 3 Jan 2001 14:44:17 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 3 Jan 2001 14:44:17 -0000 Sender: robin@FreeBSD.ORG Message-ID: <3A533AAD.9001E463@gactr.uga.edu> Date: Wed, 03 Jan 2001 09:43:57 -0500 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: buildworld problem References: <3A533618.FFCF985D@gactr.uga.edu> <14931.14823.208291.448237@raw.grenland.fast.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Raymond Wiker wrote: > > Robin P. Blanchard writes: > > i've been having this problem since some time before shortly before > > christmas: > > > > ===> ../secure/lib/libcrypt > > sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 bsd.README > > bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk > > bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk > > bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk > > bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/usr/src/i386/mk > > usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] > > file1 file2 > > install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] > > file1 ... > > fileN directory > > install -d [-v] [-g group] [-m mode] [-o owner] directory ... > > *** Error code 64 > > > > Stop in /usr/src/secure/lib/libcrypt. > > *** Error code 1 > > > > > > that's been with regular cvs updates done, total removal of /usr/src & > > /usr/obj -- > > all to no avail. any idea as to what's up? > > It's possible that you have several versions of "install" in > your path - for example, under /usr/local/bin as well as under > /usr/bin. You can check this by typing "which install" or "type > install", depending on what shell you're using. > > Tip: I almost always use "su -" instead of just "su" when I > want to become root. Specifying the "-" flag makes su simulate a full > login; among other things, this changes your working directory to > root's home directory, and gets rid of any path settings that are in > effect for your "normal" (i.e, non-root) login. > > I suspect that install.sh should specify a full path to > install (i.e, "/usr/bin/install" instead of just "install"). install only exists as /usr/bin/install (i also have /usr/local/bin/ginstall). i always su as "su -". nothing in my system has changed except the source tree. i can take a source tree from another one of my machines that hasn't been cvs'ed since early december, and installworld goes just fine. there's something else going on here. -- ------------------------------------ Robin P. Blanchard Network Engineering & Support Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 6:46:40 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 06:46:37 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id 954F837B400 for ; Wed, 3 Jan 2001 06:46:37 -0800 (PST) Received: (qmail 6358 invoked from network); 3 Jan 2001 14:46:37 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 3 Jan 2001 14:46:37 -0000 Sender: robin@FreeBSD.ORG Message-ID: <3A533B39.5BC1D521@gactr.uga.edu> Date: Wed, 03 Jan 2001 09:46:17 -0500 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: buildworld problem References: <3A533618.FFCF985D@gactr.uga.edu> <14931.14823.208291.448237@raw.grenland.fast.no> <3A533AAD.9001E463@gactr.uga.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Robin P. Blanchard" wrote: > > Raymond Wiker wrote: > > > > Robin P. Blanchard writes: > > > i've been having this problem since some time before shortly before > > > christmas: > > > > > > ===> ../secure/lib/libcrypt > > > sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 bsd.README > > > bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk > > > bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk > > > bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk > > > bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/usr/src/i386/mk > > > usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] > > > file1 file2 > > > install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] > > > file1 ... > > > fileN directory > > > install -d [-v] [-g group] [-m mode] [-o owner] directory ... > > > *** Error code 64 > > > > > > Stop in /usr/src/secure/lib/libcrypt. > > > *** Error code 1 > > > > > > > > > that's been with regular cvs updates done, total removal of /usr/src & > > > /usr/obj -- > > > all to no avail. any idea as to what's up? > > > > It's possible that you have several versions of "install" in > > your path - for example, under /usr/local/bin as well as under > > /usr/bin. You can check this by typing "which install" or "type > > install", depending on what shell you're using. > > > > Tip: I almost always use "su -" instead of just "su" when I > > want to become root. Specifying the "-" flag makes su simulate a full > > login; among other things, this changes your working directory to > > root's home directory, and gets rid of any path settings that are in > > effect for your "normal" (i.e, non-root) login. > > > > I suspect that install.sh should specify a full path to > > install (i.e, "/usr/bin/install" instead of just "install"). > > install only exists as /usr/bin/install (i also have > /usr/local/bin/ginstall). > i always su as "su -". nothing in my system has changed except the > source tree. > i can take a source tree from another one of my machines that hasn't > been cvs'ed > since early december, and installworld goes just fine. there's something > else going on here. little typo above...make that buildworld (where my problem is). sorry - -- ------------------------------------ Robin P. Blanchard Network Engineering & Support Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 7:30:36 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 07:30:34 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 8F0BF37B400 for ; Wed, 3 Jan 2001 07:30:33 -0800 (PST) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 9E7722CE74; Wed, 3 Jan 2001 17:30:17 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.1/8.11.1) id f03FSiA14057; Wed, 3 Jan 2001 17:28:44 +0200 (EET) (envelope-from vallo) Date: Wed, 3 Jan 2001 17:28:44 +0200 From: Vallo Kallaste To: Greg Lehey Cc: Josef Karthauser , Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? Message-ID: <20010103172844.D13221@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20010102230107.A559@basildon.homerun> <20010103102943.A770@tao.org.uk> <20010103214829.X4336@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010103214829.X4336@wantadilla.lemis.com>; from grog@lemis.com on Wed, Jan 03, 2001 at 09:48:29PM +1030 Sender: vallo@myhakas.matti.ee Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 09:48:29PM +1030, Greg Lehey wrote: > > As far as I understand from Greg he's not aware of many people who > > are having problems with raid 5. > > Probably. If you know of somebody I don't know of, please let me > know. For a while now I have a old spare Intel Madrona server. It has in current configuration one SCSI backplane with 5 SCA plugs and four Seagate Cheetah disks (old model: 4.3GB 10000rpm). The SCSI controller is onboard Symbios 875. I did some vinum raid-5 tests in November, all what I got was massive filesystem corruption and panics after the degraded volume got rebuilt. I'll probably have this box for yet two weeks or so and my time isn't so limited now, so.. What I can do to help you besides installing latest -stable? Do you have some formalized test procedures or anything to prove the stability of raid-5 configuration? Thanks -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 7:59:53 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 07:59:48 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from brave.vnet (IP1A0848.aic.mesh.ad.jp [211.13.12.218]) by hub.freebsd.org (Postfix) with ESMTP id 738B537B400 for ; Wed, 3 Jan 2001 07:59:46 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by brave.vnet (8.11.1/8.11.1) with ESMTP id f03G2jn01767 for ; Thu, 4 Jan 2001 01:02:46 +0900 (JST) (envelope-from daichi@ongs.net) Date: Thu, 4 Jan 2001 01:02:45 +0900 (JST) From: Daichi GOTO To: stable@FreeBSD.ORG Subject: Re: FUJITSU MO (ATAPI) with FreeBSD 4.2 In-Reply-to: <84775158.978447552384.JavaMail.daichi@localhost> Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Mailer: Yuzu version 1.0 Organization: ONGS Mime-Version: 1.0 Message-ID: <84778799.978537765817.JavaMail.daichi@localhost> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There is a way to use FUJITSU MO (ATAPI) ? > > /home/daichi/work(197) dmesg | grep ata > atapci0: port 0xf000-0xf00f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ad0: 29311MB [59554/16/63] at ata0-master UDMA66 > acd0: CD-RW at ata1-master using PIO4 > ata1-slave: optical device - NO DRIVER! > /home/daichi/work(198) > > I'm using FreeBSD 4.2-Release. But he said "NO DRIVER!". > It is rumored that you can use MO(ATAPI) in FreeBSD-current. > Can I use it with FreeBSD 4.2-Release? I have made simple patch to use MO(ATAPI). --- /sys/dev/ata/atapi-all.c.orig Thu Jan 4 00:23:52 2001 +++ /sys/dev/ata/atapi-all.c Thu Jan 4 00:23:00 2001 @@ -99,6 +99,8 @@ break; #endif #if NATAPIFD > 0 + case ATAPI_TYPE_OPTICAL: + ATP_PARAM->device_type = ATAPI_TYPE_DIRECT; case ATAPI_TYPE_DIRECT: if (afdattach(atp)) goto notfound; The patched kernel says: ... ad0: 29311MB [59554/16/63] at ata0-master UDMA66 acd0: CD-RW at ata1-master using PIO4 afd0: 508MB [508/64/32] at ata1-slave using PIO4 ... How to format disks are follow: 640MB MO FFS Format: # dd if=/dev/zero of=/dev/rafd0 bs=2048 count=1 1+0 records in 1+0 records out 2048 bytes transferred in 0.067482 secs (30349 bytes/sec) # disklabel -r -w afd0 auto # newfs /dev/rafd0c Warning: Block size restricts cylinders per group to 10. Warning: 8192 sector(s) in last cylinder unallocated /dev/rafd0c: 1236992 sectors in 76 cylinders of 1 tracks, 16384 sectors 604.0MB in 8 cyl groups (10 c/g, 80.00MB/g, 9536 i/g) super-block backups (for fsck -b #) at: 32, 163872, 327712, 491552, 655392, 819232, 983072, 1146912 # mount /dev/afd0 /mnt # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 28893073 11180625 15401003 42% / procfs 4 4 0 100% /proc linprocfs 4 4 0 100% /usr/compat/linux/proc /dev/afd0 608814 2 560108 0% /mnt 640MB MO FAT Format: brave# dd if=/dev/zero of=/dev/rafd0 bs=2048 count=1 1+0 records in 1+0 records out 2048 bytes transferred in 0.556006 secs (3683 bytes/sec) brave# disklabel -r -w afd0 auto brave# newfs_msdos -F 32 /dev/rafd0 /dev/rafd0: 308636 sectors in 154318 FAT32 clusters (4096 bytes/cluster) bps=2048 spc=2 res=8 nft=2 mid=0xf0 spt=32 hds=64 hid=0 bsec=309248 bspf=302 rdcl=2 infs=1 bkbs=2 brave# mount_msdos /dev/afd0 /mnt brave# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 28893073 11180631 15400997 42% / procfs 4 4 0 100% /proc linprocfs 4 4 0 100% /usr/compat/linux/proc /dev/afd0 617280 12 617268 0% /mnt 230MB MO FFS: # dd if=/dev/zero of=/dev/rafd0 bs=512 count=1 1+0 records in 1+0 records out 512 bytes transferred in 0.111073 secs (4610 bytes/sec) # disklabel -r -w afd0 auto # newfs /dev/rafd0c Warning: 2048 sector(s) in last cylinder unallocated /dev/rafd0c: 444416 sectors in 109 cylinders of 1 tracks, 4096 sectors 217.0MB in 7 cyl groups (16 c/g, 32.00MB/g, 7744 i/g) super-block backups (for fsck -b #) at: 32, 65568, 131104, 196640, 262176, 327712, 393248 # mount /dev/afd0 /mnt # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 28893073 11180509 15401119 42% / procfs 4 4 0 100% /proc linprocfs 4 4 0 100% /usr/compat/linux/proc /dev/afd0 215303 1 198078 0% /mnt 230MB FAT: # dd if=/dev/zero of=/dev/rafd0 bs=512 count=1 1+0 records in 1+0 records out 512 bytes transferred in 0.109349 secs (4682 bytes/sec) # disklabel -r -w afd0 auto # newfs_msdos -F 32 /dev/rafd0 /dev/rafd0: 443512 sectors in 55439 FAT32 clusters (4096 bytes/cluster) bps=512 spc=8 res=32 nft=2 mid=0xf0 spt=32 hds=64 hid=0 bsec=444416 bspf=434 rdcl=2 infs=1 bkbs=2 # mount_msdos /dev/afd0 /mnt # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 28893073 11180535 15401093 42% / procfs 4 4 0 100% /proc linprocfs 4 4 0 100% /usr/compat/linux/proc /dev/afd0 221764 12 221752 0% /mnt Attention: This is simple patch for MO(ATAPI) only. Do not use with other optical disks(ATAPI). Daichi T.GOTO(ONGS) http://www.ongs.net/daichi, daichi@ongs.gr.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 8:10:31 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 08:10:29 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.shorewood-epc.co.uk (mail.shorewood-epc.co.uk [195.10.240.17]) by hub.freebsd.org (Postfix) with ESMTP id E00FA37B400 for ; Wed, 3 Jan 2001 08:10:27 -0800 (PST) Received: from lfarr (bka.shorewood-epc.co.uk [192.168.15.200]) by mail.shorewood-epc.co.uk (8.9.3/8.9.3) with SMTP id QAA34256 for ; Wed, 3 Jan 2001 16:10:18 GMT (envelope-from lawrence@epcdirect.co.uk) From: "Lawrence Farr" To: Subject: Problem with Syslog and Stable Date: Wed, 3 Jan 2001 16:10:19 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am getting a lot of: Jan 3 16:04:55 frogger syslogd: '/' in "/dev//dev/tty" in /var/log/messages, and my daily run output has: Local system status: uptime: /dev//dev/tty: No such file or directory 2:36AM up 12 days, 9:55, 5 users, load averages: 0.03, 0.01, 0.00 In it. Issuing the w command gives me: w: /dev//dev/tty: No such file or directory 4:07PM up 12 days, 23:26, 6 users, load averages: 0.00, 0.00, 0.00 etc. Im getting this on multiple machines that I have, and all have been built from there own sources to stable on different days/weeks, and a mergemaster -a run. Anyone got any ideas where to start looking? Lawrence Farr EPC Direct Limited mailto:lawrence@epcdirect.co.uk T:01179666123 F:01179666111 M:07970780901 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 9:33: 8 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 09:33:03 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from public.ndh.com (public.ndh.net [195.94.90.21]) by hub.freebsd.org (Postfix) with ESMTP id 4680737B400 for ; Wed, 3 Jan 2001 09:33:02 -0800 (PST) Received: from localhost (port1120.duesseldorf.ndh.net [62.40.8.120]) by public.ndh.com (8.9.3/8.8.0) with ESMTP id SAA08892 for ; Wed, 3 Jan 2001 18:32:55 +0100 (MET) Received: from tmseck by localhost with local (Exim 3.20 #1) id 14DraF-0000AE-00 for freebsd-stable@FreeBSD.ORG; Wed, 03 Jan 2001 18:20:19 +0100 Date: Wed, 3 Jan 2001 18:20:19 +0100 From: Thomas Seck To: freebsd-stable@freebsd.org Subject: Re: Vinum safe to use for raid 0? Message-ID: <20010103182019.A381@basildon.homerun> Mail-Followup-To: Thomas Seck , freebsd-stable@FreeBSD.ORG References: <20010102230107.A559@basildon.homerun> <978524998.3a531b460566f@webmail.harmonic.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <978524998.3a531b460566f@webmail.harmonic.co.il>; from roman@harmonic.co.il on Mi , Jan 03, 2001 at 02:29:58pm +0200 Organization: Die Teilchenbeschleuniger Sender: Thomas Seck Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mi , Jan 03, 2001 at 02:29:58pm +0200, Roman Shterenzon wrote: > Quoting Thomas Seck : (...) > > I am currently deploying a proxy server for our company. It shall use > > squid on 4.2-STABLE. I would like to put the cache data on a vinum RAID > > 0, made of three U160 disks. As I understood the discussion so far, > > there are some unresolved problems with the raid 5 code. Could someone > > tell me whether I can safely use vinum for building a raid 0 system > > (despite the fact that the HW may be a point of failure of course)? (...) > But why would you want to use it for squid? Just define multiple cachedirs. > It's surely more simple to deploy and maintain, and it may even be better in > performance. You are probably right. I am sorry for this slightly premature posting and for firing up this discussion. I dived a bit deeper into the squid documentation (i.e. I read the FAQ) now and noticed this option myself. I had the wrong precaution that squid would use only one cache directory - so vinum came to my mind. But it is nonetheless interesting to hear so many opinions considering vinum. Regards from Germany -Thomas Seck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 9:33:10 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 09:33:06 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from public.ndh.com (public.ndh.net [195.94.90.21]) by hub.freebsd.org (Postfix) with ESMTP id E48D437B402 for ; Wed, 3 Jan 2001 09:33:04 -0800 (PST) Received: from localhost (port1120.duesseldorf.ndh.net [62.40.8.120]) by public.ndh.com (8.9.3/8.8.0) with ESMTP id SAA08913 for ; Wed, 3 Jan 2001 18:33:00 +0100 (MET) Received: from tmseck by localhost with local (Exim 3.20 #1) id 14Drm0-0000C1-00 for freebsd-stable@FreeBSD.ORG; Wed, 03 Jan 2001 18:32:28 +0100 Date: Wed, 3 Jan 2001 18:32:28 +0100 From: Thomas Seck To: freebsd-stable@freebsd.org Subject: Re: Vinum safe to use for raid 0? Message-ID: <20010103183228.B381@basildon.homerun> Mail-Followup-To: Thomas Seck , freebsd-stable@FreeBSD.ORG References: <20010102230107.A559@basildon.homerun> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from scotty@klement.dstorm.net on Mi , Jan 03, 2001 at 12:21:58am -0600 Organization: Die Teilchenbeschleuniger Sender: Thomas Seck Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mi , Jan 03, 2001 at 12:21:58am -0600, scotty@klement.dstorm.net wrote: > > I've been using vinum to mirror some 20gb UDMA66 IDE drives for about 8 > months now. I've even had a drive failure in that time (my 2nd western > digital 20gb drive to die within a year -- I bought a Seagate this time!) (...) > > I don't know if my input is helpful, since I'm not doing striping at all, > but I thought I'd give my 2 cents. :) Yes, thank you - as Roman pointed out I do not need to set up a raid 0 for squid but it is good to know that raid 1 is reliable. I would like to use it for an auxiliary SMB server some time soon. Regards from Germany, -Thomas Seck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 9:51:52 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 09:51:50 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from merrion.ucd.ie (mathsa.ucd.ie [137.43.41.65]) by hub.freebsd.org (Postfix) with ESMTP id B380D37B400 for ; Wed, 3 Jan 2001 09:51:49 -0800 (PST) Received: from localhost (jmcgarr@localhost) by merrion.ucd.ie (8.8.7/8.8.7) with ESMTP id RAA00727; Wed, 3 Jan 2001 17:51:33 GMT X-Authentication-Warning: merrion.ucd.ie: jmcgarr owned process doing -bs Date: Wed, 3 Jan 2001 17:51:33 +0000 (GMT) From: Sean McGarraghy X-Sender: jmcgarr@merrion.ucd.ie Reply-To: john.mcgarraghy@ucd.ie To: Andreas Gerstenberg Cc: STABLE Subject: Re: problems w/ make world... In-Reply-To: <2320948525.977278524@windoze.andy.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Same here: I'm also on 4.2-RELEASE. I recompiled the kernel with no probs at all, but make world fell over with signal 11 errors. I've never had any h/w problems either. Regards - Sean On Wed, 20 Dec 2000, Andreas Gerstenberg wrote: > > > -- Eric M Logan wrote: > > > I'm currently using FreeBSD 4.2 and I cvsup'ed the latest sources > > this morning. Everytime I try doing a make buildworld && make > > installworld (in single user mode and regular), the whole thing crashes > > out w/ signal 11 errors. Any ideas why this might be? And before > > anyone suggests hardware problems let me say this. I've been able to > > I've had the same problem with the 4.2-RELEASE (new installation) and I've > also changed the whole hardware without success. In every try it was the same > file (something while compiling gcc) where I got the SIG 11. Since I've > > regards, > Andy > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 10:38: 6 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 10:38:03 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D66C437B402 for ; Wed, 3 Jan 2001 10:38:02 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA89376; Wed, 3 Jan 2001 10:37:57 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f03Ibug62233; Wed, 3 Jan 2001 10:37:56 -0800 (PST) (envelope-from obrien) Date: Wed, 3 Jan 2001 10:37:55 -0800 From: "David O'Brien" To: Max Khon Cc: stable@freebsd.org Subject: Re: C++ threaded programs Message-ID: <20010103103755.A62189@dragon.nuxi.com> Reply-To: stable@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 fjoe@iclub.nsu.ru on Thu, Jan 04, 2001 at 12:29:17AM +0600 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: obrien@NUXI.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 12:29:17AM +0600, Max Khon wrote: > Can you tell me what do you plan on "C++ threaded programs > segfault" issue? Still fixing issues. Compiling -static is broken with my latest patch. Dan and I have a 2nd patch we are reviewing and testing. > At this time I give people the same patch that I sent you about two weeks > ago (you can get it at http://iclub.nsu.ru/~fjoe) -- only one libgcc.a > (with threads support, -fpic) is built with it and it is linked into > shared objects. I had to tweat that some (based on what I had at the time). I guess I should just post my patch. I have been unable to get anyone I've directly asked to actually test it (that emailed me saying they have a problem with the current state of the world). -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 10:40:48 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 10:40:45 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4902237B400 for ; Wed, 3 Jan 2001 10:40:45 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA89406; Wed, 3 Jan 2001 10:40:44 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f03IehD62284; Wed, 3 Jan 2001 10:40:43 -0800 (PST) (envelope-from obrien) Date: Wed, 3 Jan 2001 10:40:43 -0800 From: "David O'Brien" To: Erich Zigler Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Threaded C++ Question Message-ID: <20010103104042.B62250@dragon.nuxi.com> Reply-To: stable@FreeBSD.ORG References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> <20010102175034.B43962@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010102175034.B43962@superhero.org>; from erichz@superhero.org on Tue, Jan 02, 2001 at 05:50:34PM -0600 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: obrien@NUXI.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 05:50:34PM -0600, Erich Zigler wrote: > But I am in the process of porting several C++ apps that are exhibiting > truely strange behavior. And I was wondering if this could be the > cause. I will post a patch -- will you test it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 10:42:33 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 10:42:31 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 638F937B400 for ; Wed, 3 Jan 2001 10:42:31 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA89393 for ; Wed, 3 Jan 2001 10:39:50 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f03IdmB62270; Wed, 3 Jan 2001 10:39:48 -0800 (PST) (envelope-from obrien) Date: Wed, 3 Jan 2001 10:39:48 -0800 From: "David O'Brien" To: Jim King Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Threaded C++ Question Message-ID: <20010103103948.A62250@dragon.nuxi.com> Reply-To: stable@FreeBSD.ORG References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004101c07515$206f9340$04e48486@marble>; from jim@jimking.net on Tue, Jan 02, 2001 at 05:38:33PM -0600 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: obrien@NUXI.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 02, 2001 at 05:38:33PM -0600, Jim King wrote: > I'd like to know too. I plan on tackling Mozilla this weekend; it would be > nice if it was a no-brainer. :-) I was unable to get our mozilla port to segfault with with or without the patch I'm planning on committing. It would be quite helpful if people could explain how to experience the problem. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 10:43:52 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 10:43:43 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 475DF37B400 for ; Wed, 3 Jan 2001 10:43:41 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA89424; Wed, 3 Jan 2001 10:43:40 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f03IhY162327; Wed, 3 Jan 2001 10:43:34 -0800 (PST) (envelope-from obrien) Date: Wed, 3 Jan 2001 10:43:34 -0800 From: "David O'Brien" To: Erich Zigler , freebsd-stable@FreeBSD.ORG Subject: Re: Threaded C++ Question Message-ID: <20010103104333.C62250@dragon.nuxi.com> Reply-To: stable@FreeBSD.ORG References: <20010102175034.B43962@superhero.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 fjoe@iclub.nsu.ru on Wed, Jan 03, 2001 at 07:55:21PM +0600 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: obrien@NUXI.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 07:55:21PM +0600, Max Khon wrote: > I have made another patch available at Use this patch instead. Note that with it, things are broken if you use -static. I have been unable to get a good test report on what I plan to commit. If you are able to test it, here it is. What I want to see is, take a stock [and up to date] RELENG_4 or 5-CURRENT box and test your application to see that it fails. Apply my patch, do a full `make world' + reboot. Then run your application and test if it does or doesn't work. Report back here. Index: gnu/lib/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/lib/Makefile,v retrieving revision 1.29 diff -u -r1.29 Makefile --- gnu/lib/Makefile 2000/11/25 13:04:08 1.29 +++ gnu/lib/Makefile 2000/12/25 22:37:00 @@ -2,8 +2,10 @@ SUBDIR= csu libdialog libgcc libgmp libmp libregex libreadline +.if ${OBJFORMAT} == aout .if !defined(NOLIBC_R) SUBDIR+= libgcc_r +.endif .endif .if !defined(NO_CXX) Index: gnu/lib/libgcc/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/lib/libgcc/Makefile,v retrieving revision 1.33 diff -u -r1.33 Makefile --- gnu/lib/libgcc/Makefile 2000/06/04 06:56:21 1.33 +++ gnu/lib/libgcc/Makefile 2000/12/25 22:38:41 @@ -4,12 +4,15 @@ .PATH: ${GCCDIR}/cp ${GCCDIR} +# allow to be overridden for the a.out case .if !defined(LIB) || ${LIB} != "gcc_r" LIB= gcc .endif +.if ${OBJFORMAT} == aout # Install libgcc_pic.a, since ld.so uses it. INSTALL_PIC_ARCHIVE= yes +.endif # # XXX This is a hack, but it seems to work. libgcc1.a is supposed to be @@ -59,6 +62,9 @@ CFLAGS+= -I${GCCDIR}/config -I${GCCDIR} -I. CFLAGS+= -fexceptions CFLAGS+= -DIN_GCC +.if ${OBJFORMAT} != aout +CFLAGS+= -D_PTHREADS -fPIC -DGTHREAD_USE_WEAK +.endif CXXFLAGS+= -I${GCCDIR}/cp/inc CXXFLAGS+= -nostdinc++ Index: gnu/usr.bin/cc/cc_tools/freebsd-native.h =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h,v retrieving revision 1.7 diff -u -r1.7 freebsd-native.h --- gnu/usr.bin/cc/cc_tools/freebsd-native.h 2000/11/10 16:54:45 1.7 +++ gnu/usr.bin/cc/cc_tools/freebsd-native.h 2000/12/21 22:10:18 @@ -46,13 +46,3 @@ /* FreeBSD is 4.4BSD derived */ #define bsd4_4 - -/* Tell gcc to locate libgcc.a for us according to the -m rules. */ -#undef LIBGCC_SPEC -#define LIBGCC_SPEC \ - "%{!shared: \ - %{!pthread:libgcc.a%s} \ - %{pthread:libgcc_r.a%s}} \ - %{shared: \ - %{!pthread:libgcc_pic.a%s} \ - %{pthread:libgcc_r_pic.a%s}}" Index: lib/libpam/modules/pam_cleartext_pass_ok/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_cleartext_pass_ok/Makefile,v retrieving revision 1.3 diff -u -r1.3 Makefile --- lib/libpam/modules/pam_cleartext_pass_ok/Makefile 2000/03/27 15:24:45 1.3 +++ lib/libpam/modules/pam_cleartext_pass_ok/Makefile 2000/12/21 22:10:18 @@ -31,8 +31,8 @@ SRCS= pam_cleartext_pass_ok.c CFLAGS+= -I${PAMDIR}/libpam/include CFLAGS+= -Wall -DPADD= ${LIBSKEY} ${LIBGCC_PIC} -LDADD= -lskey -lgcc_pic +DPADD= ${LIBSKEY} +LDADD= -lskey INTERNALLIB= yes INTERNALSTATICLIB=yes Index: lib/libpam/modules/pam_deny/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_deny/Makefile,v retrieving revision 1.1 diff -u -r1.1 Makefile --- lib/libpam/modules/pam_deny/Makefile 1999/05/08 01:59:25 1.1 +++ lib/libpam/modules/pam_deny/Makefile 2000/12/21 22:10:18 @@ -33,8 +33,6 @@ SRCS= pam_deny.c CFLAGS+= -Wall CFLAGS+= -I${PAMDIR}/libpam/include -DPADD+= ${LIBGCC_PIC} -LDADD+= -lgcc_pic INTERNALLIB= yes INTERNALSTATICLIB=yes Index: lib/libpam/modules/pam_kerberosIV/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_kerberosIV/Makefile,v retrieving revision 1.5 diff -u -r1.5 Makefile --- lib/libpam/modules/pam_kerberosIV/Makefile 2000/02/24 22:24:36 1.5 +++ lib/libpam/modules/pam_kerberosIV/Makefile 2000/12/21 22:10:18 @@ -39,8 +39,8 @@ DPADD+= ${LIBCRYPTO} LDADD+= -lcrypto .endif -DPADD+= ${LIBGCC_PIC} ${LIBCOM_ERR} -LDADD+= -lgcc_pic -lcom_err +DPADD+= ${LIBCOM_ERR} +LDADD+= -lcom_err INTERNALLIB= yes INTERNALSTATICLIB=yes Index: lib/libpam/modules/pam_opie/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_opie/Makefile,v retrieving revision 1.1 diff -u -r1.1 Makefile --- lib/libpam/modules/pam_opie/Makefile 2000/04/17 00:14:41 1.1 +++ lib/libpam/modules/pam_opie/Makefile 2000/12/21 22:10:18 @@ -33,8 +33,8 @@ CFLAGS+= -Wall -g CFLAGS+= -I${PAMDIR}/libpam/include CFLAGS+= -I${.CURDIR}/../../libpam -DPADD+= ${LIBOPIE} ${LIBGCC_PIC} -LDADD+= -lopie -lgcc_pic +DPADD+= ${LIBOPIE} +LDADD+= -lopie INTERNALLIB= yes INTERNALSTATICLIB=yes Index: lib/libpam/modules/pam_permit/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_permit/Makefile,v retrieving revision 1.1 diff -u -r1.1 Makefile --- lib/libpam/modules/pam_permit/Makefile 1999/05/08 01:59:25 1.1 +++ lib/libpam/modules/pam_permit/Makefile 2000/12/21 22:10:18 @@ -34,8 +34,6 @@ CFLAGS+= -Wall CFLAGS+= -I${PAMDIR}/libpam/include CFLAGS+= -I${.CURDIR}/../../libpam -DPADD+= ${LIBGCC_PIC} -LDADD+= -lgcc_pic INTERNALLIB= yes INTERNALSTATICLIB=yes Index: lib/libpam/modules/pam_radius/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_radius/Makefile,v retrieving revision 1.4 diff -u -r1.4 Makefile --- lib/libpam/modules/pam_radius/Makefile 1999/08/20 18:32:45 1.4 +++ lib/libpam/modules/pam_radius/Makefile 2000/12/21 22:10:18 @@ -32,8 +32,8 @@ CFLAGS+= -Wall CFLAGS+= -I${PAMDIR}/libpam/include CFLAGS+= -I${.CURDIR}/../../libpam -DPADD+= ${LIBRADIUS} ${LIBGCC_PIC} -LDADD+= -lradius -lgcc_pic +DPADD+= ${LIBRADIUS} +LDADD+= -lradius INTERNALLIB= yes INTERNALSTATICLIB=yes Index: lib/libpam/modules/pam_skey/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_skey/Makefile,v retrieving revision 1.2 diff -u -r1.2 Makefile --- lib/libpam/modules/pam_skey/Makefile 1999/01/20 21:55:27 1.2 +++ lib/libpam/modules/pam_skey/Makefile 2000/12/21 22:10:18 @@ -32,8 +32,8 @@ CFLAGS+= -Wall CFLAGS+= -I${PAMDIR}/libpam/include CFLAGS+= -I${.CURDIR}/../../libpam -DPADD+= ${LIBSKEY} ${LIBGCC_PIC} -LDADD+= -lskey -lgcc_pic +DPADD+= ${LIBSKEY} +LDADD+= -lskey INTERNALLIB= yes INTERNALSTATICLIB=yes Index: lib/libpam/modules/pam_ssh/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_ssh/Makefile,v retrieving revision 1.2 diff -u -r1.2 Makefile --- lib/libpam/modules/pam_ssh/Makefile 2000/03/06 15:28:30 1.2 +++ lib/libpam/modules/pam_ssh/Makefile 2000/12/21 22:10:18 @@ -7,8 +7,8 @@ SHLIB_NAME= pam_ssh.so SRCS= log-client.c pam_ssh.c CFLAGS+= -Wall -I${SSHSRC} -DPADD+= ${LIBCRYPTO} ${LIBCRYPT} ${LIBUTIL} ${LIBZ} ${LIBGCC_PIC} -LDADD+= -L${.OBJDIR}/../../../../secure/lib/libssh -lssh -lcrypto -lcrypt -lutil -lz -lgcc_pic +DPADD+= ${LIBCRYPTO} ${LIBCRYPT} ${LIBUTIL} ${LIBZ} +LDADD+= -L${.OBJDIR}/../../../../secure/lib/libssh -lssh -lcrypto -lcrypt -lutil -lz INTERNALLIB= yes INTERNALSTATICLIB=yes Index: lib/libpam/modules/pam_tacplus/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_tacplus/Makefile,v retrieving revision 1.2 diff -u -r1.2 Makefile --- lib/libpam/modules/pam_tacplus/Makefile 1999/01/20 21:55:28 1.2 +++ lib/libpam/modules/pam_tacplus/Makefile 2000/12/21 22:10:18 @@ -32,8 +32,8 @@ CFLAGS+= -Wall CFLAGS+= -I${PAMDIR}/libpam/include CFLAGS+= -I${.CURDIR}/../../libpam -DPADD+= ${LIBTACPLUS} ${LIBGCC_PIC} -LDADD+= -ltacplus -lgcc_pic +DPADD+= ${LIBTACPLUS} +LDADD+= -ltacplus INTERNALLIB= yes INTERNALSTATICLIB=yes Index: lib/libpam/modules/pam_unix/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_unix/Makefile,v retrieving revision 1.4 diff -u -r1.4 Makefile --- lib/libpam/modules/pam_unix/Makefile 1999/09/30 18:53:34 1.4 +++ lib/libpam/modules/pam_unix/Makefile 2000/12/21 22:10:18 @@ -32,8 +32,8 @@ CFLAGS+= -Wall CFLAGS+= -I${PAMDIR}/libpam/include CFLAGS+= -I${.CURDIR}/../../libpam -DPADD+= ${LIBUTIL} ${LIBGCC_PIC} ${LIBCRYPT} -LDADD+= -lutil -lgcc_pic -lcrypt +DPADD+= ${LIBUTIL} ${LIBCRYPT} +LDADD+= -lutil -lcrypt INTERNALLIB= yes INTERNALSTATICLIB=yes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 10:55: 7 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 10:55:05 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id 9D2A837B400 for ; Wed, 3 Jan 2001 10:55:04 -0800 (PST) Received: (qmail 58561 invoked from network); 3 Jan 2001 18:54:59 -0000 Received: from unknown (HELO prydn.tacni.net) (207.55.167.31) by 216.178.136.168 with SMTP; 3 Jan 2001 18:54:59 -0000 Received: (qmail 5426 invoked by uid 1001); 3 Jan 2001 18:54:18 -0000 Date: Wed, 3 Jan 2001 12:54:18 -0600 From: Erich Zigler To: stable@FreeBSD.ORG Subject: Re: Threaded C++ Question Message-ID: <20010103125418.C5283@superhero.org> References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> <20010102175034.B43962@superhero.org> <20010103104042.B62250@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: <20010103104042.B62250@dragon.nuxi.com>; from TrimYourCc@NUXI.com on Wed, Jan 03, 2001 at 10:40:43AM -0800 X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: needo@prydn.tacni.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 10:40:43AM -0800, David O'Brien wrote: > > But I am in the process of porting several C++ apps that are exhibiting > > truely strange behavior. And I was wondering if this could be the > > cause. > I will post a patch -- will you test it? Yes. For the test should I compile the conflicting program before the make world or after it? Truth be told, this may be a fault in the program Im trying to port it is heavily "Linuxfied." But I have a couple others I can test with too. -- Erich Zigler This 'telephone' has too many shortcomings to be seriously considered as a means of communication. The device is inherently of no value to us. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 11:24:37 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 11:24:34 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 2807B37B400; Wed, 3 Jan 2001 11:24:34 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id OAA22450; Wed, 3 Jan 2001 14:24:07 -0500 (EST) Date: Wed, 3 Jan 2001 14:24:07 -0500 (EST) From: Daniel Eischen To: obrien@FreeBSD.ORG Cc: Max Khon , stable@FreeBSD.ORG Subject: Re: C++ threaded programs In-Reply-To: <20010103103755.A62189@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Jan 2001, David O'Brien wrote: > On Thu, Jan 04, 2001 at 12:29:17AM +0600, Max Khon wrote: > > Can you tell me what do you plan on "C++ threaded programs > > segfault" issue? > > Still fixing issues. > Compiling -static is broken with my latest patch. > Dan and I have a 2nd patch we are reviewing and testing. BTW, it passes all my tests. If it passes all yours, I'd say commit it. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 11:51:23 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 11:51:20 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 09F2737B400 for ; Wed, 3 Jan 2001 11:51:20 -0800 (PST) Received: from jking (jking.lgc.com [134.132.76.82]) by cgi.sstar.com (8.11.1/8.11.1) with SMTP id f03JpDE19286 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO) for ; Wed, 3 Jan 2001 13:51:19 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <00e201c075be$8a500570$524c8486@jking> From: "Jim King" To: References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> <20010103103948.A62250@dragon.nuxi.com> Subject: Re: Threaded C++ Question Date: Wed, 3 Jan 2001 13:51:13 -0600 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > On Tue, Jan 02, 2001 at 05:38:33PM -0600, Jim King wrote: > > I'd like to know too. I plan on tackling Mozilla this weekend; it would be > > nice if it was a no-brainer. :-) > > I was unable to get our mozilla port to segfault with with or without the > patch I'm planning on committing. > > It would be quite helpful if people could explain how to experience the > problem. As of a couple weeks ago Mozilla M18 running on several flavors of 4.2 (RELEASE and a couple different -stable's) would segfault immediately on startup every time. This happened when I built it using the port, and when I used the binary from mozilla.org. I haven't tried it since then, due to the messages here about unresolved library bugs being the cause of the problem. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 11:53:36 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 11:53:33 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.com (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 6271F37B400 for ; Wed, 3 Jan 2001 11:53:33 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.com (Postfix) with ESMTP id ECE6C177E11; Wed, 3 Jan 2001 13:57:38 -0600 (CST) Message-ID: <00d601c075bf$643e9440$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Jim King" , References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> <20010103103948.A62250@dragon.nuxi.com> <00e201c075be$8a500570$524c8486@jking> Subject: Re: Threaded C++ Question Date: Wed, 3 Jan 2001 13:57:24 -0600 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That was the same problem I encountered > As of a couple weeks ago Mozilla M18 running on several flavors of 4.2 > (RELEASE and a couple different -stable's) would segfault immediately on > startup every time. This happened when I built it using the port, and when > I used the binary from mozilla.org. I haven't tried it since then, due to > the messages here about unresolved library bugs being the cause of the > problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 12: 3:55 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 12:03:53 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id A686F37B400; Wed, 3 Jan 2001 12:03:47 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.11.1/8.11.1) with ESMTP id f03K3Qt10511; Thu, 4 Jan 2001 02:03:26 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 4 Jan 2001 02:03:25 +0600 (NS) From: Max Khon To: Daniel Eischen Cc: obrien@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: C++ threaded programs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Wed, 3 Jan 2001, Daniel Eischen wrote: > > > Can you tell me what do you plan on "C++ threaded programs > > > segfault" issue? > > > > Still fixing issues. > > Compiling -static is broken with my latest patch. > > Dan and I have a 2nd patch we are reviewing and testing. > > BTW, it passes all my tests. If it passes all yours, I'd say > commit it. this patch differs from my patch only in a.out compatibility bits and -fpic vs. -fPIC flags when compiling libgcc.a. So I am all for committing it (sorry really have no time to rebuild world one more time) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 12:17:27 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 12:17:25 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 52F9737B400 for ; Wed, 3 Jan 2001 12:17:25 -0800 (PST) Received: from jking (jking.lgc.com [134.132.76.82]) by cgi.sstar.com (8.11.1/8.11.1) with SMTP id f03KHIE20474 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO) for ; Wed, 3 Jan 2001 14:17:24 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <011601c075c2$2f956900$524c8486@jking> From: "Jim King" To: References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> <20010103103948.A62250@dragon.nuxi.com> <00e201c075be$8a500570$524c8486@jking> Subject: Re: Threaded C++ Question Date: Wed, 3 Jan 2001 14:17:18 -0600 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim King wrote: > David O'Brien wrote: > > > On Tue, Jan 02, 2001 at 05:38:33PM -0600, Jim King wrote: > > > I'd like to know too. I plan on tackling Mozilla this weekend; it would > be > > > nice if it was a no-brainer. :-) > > > > I was unable to get our mozilla port to segfault with with or without the > > patch I'm planning on committing. > > > > It would be quite helpful if people could explain how to experience the > > problem. > > As of a couple weeks ago Mozilla M18 running on several flavors of 4.2 > (RELEASE and a couple different -stable's) would segfault immediately on > startup every time. This happened when I built it using the port, and when > I used the binary from mozilla.org. I haven't tried it since then, due to > the messages here about unresolved library bugs being the cause of the > problem. otoh... On a 4.2-stable built yesterday and a freshly-built gtk12 port, the Mozilla M18 binary from mozilla.org runs fine. Cool! Now to take a shot at getting Mozilla 0.6 built and running... Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 12:17:46 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 12:17:44 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id DE9A937B400 for ; Wed, 3 Jan 2001 12:17:42 -0800 (PST) Received: (qmail 28343 invoked by uid 0); 3 Jan 2001 20:17:32 -0000 Received: from p3ee21632.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.50) by mail.gmx.net (mail07) with SMTP; 3 Jan 2001 20:17:32 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id TAA15766 for freebsd-stable@FreeBSD.ORG; Wed, 3 Jan 2001 19:47:22 +0100 Date: Wed, 3 Jan 2001 19:47:22 +0100 From: Gerhard Sittig To: freebsd-stable@FreeBSD.ORG Subject: Re: fetch problem Message-ID: <20010103194722.X253@speedy.gsinet> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <20010102132905.A15311@math.uic.edu> <5.0.2.1.2.20010103020936.08932118@mail.veetvision.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <5.0.2.1.2.20010103020936.08932118@mail.veetvision.com>; from ravi@veetvision.com on Wed, Jan 03, 2001 at 02:10:47AM +0530 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ recycling the message since the original went to /dev/null ] On Wed, Jan 03, 2001 at 02:10 +0530, Ravi Jethani wrote: > > At 01:29 PM 1/2/2001 -0600, Vladimir V. Egorin wrote: > >Dear -STABLE Users, > > > >I ran into some problems with the ports collection (the system is > >4.2-STABLE, built on Dec 21). My machine is sitting behind > >a proxy server (proxying http/ftp requests). > > > >I've set > >export FTP_PROXY=ftp://proxy_address:1080/ > >export HTTP_PROXY=ftp://proxy_address:1080/ > >I've also tried setting FTP_PASSIVE_MODE. Isn't the URL for an FTP proxy http(!)://proxy.ip:port/ ? > >Fetch fails with the messages: > > > > >> libtool-1.3.4.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > > >> Attempting to fetch from ftp://ftp.gnu.org/gnu/libtool/. > >fetch: libtool-1.3.4.tar.gz: Protocol error This makes sense if you try to talk FTP to an HTTP service. :) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 12:22:46 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 12:22:43 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 202B237B404 for ; Wed, 3 Jan 2001 12:22:43 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id PAA02181; Wed, 3 Jan 2001 15:22:18 -0500 (EST) Date: Wed, 3 Jan 2001 15:22:17 -0500 (EST) From: Daniel Eischen To: Jim King Cc: stable@FreeBSD.ORG Subject: Re: Threaded C++ Question In-Reply-To: <011601c075c2$2f956900$524c8486@jking> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Jan 2001, Jim King wrote: > Jim King wrote: > > > David O'Brien wrote: > > > > > On Tue, Jan 02, 2001 at 05:38:33PM -0600, Jim King wrote: > > > > I'd like to know too. I plan on tackling Mozilla this weekend; it > would > > be > > > > nice if it was a no-brainer. :-) > > > > > > I was unable to get our mozilla port to segfault with with or without > the > > > patch I'm planning on committing. > > > > > > It would be quite helpful if people could explain how to experience the > > > problem. > > > > As of a couple weeks ago Mozilla M18 running on several flavors of 4.2 > > (RELEASE and a couple different -stable's) would segfault immediately on > > startup every time. This happened when I built it using the port, and > when > > I used the binary from mozilla.org. I haven't tried it since then, due to > > the messages here about unresolved library bugs being the cause of the > > problem. > > otoh... On a 4.2-stable built yesterday and a freshly-built gtk12 port, the > Mozilla M18 binary from mozilla.org runs fine. Cool! That's because they changed the mozilla port to work around the problem with libgcc (I believe with an explicit link -lgcc_r). This should be reverted once the correct fix is committed to libgcc and friends. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 12:31: 5 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 12:31:02 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 55F2B37B400 for ; Wed, 3 Jan 2001 12:30:58 -0800 (PST) Received: from jking (jking.lgc.com [134.132.76.82]) by cgi.sstar.com (8.11.1/8.11.1) with SMTP id f03KUoE20929 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Wed, 3 Jan 2001 14:30:56 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <012701c075c4$13718360$524c8486@jking> From: "Jim King" To: "Daniel Eischen" Cc: References: Subject: Re: Threaded C++ Question Date: Wed, 3 Jan 2001 14:30:50 -0600 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel Eischen" wrote: > On Wed, 3 Jan 2001, Jim King wrote: > > Jim King wrote: > > > > > David O'Brien wrote: > > > > > > > On Tue, Jan 02, 2001 at 05:38:33PM -0600, Jim King wrote: > > > > > I'd like to know too. I plan on tackling Mozilla this weekend; it > > would > > > be > > > > > nice if it was a no-brainer. :-) > > > > > > > > I was unable to get our mozilla port to segfault with with or without > > the > > > > patch I'm planning on committing. > > > > > > > > It would be quite helpful if people could explain how to experience the > > > > problem. > > > > > > As of a couple weeks ago Mozilla M18 running on several flavors of 4.2 > > > (RELEASE and a couple different -stable's) would segfault immediately on > > > startup every time. This happened when I built it using the port, and > > when > > > I used the binary from mozilla.org. I haven't tried it since then, due to > > > the messages here about unresolved library bugs being the cause of the > > > problem. > > > > otoh... On a 4.2-stable built yesterday and a freshly-built gtk12 port, the > > Mozilla M18 binary from mozilla.org runs fine. Cool! > > That's because they changed the mozilla port to work around the > problem with libgcc (I believe with an explicit link -lgcc_r). > This should be reverted once the correct fix is committed to > libgcc and friends. But I didn't build Mozilla from the port, I downloaded the binary from mozilla.org. Something in -stable must have changed since the last time I tried to run the binary from mozilla.org. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 12:40:37 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 12:40:33 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 651FE37B400 for ; Wed, 3 Jan 2001 12:40:29 -0800 (PST) Received: from gorean.org (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id MAA13305; Wed, 3 Jan 2001 12:40:25 -0800 (PST) (envelope-from DougB@gorean.org) Message-ID: <3A538E39.FA02E0CD@gorean.org> Date: Wed, 03 Jan 2001 12:40:25 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Hans de Hartog Cc: freebsd-stable@freebsd.org Subject: Re: mergemaster problem and apache+ssl problem References: <3A427A03.FA9EF800@chello.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hans de Hartog wrote: > > I'm not a newbie but it's the first time I tried to keep stable by > cvsup (today), make buildworld (no problems), make buildkernel (OK), > reboot (yes, being a good boy I was single user), make installworld > (Ok, but didn't read all the messages :-) and then mergemaster died with > > install -c -o root -g wheel -m 644 freebsd.cf > /var/tmp/temproot/etc/mail/sendmail.cf > install: freebsd.cf: No such file or directory > *** Error 71 That's very strange. Have you done something unusual related to sendmail? Or perhaps have you set any make.conf variables related to sendmail? Mergemaster uses the makefile in /usr/src/etc to build and install it's files, so it should work 99.9% of the time. > So I rebooted and was prepared to manually upgrade my whole /etc from > /var/tmp/temproot/etc. Then I noticed that lots of other things where > missing there that are in my original /etc (from the 4.2 RELEASE CD, > everything dated november 20). My fault? Just curious. No, there are a lot of files that are installed during a standard installation that aren't located in /usr/src. This may or may not be a good thing, but in any case, it's not something to worry about. If there are no copies in /var/tmp/temproot you don't have to worry about updating them. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 12:53:26 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 12:53:22 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from nu.nu.cuk.nu (nu.nu.cuk.nu [212.30.95.50]) by hub.freebsd.org (Postfix) with ESMTP id AFF6737B400; Wed, 3 Jan 2001 12:53:21 -0800 (PST) Received: from nu.cuk.nu (cuk.localnet [192.168.6.11]) by nu.nu.cuk.nu (Postfix) with ESMTP id 860631AB6B; Wed, 3 Jan 2001 21:53:23 +0100 (CET) Message-ID: <3A5390E8.953CAD50@nu.cuk.nu> Date: Wed, 03 Jan 2001 21:51:52 +0100 From: Marko Cuk X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Lang Cc: grog@FreeBSD.org, Andy Newman , Roman Shterenzon , freebsd-gnats-submit@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kern/21148: multiple crashes while using vinum References: <200101012239.f01MdiH40906@freefall.freebsd.org> <20010103145232.B10169@atrbg11.informatik.tu-muenchen.de> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the same problems on IDE and SCSI configuration on 4.0, 4.1, 4.1.1 . I spent cash on buying 2 x 40Gig IDE Wd's and put them into mirror. That was a few months ago. I had crashes also with bridging, but Bosko Milekic and Thomas fixed the code with a little help and bridge works superb in 4.2 STABLE. So I was still interested in RAID5 and also very curious about Vinum in 4.2 so I decided to test that thing with same disks ( old SCSI disks , bud good ) and belive or not, it works also under heavy load. It is strange, but I didn't change anything. Controller was the same Adaptec, cables were the same, disks also. Bsd was 4.2 STABLE. Please try it on 4.2 STABLE and report. I must admit, that I am not a FreeBSD hacker, I don't know many about debugging and I was very unhelpful to Grog, but he is very sure, that Vinum works and I don't like his way of thinking about that. I also set him account on that maschine, to check and debug problems on that maschine and repair them, but he wasn't interested in solving such problems. He blamed me for config or some other mistake. Vinum and RAID5 under 4.1 is not stable. That's all. Cuk Daniel Lang wrote: > Dear Greg, Andy, Roman, > > grog@FreeBSD.org wrote on Mon, Jan 01, 2001 at 11:41:19PM +0000: > > Synopsis: multiple crashes while using vinum > [..] > > State-Changed-Why: > > No feedback from submitter. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=21148 > > Well, I've sent you stack-traces, with (and alas as well without) > debugging symbols, I am perfectly aware of your instruction page > about debugging vinum, and not an ignorant moron, who complains > without reading. Unfortunately you don't seem to trust me > or other people in this matter. > > If you look at my stack-traces again you will notice, that no > stack-frame is part of the vinum module, so your .gdb-debugging > scripts cannot apply. > > The reason is, that _some code_ writes into unallocated memory, > in my case overwriting a data-structure of an ata-request > with a few zero bytes, causing the panic. The stack trace > allows me to trace the problem back to this point, but not > further. I later experienced a similar problem on a > scsi-only system. > > The reason, why I filed this pr unter 'vinum' is, that it only > occured on boxes using vinum, and perfectly reproducable > via simple operations like a 'find /vinum/file/system -print' > on a larger and moderately filled vinum-filesystem. > Perfectly reproducable means: each night, periodic daily > caused the panic (traceable to the find call in /etc/security, > finding files with setuid bits). > > As far as I know, the only way to trace this writing into > unallocated/otherallocated memory resp. buffer overrun > would be to set a watchpoint to the overwritten data-structure > within the kernel-debugger. My stack-traces showed that this > memory region stays the same on the same machine with the > same kernel (although I can't tell how reliable this is). > My experiences with kernel code and kernel-debugging with > ddb are very limited. So is my time (I know this applies > to anyone). Therefore I ceased spending time to set up > remote-gdb sessions and sending you stack traces trying to be > helpful, since you obviously didn't seem to be interested. > > I further decided not to use vinum any more. We spent some > cash on a few hardware RAIDs, and the boxes run smooth now, > since. > > I am just writing this to state: > a) I did respond to your requests, trying to be as helpful as > I could. You could blame me for not knowing or willing to > learn how to set up a ddb/gdb session using watchpoints > and waiting for the next crash in an environmen that should > be productive (and now is). > b) I still believe, that there is a problem somewhere in the > vinum code (probably within raid5 routines, since a mirror > setup worked fine). > > And in fact, I wouldn't have bothered if there weren't any > other people like Roman Shterenzon and Andy Newman, > who seem to have the same problems. > > Best regards, > Daniel Lang > > P.S.: I don't use vinum anymore, nor can I take my boxes > out of production. The debugging kernels and crash-dumps > are no longer present, sorry. > -- > IRCnet: Mr-Spock - Der Schatten von Hasenfuss ist ziemlich dunkel - > *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 13: 8:36 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 13:08:33 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 1CA0437B400 for ; Wed, 3 Jan 2001 13:08:33 -0800 (PST) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: postfix [port 1566]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <113148-220>; Wed, 3 Jan 2001 22:08:26 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id F36C813631; Wed, 3 Jan 2001 22:08:22 +0100 (CET) From: Daniel Lang To: Marko Cuk Cc: freebsd-stable@freebsd.org Subject: Re: kern/21148: multiple crashes while using vinum Message-ID: <20010103220822.A13630@atrbg11.informatik.tu-muenchen.de> References: <200101012239.f01MdiH40906@freefall.freebsd.org> <20010103145232.B10169@atrbg11.informatik.tu-muenchen.de> <3A5390E8.953CAD50@nu.cuk.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A5390E8.953CAD50@nu.cuk.nu>; from cuk@nu.cuk.nu on Wed, Jan 03, 2001 at 09:54:53PM +0000 X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Sender: langd@informatik.tu-muenchen.de Date: Wed, 3 Jan 2001 22:08:23 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Marko, Marko Cuk wrote on Wed, Jan 03, 2001 at 09:54:53PM +0000: [..] > Please try it on 4.2 STABLE and report. I won't but I will follow the thread around vinum still for a while. Please check the headers in a group-reply. I put freebsd-gnats-submit on it on purpose since I wanted my statement included into it, since I opened the pr. The following discussion is probably not well placed there. No offence, just a hint. Best regards, Daniel -- IRCnet: Mr-Spock - Cool people don't move, they just hang around. - Daniel Lang * dl@leo.org * ++49 89 289 25735 * http://www.leo.org/~dl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 13:12:34 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 13:12:33 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.andy.de (fw.andy.de [212.8.198.74]) by hub.freebsd.org (Postfix) with ESMTP id C97FC37B400 for ; Wed, 3 Jan 2001 13:12:32 -0800 (PST) Received: from windoze.andy.de (windoze.andy.de [212.8.199.4]) by mail.andy.de (Postfix) with ESMTP id 25FF87CEC1; Wed, 3 Jan 2001 22:12:26 +0100 (CET) Date: Wed, 03 Jan 2001 22:13:13 +0100 From: Andreas Gerstenberg To: john.mcgarraghy@ucd.ie Cc: STABLE Subject: Re: problems w/ make world... Message-ID: <3602417219.978559993@windoze.andy.de> In-Reply-To: X-Mailer: Mulberry/2.0.5 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- Sean McGarraghy wrote: > Same here: I'm also on 4.2-RELEASE. I recompiled the kernel with no probs at > all, but make world fell over with signal 11 errors. I've never had any h/w > problems either. Try to install 4.1.1-RELEASE. If it is a new installation on your system, the time you have spend yet won't hurt..(as well as the data on your disc :-) This was the only working solution for me. regards, Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 13:14:18 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 13:14:15 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 74B1537B400 for ; Wed, 3 Jan 2001 13:14:15 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id QAA10799; Wed, 3 Jan 2001 16:13:51 -0500 (EST) Date: Wed, 3 Jan 2001 16:13:51 -0500 (EST) From: Daniel Eischen To: Jim King Cc: stable@FreeBSD.ORG Subject: Re: Threaded C++ Question In-Reply-To: <012701c075c4$13718360$524c8486@jking> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Jan 2001, Jim King wrote: > "Daniel Eischen" wrote: > > > Mozilla M18 binary from mozilla.org runs fine. Cool! > > > > That's because they changed the mozilla port to work around the > > problem with libgcc (I believe with an explicit link -lgcc_r). > > This should be reverted once the correct fix is committed to > > libgcc and friends. > > But I didn't build Mozilla from the port, I downloaded the binary from > mozilla.org. Something in -stable must have changed since the last time I > tried to run the binary from mozilla.org. Well, here's the log from the port: revision 1.52 date: 2000/12/21 19:40:39; author: reg; state: Exp; lines: +2 -2 Explictly link against libgcc_r, to work around bugs in 4.2-RELEASE onwards and -CURRENT. I'm still not sure why the bug was exposed only recently, but it is due to libstdc++ being linked without the -nostdlib option (causing it to be statically linked against libgcc even for the threaded case). They could have used the same fix at mozilla.org.... -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 13:24:39 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 13:24:37 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id D9B6437B400 for ; Wed, 3 Jan 2001 13:24:36 -0800 (PST) Received: from jking (jking.lgc.com [134.132.76.82]) by cgi.sstar.com (8.11.1/8.11.1) with SMTP id f03LOTE23135 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Wed, 3 Jan 2001 15:24:35 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <015801c075cb$91f86580$524c8486@jking> From: "Jim King" To: "Daniel Eischen" Cc: References: Subject: Re: Threaded C++ Question Date: Wed, 3 Jan 2001 15:24:29 -0600 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel Eischen" wrote: > On Wed, 3 Jan 2001, Jim King wrote: > > "Daniel Eischen" wrote: > > > > Mozilla M18 binary from mozilla.org runs fine. Cool! > > > > > > That's because they changed the mozilla port to work around the > > > problem with libgcc (I believe with an explicit link -lgcc_r). > > > This should be reverted once the correct fix is committed to > > > libgcc and friends. > > > > But I didn't build Mozilla from the port, I downloaded the binary from > > mozilla.org. Something in -stable must have changed since the last time I > > tried to run the binary from mozilla.org. > > Well, here's the log from the port: > > revision 1.52 > date: 2000/12/21 19:40:39; author: reg; state: Exp; lines: +2 -2 > Explictly link against libgcc_r, to work around bugs in 4.2-RELEASE > onwards and -CURRENT. I'm still not sure why the bug was exposed only > recently, but it is due to libstdc++ being linked without the -nostdlib > option (causing it to be statically linked against libgcc even for the > threaded case). > > They could have used the same fix at mozilla.org.... The binary was built back in October. This is the same binary that failed on 4.2-RELEASE and -stable's as of a couple weeks ago. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 13:25:53 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 13:25:51 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 5BFA037B400 for ; Wed, 3 Jan 2001 13:25:50 -0800 (PST) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id XAA06706; Wed, 3 Jan 2001 23:32:15 +0100 Message-ID: <3A539914.48E34811@i-clue.de> Date: Wed, 03 Jan 2001 22:26:44 +0100 From: Christoph Sold Reply-To: christoph.sold@server.i-clue.de Organization: i-clue interactive X-Mailer: Mozilla 4.75 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: =?iso-8859-1?Q?Thorbj=F6rn?= Axelsson Cc: stable@FreeBSD.ORG Subject: Re: can't reset keyboard? References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thorbj=F6rn Axelsson schrieb: > = > I updatede my box from 4.2R to 4.2S yesterday and it won't reboot prope= rly > now (I use the 'reboot' command). > = > It shutdowns real nice without any problem but just when it's supposed = to > reboot it says something like "Can't reset keyboard, trying to reset CP= U" > and it just hangs so I have to press the reset button manually. This mi= ght > not sound to complicated but the fact is that it's a remote server and > it's a pain in the ass running over there (unlocking a bunch of doors o= n > the way) just to press the reset button. > = > At first I thought that it was something with my stripped down customiz= ed > kernel but I compiled GENERIC earlier today and it seems to have the sa= me > problem. > = > The computer is an old p100 and no keyboard is generally used with it > (only plugged in when emergencies) but it seems to have the problem whe= n > it's plugged in too. > = > Otherwise the box seems to function just great. Just speculating: PC hardware uses the keyboard controller to generate the reset pulse. On some older hardware, this fails. The CPU is not powerful enough to generate a clean reset pulse, too. You may either remove boards (thus reducing the load of the reset line), or replace the board. To put it short: It is a hardware problem I have seen in older PCs now and then. HTH -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 13:57:30 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 13:57:26 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from math.uic.edu (seifert.math.uic.edu [131.193.178.249]) by hub.freebsd.org (Postfix) with SMTP id 4BC5E37B400 for ; Wed, 3 Jan 2001 13:57:26 -0800 (PST) Received: (qmail 71273 invoked by uid 30007); 3 Jan 2001 21:55:33 -0000 Date: Wed, 3 Jan 2001 15:55:33 -0600 From: Marc Culler To: freebsd-stable@freebsd.org Subject: Bug in NFSv3 client Message-ID: <20010103155533.B71238@math.uic.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear FreeBSD folks: There is a bug in the NFS version 3 client which results in a bad time stamp when a file is created with the O_EXCL flag. A test program which produces the bug is at the end of the file. (It is actually the same program which was used to illustrate a different bug in the NFSv3 server in December 1999.) We are running a FreeBSD NFS server with Solaris, FreeBSD and Linux clients. The bad time stamps seem to be created by the FreeBSD clients, although only the Solaris clients complain about it. The others apparently ignore it. The test program creates two files, one with the O_EXCL flag set and one without. Then it prints out the access time, modification time, and status change time of the two files. PLEASE NOTE THE ACCESS TIMES! Here are the results: Test 1 -- Client: FBSD 4.0-stable Server: FBSD 4.1-stable Mount: NFSv3 [culler@neumann nfstest]$ ./fbsdtest Access time of testfile1: Fri Aug 26 02:47:15 1966 Mod time of testfile1: Wed Jan 3 13:19:25 2001 Change time of testfile1: Wed Jan 3 13:19:25 2001 Access time of testfile2: Wed Jan 3 13:19:25 2001 Mod time of testfile2: Wed Jan 3 13:19:25 2001 Change time of testfile2: Wed Jan 3 13:19:25 2001 Test 2 -- Client: FBSD 4.1-stable Server: FBSD 4.1-stable Mount: NFSv3 [culler@hopper nfstest]$ ./fbsdtest Access time of testfile1: Fri Oct 15 21:37:55 2027 Mod time of testfile1: Wed Jan 3 14:41:37 2001 Change time of testfile1: Wed Jan 3 14:41:37 2001 Access time of testfile2: Wed Jan 3 14:41:37 2001 Mod time of testfile2: Wed Jan 3 14:41:37 2001 Change time of testfile2: Wed Jan 3 14:41:37 2001 Test 3 -- Client: FBSD 4.0-stable Server: FBSD 4.1-stable Mount: NFSv2 [culler@seifert culler]$ ~/nfstest/fbsdtest Access time of testfile1: Wed Jan 3 13:24:12 2001 Mod time of testfile1: Wed Jan 3 13:24:12 2001 Change time of testfile1: Wed Jan 3 13:24:12 2001 Access time of testfile2: Wed Jan 3 13:24:12 2001 Mod time of testfile2: Wed Jan 3 13:24:12 2001 Change time of testfile2: Wed Jan 3 13:24:12 2001 Test 4 -- Client: Solaris 5.8 Server: FBSD 4.1-stable Mount: NFSv3 [culler@neumann nfstest]$ ./suntest Access time of testfile1: Wed Jan 03 13:18:30 2001 Mod time of testfile1: Wed Jan 03 13:18:30 2001 Change time of testfile1: Wed Jan 03 13:18:30 2001 Access time of testfile2: Wed Jan 03 13:18:30 2001 Mod time of testfile2: Wed Jan 03 13:18:30 2001 Change time of testfile2: Wed Jan 03 13:18:30 2001 The somewhat random time values suggest that an unitialized time value is being sent by the NFSv3 client. Marc Culler Department of Mathematics University of Illinois at Chicago ---------------------- Test Program ------------------------------ #include #include #include #include main() { int rv; struct stat s; char buf[128]; rv=open("testfile1",O_CREAT|O_RDWR|O_EXCL,0666); if ( rv < 0 ) perror("testfile1"); rv=open("testfile2",O_CREAT|O_RDWR,0666); if ( rv < 0 ) perror("testfile2"); stat("testfile1", &s); strftime(buf, 128, "%c", localtime(&(s.st_atime))); printf("Access time of testfile1: %s\n", buf); strftime(buf, 128, "%c", localtime(&(s.st_mtime))); printf("Mod time of testfile1: %s\n", buf); strftime(buf, 128, "%c", localtime(&(s.st_ctime))); printf("Change time of testfile1: %s\n", buf); stat("testfile2", &s); strftime(buf, 128, "%c", localtime(&(s.st_atime))); printf("Access time of testfile2: %s\n", buf); strftime(buf, 128, "%c", localtime(&(s.st_mtime))); printf("Mod time of testfile2: %s\n", buf); strftime(buf, 128, "%c", localtime(&(s.st_ctime))); printf("Change time of testfile2: %s\n", buf); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 14:41:26 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 14:41:24 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 88FFC37B400 for ; Wed, 3 Jan 2001 14:41:24 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f03MeeQ51401; Wed, 3 Jan 2001 14:40:40 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Jan 2001 14:40:40 -0800 (PST) From: Matt Dillon Message-Id: <200101032240.f03MeeQ51401@earth.backplane.com> To: Marc Culler Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Bug in NFSv3 client References: <20010103155533.B71238@math.uic.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Dear FreeBSD folks: : :There is a bug in the NFS version 3 client which results in a bad time :stamp when a file is created with the O_EXCL flag. : :A test program which produces the bug is at the end of the file. (It :is actually the same program which was used to illustrate a different :bug in the NFSv3 server in December 1999.) : :We are running a FreeBSD NFS server with Solaris, FreeBSD and Linux :clients. The bad time stamps seem to be created by the FreeBSD :clients, although only the Solaris clients complain about it. The :others apparently ignore it. : :The test program creates two files, one with the O_EXCL flag set and :one without. Then it prints out the access time, modification time, :and status change time of the two files. PLEASE NOTE THE ACCESS TIMES! :... Hmm. On the face of it, looking at the code, it appears that the NFSV3CREATE_EXCLUSIVE generation code is generating two create_verf RPC elements instead of one, causing the timestamp that occurs later to be at the wrong offset. See line 1399 if /usr/src/sys/nfs/nfs_vnops.c #ifdef INET if (!TAILQ_EMPTY(&in_ifaddrhead)) *tl++ = IA_SIN(in_ifaddrhead.tqh_first)->sin_add r.s_addr; else #endif *tl++ = create_verf; <<<<<<<<<<<<<< this guy *tl = ++create_verf; I have not tested this idea at all, but please try removing the indicated line above, recompile the FreeBSD client's kernel, and tell me if that solves your problem. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 14:44: 9 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 14:44:07 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 038FB37B400 for ; Wed, 3 Jan 2001 14:44:07 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f03Mhar51440; Wed, 3 Jan 2001 14:43:36 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Jan 2001 14:43:36 -0800 (PST) From: Matt Dillon Message-Id: <200101032243.f03Mhar51440@earth.backplane.com> To: Marc Culler Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Bug in NFSv3 client References: <20010103155533.B71238@math.uic.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oops, scrap that last email. Here is the broken code: #ifdef INET if (!TAILQ_EMPTY(&in_ifaddrhead)) *tl++ = IA_SIN(in_ifaddrhead.tqh_first)->sin_add r.s_addr; else #endif *tl++ = create_verf; *tl = ++create_verf; Try changing it to this: #ifdef INET if (!TAILQ_EMPTY(&in_ifaddrhead)) *tl++ = IA_SIN(in_ifaddrhead.tqh_first)->sin_add r.s_addr; else #endif *tl++ = ++create_verf; I'm just guessing here, still, but I think this will fix it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 15: 2: 5 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 15:02:04 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id F044237B400 for ; Wed, 3 Jan 2001 15:02:03 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id ndnsaaaa for ; Thu, 4 Jan 2001 10:10:08 +1100 Message-ID: <3A53AF94.2E960533@quake.com.au> Date: Thu, 04 Jan 2001 10:02:44 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrey Lakhno Cc: stable@freebsd.org Subject: Re: 3.1 -> 4-S via NFS References: <20010103140851.A17817@dnepr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrey Lakhno wrote: > > Hi ! > > I have two boxes running FreeBSD 3.1-RELEASE and 4.X-STABLE. > I want to build world on 4.X system and then install it over NFS to 3.1 system. > > Is there any pitfalls in this process ? Caveats ? Its fairly simple... The only thing you need to remember is to mount /usr/src and /usr/obj via nfs, most people having problems with this is because they didnt mount /usr/obj... You may also find you need to mount them Read/Write, since there was a bug that wouldnt allow you install if it was just Read... Good Luck! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 15: 8: 6 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 15:08:04 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 9ED5837B402 for ; Wed, 3 Jan 2001 15:08:04 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f03N84f51776; Wed, 3 Jan 2001 15:08:04 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Jan 2001 15:08:04 -0800 (PST) From: Matt Dillon Message-Id: <200101032308.f03N84f51776@earth.backplane.com> To: Marc Culler , freebsd-stable@FreeBSD.ORG Subject: Re: Bug in NFSv3 client References: <20010103155533.B71238@math.uic.edu> <200101032243.f03Mhar51440@earth.backplane.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bleh. I'm wrong twice. Don't bother with either patch. The version is supposed to be 8 bytes. Scrap both patches. I'll have to look into this some more. There is definitely some weirdness in the NFS code. It could be the VATTR_NULL() call on the server side that is broken. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 15:19:47 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 15:19:42 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id 163C437B69E for ; Wed, 3 Jan 2001 15:19:41 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id BAA01335; Thu, 4 Jan 2001 01:16:49 +0200 To: stable@FreeBSD.ORG, "David O'Brien" Subject: Re: C++ threaded programs Message-ID: <978563809.3a53b2e186ca1@webmail.harmonic.co.il> Date: Thu, 04 Jan 2001 01:16:49 +0200 (IST) From: Roman Shterenzon References: <20010103103755.A62189@dragon.nuxi.com> In-Reply-To: <20010103103755.A62189@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting David O'Brien : > On Thu, Jan 04, 2001 at 12:29:17AM +0600, Max Khon wrote: > > Can you tell me what do you plan on "C++ threaded programs > > segfault" issue? > > Still fixing issues. > Compiling -static is broken with my latest patch. > Dan and I have a 2nd patch we are reviewing and testing. > > > At this time I give people the same patch that I sent you about two > weeks > > ago (you can get it at http://iclub.nsu.ru/~fjoe) -- only one libgcc.a > > (with threads support, -fpic) is built with it and it is linked into > > shared objects. > > I had to tweat that some (based on what I had at the time). I guess I > should just post my patch. > > I have been unable to get anyone I've directly asked to actually test it > (that emailed me saying they have a problem with the current state of > the world). Yes, you asked me to test it, and I'll be glad to assist you. The problem is that I don't have time for the following couple of days, but I'll try it as soon as possible. On the other side, I tested Daniel's patch - i.e. -nostdlib in libstdc++ and it works fine for everything I've tested it with - the only downside that native 4.2 binaries that were compiled from C++ sources fail to work, but, older, e.g. 4.1-STABLE work fine. > -- > -- David (obrien@FreeBSD.org) --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 15:19:48 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 15:19:43 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id E963B37B400 for ; Wed, 3 Jan 2001 15:19:41 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id F261A6A90D; Thu, 4 Jan 2001 09:49:38 +1030 (CST) Date: Thu, 4 Jan 2001 09:49:38 +1030 From: Greg Lehey To: Vallo Kallaste Cc: Josef Karthauser , Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? Message-ID: <20010104094938.B4336@wantadilla.lemis.com> References: <20010102230107.A559@basildon.homerun> <20010103102943.A770@tao.org.uk> <20010103214829.X4336@wantadilla.lemis.com> <20010103172844.D13221@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010103172844.D13221@myhakas.matti.ee>; from vallo@matti.ee on Wed, Jan 03, 2001 at 05:28:44PM +0200 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 3 January 2001 at 17:28:44 +0200, Vallo Kallaste wrote: > On Wed, Jan 03, 2001 at 09:48:29PM +1030, Greg Lehey wrote: > >>> As far as I understand from Greg he's not aware of many people who >>> are having problems with raid 5. >> >> Probably. If you know of somebody I don't know of, please let me >> know. > > For a while now I have a old spare Intel Madrona server. It has in > current configuration one SCSI backplane with 5 SCA plugs and four > Seagate Cheetah disks (old model: 4.3GB 10000rpm). The SCSI > controller is onboard Symbios 875. I did some vinum raid-5 tests in > November, all what I got was massive filesystem corruption and > panics after the degraded volume got rebuilt. I'll probably have > this box for yet two weeks or so and my time isn't so limited now, > so.. What I can do to help you besides installing latest -stable? Do > you have some formalized test procedures or anything to prove the > stability of raid-5 configuration? No testing can prove stability, only instability :-) If you were able to get file system corruption, go and check how you did it and see if you can do it again. Don't forget the information I asked for in http://www.vinumvm.org/vinum/how-to-debug.html. 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-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 15:22:34 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 15:22:30 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 13E8F37B400 for ; Wed, 3 Jan 2001 15:22:30 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f03NMTK51973; Wed, 3 Jan 2001 15:22:29 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Jan 2001 15:22:29 -0800 (PST) From: Matt Dillon Message-Id: <200101032322.f03NMTK51973@earth.backplane.com> To: Marc Culler , freebsd-stable@FreeBSD.ORG Subject: ... yet more spaz email ... Re: Bug in NFSv3 client References: <20010103155533.B71238@math.uic.edu> <200101032243.f03Mhar51440@earth.backplane.com> <200101032308.f03N84f51776@earth.backplane.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Found it. /usr/src/sys/nfs/nfs_serv.c line 1737 (in stable) if (error) NDFREE(&nd, NDF_ONLY_PNBUF); else { nfsrv_object_create(nd.ni_vp); if (exclusive_flag) { exclusive_flag = 0; VATTR_NULL(vap); bcopy(cverf, (caddr_t)&vap->va_atime, NFSX_V3CREATEVERF); error = VOP_SETATTR(nd.ni_vp, vap, cred, procp); } } Say what? It's copying the version block into va_atime for the file? It looks like this bug has been in here since NFSv3 was first coded up, this is where the code is added: # revision 1.16 # date: 1995/06/27 11:06:37; author: dfr; state: Exp; lines: +2161 -771 # Changes to support version 3 of the NFS protocol. # The version 2 support has been tested (client+server) against FreeBSD-2.0, # IRIX 5.3 and FreeBSD-current (using a loopback mount). The version 2 support # is stable AFAIK. # The version 3 support has been tested with a loopback mount and minimally # against an IRIX 5.3 server. It needs more testing and may have problems. # I have patched amd to support the new variable length filehandles although # it will still only use version 2 of the protocol. # # Before booting a kernel with these changes, nfs clients will need to at least # build and install /usr/sbin/mount_nfs. Servers will need to build and # install /usr/sbin/mountd. # NFS diskless support is untested. I'm not sure what the solution is... possibly to just remove the whole piece of code surrounded by the if (exclusive_flag) { .... } I will do some testing later tonight when I get home. You might try the above yourself, or you can wait. I'm really confused as to why the access time stamp was being forced to the NFS version info data in the first place. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 15:23: 8 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 15:23:03 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id CA43837B404; Wed, 3 Jan 2001 15:23:01 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id BAA01340; Thu, 4 Jan 2001 01:20:27 +0200 To: "David O'Brien" Subject: Re: Threaded C++ Question Message-ID: <978564027.3a53b3bb7341f@webmail.harmonic.co.il> Date: Thu, 04 Jan 2001 01:20:27 +0200 (IST) From: Roman Shterenzon Cc: freebsd-stable@freebsd.org References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> <20010103103948.A62250@dragon.nuxi.com> In-Reply-To: <20010103103948.A62250@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting David O'Brien : > On Tue, Jan 02, 2001 at 05:38:33PM -0600, Jim King wrote: > > I'd like to know too. I plan on tackling Mozilla this weekend; it > would be > > nice if it was a no-brainer. :-) > > I was unable to get our mozilla port to segfault with with or without > the > patch I'm planning on committing. > > It would be quite helpful if people could explain how to experience the > problem. > How to repeat the problem: Make a vanilla install of 4.2-RELEASE. Get a mozilla port without the explicit -lgcc_r (I don't remember the date, but it can be checked in cvsweb). make install. The resulting binary will segfault when started. You don't need to change anything else. I verified it by myself. However, like I've said before - the binary from 4.1 will work fine (I'm still using one on my home computer). --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 15:29:48 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 15:29:44 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 37F5E37B400 for ; Wed, 3 Jan 2001 15:29:44 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id PAA27362; Wed, 3 Jan 2001 15:28:55 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda27360; Wed Jan 3 15:28:45 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.1/8.9.1) id f03NSew01419; Wed, 3 Jan 2001 15:28:40 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdIq1417; Wed Jan 3 15:27:47 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f03NRk503583; Wed, 3 Jan 2001 15:27:46 -0800 (PST) Message-Id: <200101032327.f03NRk503583@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdHb3576; Wed Jan 3 15:27:04 2001 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.2-RELEASE X-Sender: cy To: christoph.sold@server.i-clue.de Cc: =?iso-8859-1?Q?Thorbj=F6rn?= Axelsson , stable@FreeBSD.ORG Subject: Re: can't reset keyboard? In-reply-to: Your message of "Wed, 03 Jan 2001 22:26:44 +0100." <3A539914.48E34811@i-clue.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 03 Jan 2001 15:27:04 -0800 Sender: cy@uumail.gov.bc.ca Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A539914.48E34811@i-clue.de>, Christoph Sold writes: > = > = > Thorbj=F6rn Axelsson schrieb: > > = > > I updatede my box from 4.2R to 4.2S yesterday and it won't reboot pro= perly > > now (I use the 'reboot' command). > > = > > It shutdowns real nice without any problem but just when it's suppose= d to > > reboot it says something like "Can't reset keyboard, trying to reset = CPU" > > and it just hangs so I have to press the reset button manually. This = might > > not sound to complicated but the fact is that it's a remote server an= d > > it's a pain in the ass running over there (unlocking a bunch of doors= on > > the way) just to press the reset button. > > = > > At first I thought that it was something with my stripped down custom= ized > > kernel but I compiled GENERIC earlier today and it seems to have the = same > > problem. > > = > > The computer is an old p100 and no keyboard is generally used with it= > > (only plugged in when emergencies) but it seems to have the problem w= hen > > it's plugged in too. > > = > > Otherwise the box seems to function just great. > = > Just speculating: PC hardware uses the keyboard controller to generate > the reset pulse. On some older hardware, this fails. The CPU is not > powerful enough to generate a clean reset pulse, too. You may either > remove boards (thus reducing the load of the reset line), or replace th= e > board. > = > To put it short: It is a hardware problem I have seen in older PCs now > and then. I had a similar problem in a 486 a few years ago. Replacing the M = level keyboard BIOS (keyboard controller) with a F (newer) keyboard = BIOS fixed the problem. Newer operating systems will not work with the = older M keyboard controller. -- = Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC = "COBOL IS A WASTE OF CARDS." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 16: 4:38 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 16:04:31 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 311D437B400 for ; Wed, 3 Jan 2001 16:04:29 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 481ED6A911; Thu, 4 Jan 2001 10:34:26 +1030 (CST) Date: Thu, 4 Jan 2001 10:34:26 +1030 From: Greg Lehey To: Roman Shterenzon Cc: Daniel Lang , freebsd-stable@freebsd.org Subject: Re: Vinum saga continues Message-ID: <20010104103426.C4336@wantadilla.lemis.com> References: <20010103141514.A381@jamus.xpert.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20010103141514.A381@jamus.xpert.com>; from roman@jamus.xpert.com on Wed, Jan 03, 2001 at 02:15:14PM +0200 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] On Wednesday, 3 January 2001 at 14:15:14 +0200, Roman Shterenzon wrote: > Hi, > > Attached is the most valuable information that was in my pr 22103. > I've read the vinumdebug and the other guy's PR. > I'm still not getting what is missing. > You told the other guy to submit the backtrace, but it was in fact submitted! > It's as well in my PR as well. > Your responses are very brief - "please read vinumdebug", but in fact, if > there's something that is missing, you can be more specific. OK. I don't know what's so difficult about this, but here we go:. On the web page to which I refer, I say: If you need to contact me because of problems with Vinum, please send me a mail message with the following information: - What problems are you having? You don't say this, but I suppose it's obvious. - Which version of FreeBSD are you running? I can't find this in your report. - Have you made any changes to the system sources, including Vinum? I can't find this in your report. - Supply the output of the vinum list command. If you can't start Vinum, supply the on-disk configuration, as described below. If you can't start Vinum, then (and only then) send a copy of the configuration file. I can't find this in your report. - Supply an extract of the Vinum history file. Unless you have explicitly renamed it, it will be /var/log/vinum_history. This file can get very big; please limit it to the time around when you have the problems. Each line contains a timestamp at the beginning, so you will have no difficulty in establishing which data is of relevance. I can't find this in your report. - Supply an extract of the file /var/log/messages. Restrict the extract to the same time frame as the history file. Again, each line contains a timestamp at the beginning, so you will have no difficulty in establishing which data is of relevance. I can't find this in your report. - If you have a crash, please supply a backtrace from the dump analysis as discussed below under Kernel Panics. Please don't delete the crash dump; it may be needed for further analysis. Basically, all I can see here is the backtrace, which is still wrapped at 80 characters, despite all my requests. I've had to manually reformat it to make it legible. Have you really read the web page? > Alfred Perlstein looked it my PR once and he thinks that it's due to > stack smashing. > However, he wasn't able to find where it happends. > It may be in fact interaction with some other driver, like you said, for > example - fxp. This is why I submitted the dmesg output. Please, only if I ask for it. > #62 0xc023660b in trap (frame={tf_fs = 0xc0270010, tf_es = 0xc0150010, tf_ds = 0x680010, tf_edi = 0xc16e9588, > tf_esi = 0xc16e9400, tf_ebp = 0xc02773b0, tf_isp = 0xc0277380, tf_ebx = 0xc208e340, tf_edx = 0x0, > tf_ecx = 0x5610001, tf_eax = 0xff9773bf, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0xc150fc67, tf_cs = 0x8, > tf_eflags = 0x10246, tf_esp = 0xc16e9588, tf_ss = 0xc14bd000}) at ../../i386/i386/trap.c:426 > #63 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../dev/vinum/vinuminterrupt.c:199 > #64 0xc0178d6b in biodone (bp=0xc16e9588) at ../../kern/vfs_bio.c:2637 > #65 0xc0126bb9 in dadone (periph=0xc14ca700, done_ccb=0xc1808400) at ../../cam/scsi/scsi_da.c:1246 > #66 0xc0122aff in camisr (queue=0xc0298690) at ../../cam/cam_xpt.c:6319 > #67 0xc0122911 in swi_cambio () at ../../cam/cam_xpt.c:6222 > #68 0xc022d0e0 in splz_swi () > (kgdb) up 63 > #64 0xc0178d6b in biodone (bp=0xc16e9588) at ../../kern/vfs_bio.c:2637 > 2637 (*bp->b_iodone) (bp); > (kgdb) print bp > $1 = (struct buf *) 0xc16e9588 > (kgdb) print *bp->b_iodone > $2 = {void ()} 0xc150f6ac > (kgdb) down > #63 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../dev/vinum/vinuminterrupt.c:199 > 199 } > (kgdb) list > 194 VOL[rq->volplex.volno].active--; /* another request finished */ > 195 biodone(ubp); /* top level buffer completed */ > 196 freerq(rq); /* return the request storage */ > 197 } > 198 } > 199 } > (kgdb) down > #62 0xc023660b in trap (frame={tf_fs = 0xc0270010, tf_es = 0xc0150010, tf_ds = 0x680010, tf_edi = 0xc16e9588, > tf_esi = 0xc16e9400, tf_ebp = 0xc02773b0, tf_isp = 0xc0277380, tf_ebx = 0xc208e340, tf_edx = 0x0, > tf_ecx = 0x5610001, tf_eax = 0xff9773bf, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0xc150fc67, tf_cs = 0x8, > tf_eflags = 0x10246, tf_esp = 0xc16e9588, tf_ss = 0xc14bd000}) at ../../i386/i386/trap.c:426 > 426 (void) trap_pfault(&frame, FALSE, eva); > (kgdb) up 2 > #64 0xc0178d6b in biodone (bp=0xc16e9588) at ../../kern/vfs_bio.c:2637 > 2637 (*bp->b_iodone) (bp); > (kgdb) up > #65 0xc0126bb9 in dadone (periph=0xc14ca700, done_ccb=0xc1808400) at ../../cam/scsi/scsi_da.c:1246 > 1246 biodone(bp); > (kgdb) print bp > $3 = (struct buf *) 0xc16e9588 > (kgdb) print *bp > b_flags = 0x204, > b_qindex = 0x0, > b_xflags = 0x0, > b_lock = { > lk_interlock = { > lock_data = 0x0 > }, > lk_flags = 0x400, > lk_sharecount = 0x0, > lk_waitcount = 0x0, > lk_exclusivecount = 0x1, > lk_prio = 0x14, > lk_wmesg = 0xc0257a24 "bufwait", > lk_timo = 0x0, > lk_lockholder = 0x5 > }, > b_error = 0x0, > b_bufsize = 0x2000, > b_bcount = 0x2000, > b_resid = 0x0, > b_dev = 0xc15cd880, > b_data = 0xcbdcc000 "jA\002", > b_kvabase = 0x0, > b_kvasize = 0x0, > b_lblkno = 0x0, > b_blkno = 0x2b08149, > b_offset = 0x0, > b_iodone = 0xc150f6ac , OK, this is *not* the buffer header corruption bug, but it's happening in a very similar position. With the buffer header corruption, you wouldn't have got as far as this, because b_iodone would be zeroed out. I also can't see any other obvious damage to the buffer header. What we need to do now is to find out where the trap occurred. That's at line 199 of complete_rqe, which shows as the very end of the function. Could you give me the following information from gdb, please? (gdb) x/20i 0xc150fc60 Thanks Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html 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-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 16:24:37 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 16:24:33 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 6B64C37B400; Wed, 3 Jan 2001 16:24:31 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 086CE6A90D; Thu, 4 Jan 2001 10:54:29 +1030 (CST) Date: Thu, 4 Jan 2001 10:54:28 +1030 From: Greg Lehey To: Daniel Lang Cc: Andy Newman , Roman Shterenzon , freebsd-gnats-submit@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kern/21148: multiple crashes while using vinum Message-ID: <20010104105428.D4336@wantadilla.lemis.com> References: <200101012239.f01MdiH40906@freefall.freebsd.org> <20010103145232.B10169@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010103145232.B10169@atrbg11.informatik.tu-muenchen.de>; from dl@leo.org on Wed, Jan 03, 2001 at 02:52:35PM +0000 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 3 January 2001 at 14:52:35 +0000, Daniel Lang wrote: > Dear Greg, Andy, Roman, > > grog@FreeBSD.org wrote on Mon, Jan 01, 2001 at 11:41:19PM +0000: >> Synopsis: multiple crashes while using vinum > [..] >> State-Changed-Why: >> No feedback from submitter. >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=21148 > > Well, I've sent you stack-traces, with (and alas as well without) > debugging symbols, I am perfectly aware of your instruction page > about debugging vinum, and not an ignorant moron, who complains > without reading. Unfortunately you don't seem to trust me > or other people in this matter. As my closing message says, the reason I closed the PR was: >> No feedback from submitter. I sent you a message on 10 September 2000 asking for additional information. I received none. There's no reason to get all upset now, or make claims about my intentions. This was just a dead PR, and you've made it clear, both before and now, that you have no intention of following up on it. This is not a question of "ignorant morons" or "trust". > The reason is, that _some code_ writes into unallocated memory, in > my case overwriting a data-structure of an ata-request with a few > zero bytes, causing the panic. The stack trace allows me to trace > the problem back to this point, but not further. I later experienced > a similar problem on a scsi-only system. Yes, this looks very much like the other issues. But you must understand that there's nothing I can do without further information. > The reason, why I filed this pr unter 'vinum' is, that it only > occured on boxes using vinum, and perfectly reproducable via simple > operations like a 'find /vinum/file/system -print' on a larger and > moderately filled vinum-filesystem. Perfectly reproducable means: > each night, periodic daily caused the panic (traceable to the find > call in /etc/security, finding files with setuid bits). > > As far as I know, the only way to trace this writing into > unallocated/otherallocated memory resp. buffer overrun > would be to set a watchpoint to the overwritten data-structure > within the kernel-debugger. The trouble with that is that this only happens when the system is very active, and there are thousands of potential buffer headers which could be trashed. I do have a trace facility within Vinum, but even with that it's difficult to figure out what's going on. > My stack-traces showed that this memory region stays the same on the > same machine with the same kernel (although I can't tell how > reliable this is). If you mean that the same part of the buffer header gets smashed every time, yes, this is reliably reproducible (well, in other words, when it happens (at random), it happens in the same place every time). It may mean that Vinum is doing it, but as far as I can tell it's always 6 words being zeroed out, and I don't do that anywhere in Vinum. The other possibility, which I consider most likely, is that the data structures accidentally get freed and used by some other driver (or, possibly, that some other driver freed them first and then continued using them). This would explain the observed correlation with the fxp driver. > My experiences with kernel code and kernel-debugging with > ddb are very limited. So is my time (I know this applies > to anyone). Therefore I ceased spending time to set up > remote-gdb sessions and sending you stack traces trying to be > helpful, since you obviously didn't seem to be interested. > > I further decided not to use vinum any more. We spent some > cash on a few hardware RAIDs, and the boxes run smooth now, > since. > > I am just writing this to state: > a) I did respond to your requests, trying to be as helpful as > I could. Well, I sent you a message on 10 September 2000, asking for additional information. You didn't send it to me. > You could blame me for not knowing or willing to learn how to > set up a ddb/gdb session using watchpoints and waiting for the > next crash in an environmen that should be productive (and now > is). No, I wouldn't do that. > b) I still believe, that there is a problem somewhere in the > vinum code (probably within raid5 routines, since a mirror > setup worked fine). Correct. I have no doubt about it. But some bugs are difficult to find, and I need help. 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-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 16:39:50 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 16:39:47 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7EB0A37B400; Wed, 3 Jan 2001 16:39:45 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id A9BA26A911; Thu, 4 Jan 2001 11:09:40 +1030 (CST) Date: Thu, 4 Jan 2001 11:09:40 +1030 From: Greg Lehey To: Marko Cuk Cc: Daniel Lang , Andy Newman , Roman Shterenzon , freebsd-gnats-submit@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kern/21148: multiple crashes while using vinum Message-ID: <20010104110940.E4336@wantadilla.lemis.com> References: <200101012239.f01MdiH40906@freefall.freebsd.org> <20010103145232.B10169@atrbg11.informatik.tu-muenchen.de> <3A5390E8.953CAD50@nu.cuk.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A5390E8.953CAD50@nu.cuk.nu>; from cuk@nu.cuk.nu on Wed, Jan 03, 2001 at 09:51:52PM +0100 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 3 January 2001 at 21:51:52 +0100, Marko Cuk wrote: > I had the same problems on IDE and SCSI configuration on 4.0, 4.1, 4.1.1 . > I spent cash on buying 2 x 40Gig IDE Wd's and put them into mirror. > That was a few months ago. > > I had crashes also with bridging, but Bosko Milekic and Thomas fixed the > code with a little help and bridge works superb in 4.2 STABLE. > > So I was still interested in RAID5 and also very curious about Vinum in 4.2 > so I decided to test that thing with same disks ( old SCSI disks , bud good > ) and belive or not, it works also under heavy load. > It is strange, but I didn't change anything. Controller was the same > Adaptec, cables were the same, disks also. Bsd was 4.2 STABLE. > > Please try it on 4.2 STABLE and report. > > I must admit, that I am not a FreeBSD hacker, I don't know many > about debugging and I was very unhelpful to Grog, but he is very > sure, that Vinum works and I don't like his way of thinking about > that. I'm not sure what you're saying here. I've made it clear (even in the man pages) that there are some problems with RAID-5. What else (apart from fix the problem :-) do you want me to do? > I also set him account on that maschine, to check and debug problems > on that maschine and repair them, but he wasn't interested in > solving such problems. He blamed me for config or some other > mistake. I don't have any record of this. Did you use some other name? The last exchange we had (27 November 2000), you didn't want to submit the information I asked for, I said I wouldn't be able to help you much without it, and you said you would go back and get the information. I don't see anything about being offered an account on the machine, which indeed would have been of assistance. But basically, all I needed at that point was a (preferably unmutilated) copy of the information I asked for. Based on what you supplied, I don't even know if you had a panic or just a freeze. > Vinum and RAID5 under 4.1 is not stable. That's all. Ah, but there's the problem. There are no changes between 4.1 and 4.2. In some cases, we run into these problems, but for the most part it just works. 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-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 16:46:46 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 16:46:39 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from jamus.xpert.com (jamus.xpert.com [199.203.132.17]) by hub.freebsd.org (Postfix) with ESMTP id 712FD37B400 for ; Wed, 3 Jan 2001 16:46:37 -0800 (PST) Received: from roman (helo=localhost) by jamus.xpert.com with local-esmtp (Exim 3.12 #5) id 14DyLG-0005ZH-00; Thu, 04 Jan 2001 02:33:18 +0200 Date: Thu, 4 Jan 2001 02:33:18 +0200 (IST) From: Roman Shterenzon To: Greg Lehey Cc: Daniel Lang , Subject: Re: Vinum saga continues In-Reply-To: <20010104103426.C4336@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=koi8-r Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 Jan 2001, Greg Lehey wrote: > [Format recovered--see http://www.lemis.com/email/email-format.html] > > On Wednesday, 3 January 2001 at 14:15:14 +0200, Roman Shterenzon wrote: > > Hi, > > > > Attached is the most valuable information that was in my pr 22103. > > I've read the vinumdebug and the other guy's PR. > > I'm still not getting what is missing. > > You told the other guy to submit the backtrace, but it was in fact subm= itted! > > It's as well in my PR as well. > > Your responses are very brief - "please read vinumdebug", but in fact, = if > > there's something that is missing, you can be more specific. > > OK. I don't know what's so difficult about this, but here we go:. On > the web page to which I refer, I say: > > If you need to contact me because of problems with Vinum, please send > me a mail message with the following information: > > - What problems are you having? > > You don't say this, but I suppose it's obvious. Hmm, I still think that you didn't read my PR. It was in the synopsis. > - Which version of FreeBSD are you running? > > I can't find this in your report. So I was right. You didn't read it. What I resent is only small part of the PR. The version was there. 4.1-RELEASE. > - Have you made any changes to the system sources, including Vinum? > > I can't find this in your report. No I didn't > - Supply the output of the vinum list command. If you can't start > Vinum, supply the on-disk configuration, as described below. If > you can't start Vinum, then (and only then) send a copy of the > configuration file. > > I can't find this in your report. > > - Supply an extract of the Vinum history file. Unless you have > explicitly renamed it, it will be /var/log/vinum_history. This > file can get very big; please limit it to the time around when you > have the problems. Each line contains a timestamp at the > beginning, so you will have no difficulty in establishing which > data is of relevance. > > I can't find this in your report. > > - Supply an extract of the file /var/log/messages. Restrict the > extract to the same time frame as the history file. Again, each > line contains a timestamp at the beginning, so you will have no > difficulty in establishing which data is of relevance. > > I can't find this in your report. All these were in one or both of my PRs. There was nothing interesting there. > > - If you have a crash, please supply a backtrace from the dump > analysis as discussed below under Kernel Panics. Please don't > delete the crash dump; it may be needed for further analysis. > > Basically, all I can see here is the backtrace, which is still wrapped > at 80 characters, despite all my requests. I've had to manually > reformat it to make it legible. Have you really read the web page? Hmm.. I don't know why it wrapped around at 80 chars. I took it out of the "Raw PR" > > Alfred Perlstein looked it my PR once and he thinks that it's due to > > stack smashing. > > However, he wasn't able to find where it happends. > > It may be in fact interaction with some other driver, like you said, fo= r > > example - fxp. This is why I submitted the dmesg output. > > Please, only if I ask for it. ok. > > > #62 0xc023660b in trap (frame=3D{tf_fs =3D 0xc0270010, tf_es =3D 0xc01= 50010, tf_ds =3D 0x680010, tf_edi =3D 0xc16e9588, > > tf_esi =3D 0xc16e9400, tf_ebp =3D 0xc02773b0, tf_isp =3D 0xc0277= 380, tf_ebx =3D 0xc208e340, tf_edx =3D 0x0, > > tf_ecx =3D 0x5610001, tf_eax =3D 0xff9773bf, tf_trapno =3D 0xc, = tf_err =3D 0x2, tf_eip =3D 0xc150fc67, tf_cs =3D 0x8, > > tf_eflags =3D 0x10246, tf_esp =3D 0xc16e9588, tf_ss =3D 0xc14bd0= 00}) at ../../i386/i386/trap.c:426 > > #63 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../= dev/vinum/vinuminterrupt.c:199 > > #64 0xc0178d6b in biodone (bp=3D0xc16e9588) at ../../kern/vfs_bio.c:26= 37 > > #65 0xc0126bb9 in dadone (periph=3D0xc14ca700, done_ccb=3D0xc1808400) = at ../../cam/scsi/scsi_da.c:1246 > > #66 0xc0122aff in camisr (queue=3D0xc0298690) at ../../cam/cam_xpt.c:6= 319 > > #67 0xc0122911 in swi_cambio () at ../../cam/cam_xpt.c:6222 > > #68 0xc022d0e0 in splz_swi () > > (kgdb) up 63 > > #64 0xc0178d6b in biodone (bp=3D0xc16e9588) at ../../kern/vfs_bio.c:26= 37 > > 2637 (*bp->b_iodone) (bp); > > (kgdb) print bp > > $1 =3D (struct buf *) 0xc16e9588 > > (kgdb) print *bp->b_iodone > > $2 =3D {void ()} 0xc150f6ac > > (kgdb) down > > #63 0xc150fc67 in complete_rqe () at /usr/src/sys/modules/vinum/../../= dev/vinum/vinuminterrupt.c:199 > > 199 } > > (kgdb) list > > 194 VOL[rq->volplex.volno].active--; /* = another request finished */ > > 195 biodone(ubp); /* = top level buffer completed */ > > 196 freerq(rq); /* = return the request storage */ > > 197 } > > 198 } > > 199 } > > (kgdb) down > > #62 0xc023660b in trap (frame=3D{tf_fs =3D 0xc0270010, tf_es =3D 0xc01= 50010, tf_ds =3D 0x680010, tf_edi =3D 0xc16e9588, > > tf_esi =3D 0xc16e9400, tf_ebp =3D 0xc02773b0, tf_isp =3D 0xc0277= 380, tf_ebx =3D=A00xc208e340, tf_edx =3D 0x0, > > tf_ecx =3D 0x5610001, tf_eax =3D 0xff9773bf, tf_trapno =3D 0xc, = tf_err =3D 0x2, tf_eip =3D 0xc150fc67, tf_cs =3D 0x8, > > tf_eflags =3D 0x10246, tf_esp =3D 0xc16e9588, tf_ss =3D 0xc14bd0= 00}) at ../../i386/i386/trap.c:426 > > 426 (void) trap_pfault(&frame, FALSE, eva); > > (kgdb) up 2 > > #64 0xc0178d6b in biodone (bp=3D0xc16e9588) at ../../kern/vfs_bio.c:26= 37 > > 2637 (*bp->b_iodone) (bp); > > (kgdb) up > > #65 0xc0126bb9 in dadone (periph=3D0xc14ca700, done_ccb=3D0xc1808400) = at ../../cam/scsi/scsi_da.c:1246 > > 1246 biodone(bp); > > (kgdb) print bp > > $3 =3D (struct buf *) 0xc16e9588 > > (kgdb) print *bp > > b_flags =3D 0x204, > > b_qindex =3D 0x0, > > b_xflags =3D 0x0, > > b_lock =3D { > > lk_interlock =3D { > > lock_data =3D 0x0 > > }, > > lk_flags =3D 0x400, > > lk_sharecount =3D 0x0, > > lk_waitcount =3D 0x0, > > lk_exclusivecount =3D 0x1, > > lk_prio =3D 0x14, > > lk_wmesg =3D 0xc0257a24 "bufwait", > > lk_timo =3D 0x0, > > lk_lockholder =3D 0x5 > > }, > > b_error =3D 0x0, > > b_bufsize =3D 0x2000, > > b_bcount =3D 0x2000, > > b_resid =3D 0x0, > > b_dev =3D 0xc15cd880, > > b_data =3D 0xcbdcc000 "jA\002", > > b_kvabase =3D 0x0, > > b_kvasize =3D 0x0, > > b_lblkno =3D 0x0, > > b_blkno =3D 0x2b08149, > > b_offset =3D 0x0, > > b_iodone =3D 0xc150f6ac , > > OK, this is *not* the buffer header corruption bug, but it's happening > in a very similar position. With the buffer header corruption, you > wouldn't have got as far as this, because b_iodone would be zeroed > out. I also can't see any other obvious damage to the buffer header. > > What we need to do now is to find out where the trap occurred. That's > at line 199 of complete_rqe, which shows as the very end of the > function. Could you give me the following information from gdb, > please? > > (gdb) x/20i 0xc150fc60 > > Thanks Heh :( I wish you read the PR when I submitted it. It was there. I only took it out of the closed PR and resent to you. This crash is not available anymore. I used the disks for RAID-1 setup. But, for curiosity, what this command supposedly does? The fact that the page fault occures at the end of the function, i.e. "return" hints that perhaps the return address from the call was smashed. I think that the crash can be reproduced - three disks in raid5 setup, more than 50% filled. find /raid -print should crash it. I can send you my setup. I'd 3 x 36Gb IBM drives on adaptec. My mutilated and huge PR kern/22103 has more info (dmesg!) that you may or may not find interesting. Daniel, do you have any other assumptions or ideas how this can be reproduced? I know that we had a different hardware. BTW, Daniel Lang had his crash *exactly* in the same place - kern/21148 if I'm not mistaken. But he doesn't have his crash file as well. You just didn't come back to us in time. Well.. Until next time. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 16:52:48 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 16:52:45 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from jamus.xpert.com (jamus.xpert.com [199.203.132.17]) by hub.freebsd.org (Postfix) with ESMTP id C65B737B400 for ; Wed, 3 Jan 2001 16:52:42 -0800 (PST) Received: from roman (helo=localhost) by jamus.xpert.com with local-esmtp (Exim 3.12 #5) id 14DyR6-0005qN-00; Thu, 04 Jan 2001 02:39:20 +0200 Date: Thu, 4 Jan 2001 02:39:20 +0200 (IST) From: Roman Shterenzon To: Greg Lehey Cc: Daniel Lang , Andy Newman , Subject: Re: kern/21148: multiple crashes while using vinum In-Reply-To: <20010104105428.D4336@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 Jan 2001, Greg Lehey wrote: ...snip... > > The reason is, that _some code_ writes into unallocated memory, in > > my case overwriting a data-structure of an ata-request with a few > > zero bytes, causing the panic. The stack trace allows me to trace > > the problem back to this point, but not further. I later experienced > > a similar problem on a scsi-only system. > > Yes, this looks very much like the other issues. But you must > understand that there's nothing I can do without further information. > > > The reason, why I filed this pr unter 'vinum' is, that it only > > occured on boxes using vinum, and perfectly reproducable via simple > > operations like a 'find /vinum/file/system -print' on a larger and > > moderately filled vinum-filesystem. Perfectly reproducable means: > > each night, periodic daily caused the panic (traceable to the find > > call in /etc/security, finding files with setuid bits). > > > > As far as I know, the only way to trace this writing into > > unallocated/otherallocated memory resp. buffer overrun > > would be to set a watchpoint to the overwritten data-structure > > within the kernel-debugger. > > The trouble with that is that this only happens when the system is > very active, and there are thousands of potential buffer headers which > could be trashed. I do have a trace facility within Vinum, but even > with that it's difficult to figure out what's going on. I don't agree about "very active". My system in question was calm during the test, I just run find /raid -print and it crashed. > > My stack-traces showed that this memory region stays the same on the > > same machine with the same kernel (although I can't tell how > > reliable this is). > > If you mean that the same part of the buffer header gets smashed every > time, yes, this is reliably reproducible (well, in other words, when > it happens (at random), it happens in the same place every time). It That is correct. Both me and Daniel had the crash occuring exactly at the same place. > may mean that Vinum is doing it, but as far as I can tell it's always > 6 words being zeroed out, and I don't do that anywhere in Vinum. The > other possibility, which I consider most likely, is that the data > structures accidentally get freed and used by some other driver (or, > possibly, that some other driver freed them first and then continued > using them). This would explain the observed correlation with the fxp > driver. Do you think that the later is more probable? I had fxp card there. > > b) I still believe, that there is a problem somewhere in the > > vinum code (probably within raid5 routines, since a mirror > > setup worked fine). > > Correct. I have no doubt about it. But some bugs are difficult to > find, and I need help. Hmm.. that part of the code in question, isn't it shared for both raid1 and raid5? --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 17: 5:30 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 17:05:27 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 2073F37B400 for ; Wed, 3 Jan 2001 17:05:25 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 927666A90D; Thu, 4 Jan 2001 11:35:21 +1030 (CST) Date: Thu, 4 Jan 2001 11:35:21 +1030 From: Greg Lehey To: Roman Shterenzon Cc: Daniel Lang , Andy Newman , freebsd-stable@freebsd.org Subject: Re: kern/21148: multiple crashes while using vinum Message-ID: <20010104113521.G4336@wantadilla.lemis.com> References: <20010104105428.D4336@wantadilla.lemis.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 roman@xpert.com on Thu, Jan 04, 2001 at 02:39:20AM +0200 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 4 January 2001 at 2:39:20 +0200, Roman Shterenzon wrote: > On Thu, 4 Jan 2001, Greg Lehey wrote: > >> The trouble with that is that this only happens when the system is >> very active, and there are thousands of potential buffer headers which >> could be trashed. I do have a trace facility within Vinum, but even >> with that it's difficult to figure out what's going on. > > I don't agree about "very active". My system in question was calm during > the test, I just run find /raid -print and it crashed.o Your problem seems to be a little different, as I mentioned in my reply to your stack trace. It might be related, and it might give us the information we need to find the problem. >>> My stack-traces showed that this memory region stays the same on the >>> same machine with the same kernel (although I can't tell how >>> reliable this is). >> >> If you mean that the same part of the buffer header gets smashed every >> time, yes, this is reliably reproducible (well, in other words, when >> it happens (at random), it happens in the same place every time). It > > That is correct. Both me and Daniel had the crash occuring exactly > at the same place. Hmm. Well, almost: this time the line number is different, and it looks more plausible. Can you get me the local variables from your stack trace of this frame? (gdb) i loc >> may mean that Vinum is doing it, but as far as I can tell it's always >> 6 words being zeroed out, and I don't do that anywhere in Vinum. The >> other possibility, which I consider most likely, is that the data >> structures accidentally get freed and used by some other driver (or, >> possibly, that some other driver freed them first and then continued >> using them). This would explain the observed correlation with the fxp >> driver. > > Do you think that the later is more probable? I had fxp card there. That's what I said. I don't necessarily think it's a bug in the fxp driver, but Vinum is unique in the way it allocates buffer headers, so it's possible. >>> b) I still believe, that there is a problem somewhere in the >>> vinum code (probably within raid5 routines, since a mirror >>> setup worked fine). >> >> Correct. I have no doubt about it. But some bugs are difficult to >> find, and I need help. > > Hmm.. that part of the code in question, isn't it shared for both > raid1 and raid5? Yes, but if you look a few lines higher, you'll see that we've called complete_raid5_write for RAID-[45], and it's possible that something has happened there. Note that in the other case (buffer header corruption), we're executing non-Vinum code when the crash comes, so there's no requirement to stay in RAID-5 code. 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-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 17: 9:41 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 17:09:38 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 0737537B402 for ; Wed, 3 Jan 2001 17:09:37 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA17434; Thu, 4 Jan 2001 11:39:27 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: <200101030104.f03143902756@henry.cs.adfa.edu.au> Date: Thu, 04 Jan 2001 11:39:27 +1030 (CST) Sender: doconnor@gsoft.com.au From: "Daniel O'Connor" To: wkt@cs.adfa.edu.au Subject: RE: kldload: Exec format error, is 4.2 problem? Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-01 Warren Toomey wrote: > # kldload /usr/local/modules/rtc.ko > kldload: can't load /usr/local/modules/rtc.ko: Exec format error > > Fortunately, I kept a copy of rtc.ko from before the rebuild, and it > loads fine. > > -r-xr-xr-x 1 root wheel 6087 Jan 3 12:00 good_rtc.ko > -r-xr-xr-x 1 root wheel 6095 Jan 3 12:02 rtc.ko > > I also can't load vmmon.ko nor vmnet.ko, same problem. > > Is this a 4.2-thing, or have I just done something wrong? I've > searched the FreeBSD mail lists for clues, with no luck. Do you see any messages in the kernel log about missing symbols? Also, have you updated the port recently? Disclaimer: I don't use the vmware port :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 17:11:47 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 17:11:43 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 52E8837B402 for ; Wed, 3 Jan 2001 17:11:41 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 08C696A911; Thu, 4 Jan 2001 11:41:38 +1030 (CST) Date: Thu, 4 Jan 2001 11:41:38 +1030 From: Greg Lehey To: Roman Shterenzon Cc: Daniel Lang , freebsd-stable@freebsd.org Subject: Re: Vinum saga continues Message-ID: <20010104114138.H4336@wantadilla.lemis.com> References: <20010104103426.C4336@wantadilla.lemis.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 roman@xpert.com on Thu, Jan 04, 2001 at 02:33:18AM +0200 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 4 January 2001 at 2:33:18 +0200, Roman Shterenzon wrote: > On Thu, 4 Jan 2001, Greg Lehey wrote: > >> [Format recovered--see http://www.lemis.com/email/email-format.html] >> >> On Wednesday, 3 January 2001 at 14:15:14 +0200, Roman Shterenzon wrote: >>> Hi, >>> >>> Attached is the most valuable information that was in my pr 22103. >>> I've read the vinumdebug and the other guy's PR. >>> I'm still not getting what is missing. >>> You told the other guy to submit the backtrace, but it was in fact submitted! >>> It's as well in my PR as well. >>> Your responses are very brief - "please read vinumdebug", but in fact, if >>> there's something that is missing, you can be more specific. >> >> OK. I don't know what's so difficult about this, but here we go:. On >> the web page to which I refer, I say: >> >> If you need to contact me because of problems with Vinum, please send >> me a mail message with the following information: >> >> - What problems are you having? >> - Which version of FreeBSD are you running? >> >> I can't find this in your report. > > So I was right. You didn't read it. I thought this was supposed to be complete information. >> - If you have a crash, please supply a backtrace from the dump >> analysis as discussed below under Kernel Panics. Please don't >> delete the crash dump; it may be needed for further analysis. >> >> Basically, all I can see here is the backtrace, which is still wrapped >> at 80 characters, despite all my requests. I've had to manually >> reformat it to make it legible. Have you really read the web page? > > Hmm.. I don't know why it wrapped around at 80 chars. > I took it out of the "Raw PR" Well, the "raw PR" was pretty rough too, but it's probably your MUA. >> OK, this is *not* the buffer header corruption bug, but it's happening >> in a very similar position. With the buffer header corruption, you >> wouldn't have got as far as this, because b_iodone would be zeroed >> out. I also can't see any other obvious damage to the buffer header. >> >> What we need to do now is to find out where the trap occurred. That's >> at line 199 of complete_rqe, which shows as the very end of the >> function. Could you give me the following information from gdb, >> please? >> >> (gdb) x/20i 0xc150fc60 >> >> Thanks > > Heh :( I wish you read the PR when I submitted it. It was there. I > only took it out of the closed PR and resent to you. This crash is > not available anymore. I used the disks for RAID-1 setup. OK, this is another one that got away. I can't do any more without followup information. > But, for curiosity, what this command supposedly does? It disassembles 20 instructions starting at the specified address. It will give us a better idea of what's going on. > The fact that the page fault occures at the end of the function, > i.e. "return" hints that perhaps the return address from the call > was smashed. Ah, that might be what Alfred was referring to. Yes, we could have checked for that. But under those circumstances you would also expect to get a junk stack trace (not necessarily, but usually). Without a dump, of course, we'll never know. > I think that the crash can be reproduced - three disks in raid5 > setup, more than 50% filled. find /raid -print should crash it. Believe me, I tried that again and again. It worked fine here. > I can send you my setup. I'd 3 x 36Gb IBM drives on adaptec. My > mutilated and huge PR kern/22103 has more info (dmesg!) that you may > or may not find interesting. No, without a dump it's not much help. I *do* now have an fxp board here, so I should try that first. 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-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 17:40:30 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 17:40:24 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.jcsd1.k12.wy.us (unknown [209.181.17.144]) by hub.freebsd.org (Postfix) with ESMTP id 5324637B400 for ; Wed, 3 Jan 2001 17:40:24 -0800 (PST) Received: (from uucp@localhost) by mail.jcsd1.k12.wy.us (8.11.1/8.9.3) id f041dOp87162 for ; Wed, 3 Jan 2001 18:39:24 -0700 (MST) (envelope-from matt@jcsd1.k12.wy.us) Received: from UNKNOWN(137.89.176.38), claiming to be "hub.jcsd1.k12.wy.us" via SMTP by mail.jcsd1.k12.wy.us, id smtpdH87160; Wed Jan 3 18:39:21 2001 Received: from chaos.jcsd1.k12.wy.us (chaos.jcsd1.k12.wy.us [10.10.0.22]) by hub.jcsd1.k12.wy.us (8.11.1/8.11.1) with ESMTP id f041eJa16794 for ; Wed, 3 Jan 2001 18:40:20 -0700 (MST) (envelope-from matt@jcsd1.k12.wy.us) Received: from localhost (matt@localhost) by chaos.jcsd1.k12.wy.us (8.9.3/8.9.3) with ESMTP id SAA99831 for ; Wed, 3 Jan 2001 18:40:19 -0700 (MST) (envelope-from matt@jcsd1.k12.wy.us) Date: Wed, 3 Jan 2001 18:40:18 -0700 (MST) From: Matt DeLapp To: freebsd-stable@freebsd.org Subject: 4.2-STABLE - Fatal trap 12 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having lockup problems with a Compaq Prolinea 5100. It's an old Pentium-100 that's been working fine with 3.3. It's locked up 6 times in the last month or so since 4.2 was installed. The machine is currently using sources cvsupped 12/25/00 at about 20:45 (-0600). I've tried to come up with kernel debug information but since it's my first stab at this I'm sure it's incomplete. I'd appreciate any pointers here. Matt root@dws-ccs: {163} gdb -k 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 "i386-unknown-freebsd". (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /home/matt/worf/kernel.0 (kgdb) core-file /home/matt/worf/vmcore.0 IdlePTD 3948544 initial pcb at 325a40 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x56c0cf00 fault code= supervisor read, page not present instruction pointer= 0x8:0xc0187b90 stack pointer = 0x10:0xc87eee34 frame pointer = 0x10:0xc87eee58 code segment= base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 2658 (sendmail) interrupt mask = net tty trap number= 12 panic: page fault syncing disks... 25 25 19 9 done Uptime: 1d0h28m44s dumping to dev #da/0x20001, offset 32768 dump 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:469 469if (dumping++) { (kgdb) where #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:469 #1 0xc016b427 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:309 #2 0xc016b7a4 in poweroff_wait (junk=0xc02eec6f, howto=-935448096) at /usr/src/sys/kern/kern_shutdown.c:556 #3 0xc02a3625 in trap_fatal (frame=0xc87eedf4, eva=1455476480) at /usr/src/sys/i386/i386/trap.c:951 #4 0xc02a32fd in trap_pfault (frame=0xc87eedf4, usermode=0, eva=1455476480) at /usr/src/sys/i386/i386/trap.c:844 #5 0xc02a2eb7 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = 0, tf_ebp = -931205544, tf_isp = -931205600, tf_ebx = 1, tf_edx = 1455476480, tf_ecx = 16, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1072137328, tf_cs = 8, tf_eflags = 66054, tf_esp = -1052230016, tf_ss = -935448096}) at /usr/src/sys/i386/i386/trap.c:443 #6 0xc0187b90 in sosend (so=0xc754b9c0, addr=0x0, uio=0xc87eeed8, top=0x0, control=0x0, flags=0, p=0xc83e31e0) at /usr/src/sys/kern/uipc_socket.c:564 #7 0xc017c57c in soo_write (fp=0xc1483e80, uio=0xc87eeed8, cred=0xc13cbf00, flags=0, p=0xc83e31e0) at /usr/src/sys/kern/sys_socket.c:79 #8 0xc01791bd in dofilewrite (p=0xc83e31e0, fp=0xc1483e80, fd=7, buf=0x80f6000, nbyte=15325, offset=-1, flags=0) at /usr/src/sys/sys/file.h:159 #9 0xc0179076 in write (p=0xc83e31e0, uap=0xc87eef80) at /usr/src/sys/kern/sys_generic.c:328 #10 0xc02a38d1 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 135225344, tf_esi = 673498632, tf_ebp = -1077957204, tf_isp = -931205164, tf_ebx = 673425000, tf_edx = 673498632, tf_ecx = 673383208, tf_eax = 4, tf_trapno = 0, tf_err = 2, tf_eip = 673384524, tf_cs = 31, tf_eflags = 663, tf_esp = -1077957248, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1150 #11 0xc0295aa5 in Xint0x80_syscall () #12 0x2822e54a in ?? () #13 0x2822e4b9 in ?? () #14 0x805d224 in ?? () #15 0x808c197 in ?? () #16 0x805b1a4 in ?? () #17 0x8058570 in ?? () #18 0x805831c in ?? () #19 0x8068dfd in ?? () ---Type to continue, or q to quit--- #20 0x804bffd in ?? () (kgdb) dmesg output: Copyright (c) 1992-2000 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.2-STABLE #0: Tue Jan 2 14:10:14 MST 2001 matt@dws-ccs.jcsd1.k12.wy.us:/usr/obj/usr/src/sys/WORF Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 100227805 Hz CPU: Pentium/P54C (100.23-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x1bf real memory = 50331648 (49152K bytes) config> en ed0 config> po ed0 0x280 config> ir ed0 5 config> iom ed0 0xd8000 config> f ed0 0 config> q avail memory = 44941312 (43888K bytes) bios32: Bad BIOS32 Service Directory Preloaded elf kernel "kernel" at 0xc03a5000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03a509c. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0 on motherboard pci0: on pcib0 pci0: (vendor=0x0e11, dev=0x1000) at 0.0 irq 128 pci0: at 10.0 irq 11 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x1080-0x10ff mem 0x41000000-0x4100007f irq 11 at device 13.0 on pci0 xl0: Ethernet address: 00:50:04:07:87:23 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vx0: <3COM 3C595 Fast Etherlink III PCI> port 0x1000-0x101f irq 11 at device 14.0 on pci0 utp/tx[*tx*] address 00:a0:24:76:b0:b4 vx0: driver is using old-style compatability shims isab0: at device 15.0 on pci0 isa0: on isab0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 aha0 at port 0x330-0x333 irq 10 drq 5 on isa0 aha0: AHA-1542CF FW Rev. E.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 plip0: on ppbus0 ed0 at port 0x280-0x29f iomem 0xd8000 irq 5 drq 0 on isa0 ed0: address 00:00:e8:5f:07:36, type NE2000 (16 bit) IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, unlimited logging Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at aha0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: 1010MB (2069860 512 byte sectors: 64H 32S/T 1010C) da1 at aha0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 3.300MB/s transfers da1: 1010MB (2069860 512 byte sectors: 64H 32S/T 1010C) da2 at aha0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 3.300MB/s transfers da2: 2049MB (4197405 512 byte sectors: 64H 32S/T 2049C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 18:40:36 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 18:40:34 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from pinky.plambert.net (pinky.plambert.net [205.219.88.225]) by hub.freebsd.org (Postfix) with ESMTP id E319C37B400 for ; Wed, 3 Jan 2001 18:40:33 -0800 (PST) Received: (from plambert@localhost) by pinky.plambert.net (8.11.1/8.9.3) id f042eXb28612; Wed, 3 Jan 2001 18:40:33 -0800 (PST) (envelope-from plambert) Date: Wed, 3 Jan 2001 18:40:33 -0800 From: "Paul M . Lambert" To: "Paul M . Lambert" Cc: stable@freebsd.org Subject: Re: 4.2-STABLE broken build? (Recent commit) Message-ID: <20010103184033.F86614@pinky.plambert.net> References: <200101030436.XAA04894@cowpie.acm.vt.edu> <20010102220820.E86614@pinky.plambert.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010102220820.E86614@pinky.plambert.net> Sender: plambert@pinky.plambert.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, as a temporary workaround, you should be able to edit the Makefile in /usr/src/sys/modules and remove the mention of 'ray' from the line starting with SUBDIR+= --plambert On Tue, 02 Jan 2001, Paul M . Lambert wrote: > I am seeing the same thing, on a newly-installed 4.2-RELEASE system. > > About to cvsup again, maybe something is fixed. > > --plambert > -- I hate bombs, terrorism, fear, plans, future and past injustices, manifestos, popular sentiment, ignition, timetables, meetings, and poorly adjusted weasels. A warm hello to my friends and fans in domestic surveillance! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 19:10:35 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 19:10:32 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from ns.uninet.ee (ns.uninet.ee [194.204.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 588AC37B400 for ; Wed, 3 Jan 2001 19:10:32 -0800 (PST) Received: from inspiral.net (parnu-isdn-45.uninet.ee [194.204.43.109]) by ns.uninet.ee (Postfix) with ESMTP id 5DFDB25BF5 for ; Thu, 4 Jan 2001 05:10:30 +0200 (EET) Message-ID: <3A53E988.17B052AD@inspiral.net> Date: Thu, 04 Jan 2001 05:10:00 +0200 From: Lauri Laupmaa Organization: Inspiral.Net X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en,et MIME-Version: 1.0 Newsgroups: ee.arvutid.unix.bsd To: stable@freebsd.org Subject: 4.2-REL install - no schg flags ? Content-Type: multipart/alternative; boundary="------------21E0C12E77A15FFE61095ABE" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------21E0C12E77A15FFE61095ABE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi I just found out that on 3 machines I have recently installed there are NO schg flags on /kernel ; /usr/lib/libc.so.4 or any other file which is supposed to have such :( an installer bug??? L. --------------21E0C12E77A15FFE61095ABE Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi

I just found out that on 3 machines I have recently installed there are NO schg flags on /kernel ; /usr/lib/libc.so.4 or any other file which is supposed to have such :(

an installer bug???

L. --------------21E0C12E77A15FFE61095ABE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 19:21:51 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 19:21:49 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id 9FA1D37B400 for ; Wed, 3 Jan 2001 19:21:48 -0800 (PST) Received: (qmail 93365 invoked from network); 4 Jan 2001 03:21:46 -0000 Received: from unknown (HELO prydn.tacni.net) (204.155.159.123) by 216.178.136.168 with SMTP; 4 Jan 2001 03:21:46 -0000 Received: (qmail 43653 invoked by uid 1001); 4 Jan 2001 03:21:51 -0000 Date: Wed, 3 Jan 2001 21:21:50 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Re: C++ threaded programs Message-ID: <20010103212150.A43624@superhero.org> References: <20010103103755.A62189@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: <20010103103755.A62189@dragon.nuxi.com>; from TrimYourCc@NUXI.com on Wed, Jan 03, 2001 at 10:37:55AM -0800 X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: needo@prydn.tacni.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 10:37:55AM -0800, David O'Brien wrote: > I have been unable to get anyone I've directly asked to actually test it > (that emailed me saying they have a problem with the current state of the > world). Here is what happened after test1.. This is a program called mq3 it is written in C++ and uses qt's threaded library. I applied your patch, rebuilt my world. All that good stuff, then I rebuilt qt with its thread support, and recompiled the app. It cores. The author develops on FreeBSD and the last update he made was right before the offending C++ patch was submitted and it works fine for him. Here is the information. (gdb) run Starting program: /usr/home/needo/mq3-6/bin/mq3 Xlib: extension "RENDER" missing on display ":0.0". Program received signal SIGBUS, Bus error. 0x283a933f in QWidget::event () from /usr/X11R6/lib/libqt2-mt.so (gdb) bt #0 0x283a933f in QWidget::event () from /usr/X11R6/lib/libqt2-mt.so Error accessing memory address 0x0: Bad address. The above was compiled with Pentium Pro optimizations the following core/bt was compiled with no optimizations whatsoever... (gdb) run Starting program: /usr/home/needo/mq3-6/bin/mq3 Xlib: extension "RENDER" missing on display ":0.0". Program received signal SIGSEGV, Segmentation fault. 0x8059dfc in MQ3::MQ3 (this=0xbfbff800) at mq3.cpp:84 84 songLabel->setText(tr("No song loaded.")); (gdb) bt #0 0x8059dfc in MQ3::MQ3 (this=0xbfbff800) at mq3.cpp:84 #1 0x8059099 in main (argc=1, argv=0xbfbff978) at main.cpp:17 #2 0x80520f7 in _start () I dont know how much help will this is, and if this is FreeBSD's failure, or the application's fault. I have another application I will test tonight, and report my findings. -- Erich Zigler Procrastination avoids Boredom; One never has the feeling that there is nothing important to do! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 20:38: 3 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 20:38:01 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158]) by hub.freebsd.org (Postfix) with ESMTP id 6D78937B400 for ; Wed, 3 Jan 2001 20:37:59 -0800 (PST) Received: (from wkt@localhost) by henry.cs.adfa.edu.au (8.11.1/8.9.3) id f044i6e04138; Thu, 4 Jan 2001 15:44:06 +1100 (EST) (envelope-from wkt) From: Warren Toomey Message-Id: <200101040444.f044i6e04138@henry.cs.adfa.edu.au> Subject: Re: kldload: Exec format error, is 4.2 problem? In-Reply-To: from "Daniel O'Connor" at "Jan 4, 2001 11:39:27 am" To: "Daniel O'Connor" Date: Thu, 4 Jan 2001 15:44:06 +1100 (EST) Cc: stable@freebsd.org Reply-To: wkt@cs.adfa.edu.au X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article by Daniel O'Connor: > On 03-Jan-01 Warren Toomey wrote: > > # kldload /usr/local/modules/rtc.ko > > kldload: can't load /usr/local/modules/rtc.ko: Exec format error > > Is this a 4.2-thing, or have I just done something wrong? I've > > searched the FreeBSD mail lists for clues, with no luck. > > Do you see any messages in the kernel log about missing symbols? > Also, have you updated the port recently? > Disclaimer: I don't use the vmware port :) > Daniel O'Connor No, I don't see any kernel messages in /var/log/messages. I downloaded and used the vmware port for FreeBSD 4.2 after I'd moved to 4.2-STABLE. Has there been any changes to kernel modules, magic numbers etc. that would cause this problem? I'll try reading through imgact_elf.c and compare magic numbers there with the values in the .ko files. Warren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 20:41:43 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 20:41:42 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 1DF6037B400 for ; Wed, 3 Jan 2001 20:41:40 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA19642; Thu, 4 Jan 2001 15:11:31 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: <200101040444.f044i6e04138@henry.cs.adfa.edu.au> Date: Thu, 04 Jan 2001 15:11:30 +1030 (CST) Sender: doconnor@gsoft.com.au From: "Daniel O'Connor" To: wkt@cs.adfa.edu.au Subject: Re: kldload: Exec format error, is 4.2 problem? Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jan-01 Warren Toomey wrote: > No, I don't see any kernel messages in /var/log/messages. I downloaded > and used the vmware port for FreeBSD 4.2 after I'd moved to 4.2-STABLE. > > Has there been any changes to kernel modules, magic numbers etc. that > would cause this problem? Hmm.. well generally when you update your kernel source you need to update the kld's as well. This happens automatically when you build a kernel for the 'normal' kld's, but the ones which come in ports (vmware, skip) need to be updated by rebuilding the port. > I'll try reading through imgact_elf.c and compare magic numbers there > with the values in the .ko files. Good luck :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 21:22: 3 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 21:21:59 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158]) by hub.freebsd.org (Postfix) with ESMTP id 8DCB037B400 for ; Wed, 3 Jan 2001 21:21:57 -0800 (PST) Received: (from wkt@localhost) by henry.cs.adfa.edu.au (8.11.1/8.9.3) id f045SOI05021; Thu, 4 Jan 2001 16:28:24 +1100 (EST) (envelope-from wkt) From: Warren Toomey Message-Id: <200101040528.f045SOI05021@henry.cs.adfa.edu.au> Subject: Re: kldload: Exec format error, is 4.2 problem? In-Reply-To: from "Daniel O'Connor" at "Jan 4, 2001 11:39:27 am" To: "Daniel O'Connor" Date: Thu, 4 Jan 2001 16:28:22 +1100 (EST) Cc: wkt@cs.adfa.edu.au, stable@FreeBSD.ORG Reply-To: wkt@cs.adfa.edu.au X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article by Daniel O'Connor: > On 03-Jan-01 Warren Toomey wrote: > > # kldload /usr/local/modules/rtc.ko > > kldload: can't load /usr/local/modules/rtc.ko: Exec format error > > > > Is this a 4.2-thing, or have I just done something wrong? I've > > searched the FreeBSD mail lists for clues, with no luck. Ok, I've found the answer. The rtc and vmware2 ports both turn this flag on in the appropriate Makefiles: KMODDEPS= linux This creates a binary file called `linux' which is linked in (?) to the the module at compile time, e.g: ld -Bshareable -o vmmon_up.ko setdef0.o vmmon_up.kld setdef1.o linux By commenting out this flag, the file `linux' isn't used, and the module can then be loaded by kldload. Also, vmware appears to work fine. Hope this helps someone else! Cheers, Warren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 21:29: 0 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 21:28:58 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 87EBA37B400 for ; Wed, 3 Jan 2001 21:28:56 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA20213; Thu, 4 Jan 2001 15:58:51 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: <200101040528.f045SOI05021@henry.cs.adfa.edu.au> Date: Thu, 04 Jan 2001 15:58:51 +1030 (CST) Sender: doconnor@gsoft.com.au From: "Daniel O'Connor" To: wkt@cs.adfa.edu.au Subject: Re: kldload: Exec format error, is 4.2 problem? Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jan-01 Warren Toomey wrote: > In article by Daniel O'Connor: > > On 03-Jan-01 Warren Toomey wrote: > > > # kldload /usr/local/modules/rtc.ko > > > kldload: can't load /usr/local/modules/rtc.ko: Exec format error > > > > > > Is this a 4.2-thing, or have I just done something wrong? I've > > > searched the FreeBSD mail lists for clues, with no luck. > > Ok, I've found the answer. The rtc and vmware2 ports both turn this > flag on in the appropriate Makefiles: > > KMODDEPS= linux > > This creates a binary file called `linux' which is linked in (?) to the > the module at compile time, e.g: > > ld -Bshareable -o vmmon_up.ko setdef0.o vmmon_up.kld setdef1.o linux > > By commenting out this flag, the file `linux' isn't used, and the module > can then be loaded by kldload. Also, vmware appears to work fine. The reason it has the KMODDEPS line is to add a dependancy on the linux kld. This means that if the vmware kld is loaded the linux one will be loaded if necessary. I think you should send this directly to the vmware maintainer though :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 22:55:52 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 22:55:49 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id B79A537B402 for ; Wed, 3 Jan 2001 22:55:46 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14E4Hs-000N7a-00 for freebsd-stable@freebsd.org; Thu, 4 Jan 2001 09:54:13 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.16 #1) id 14E4JC-000DUI-00 for freebsd-stable@freebsd.org; Thu, 04 Jan 2001 09:55:34 +0300 Date: Thu, 4 Jan 2001 09:55:34 +0300 From: Odhiambo Washington To: FBSD-STABLE Subject: 4.2-STABLE build fails Message-ID: <20010104095534.A51777@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , FBSD-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD poeza.iconnect.co.ke 3.5-STABLE FreeBSD 3.5-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: Odhiambo Washington Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I've seen much of this discussed here but mine seems to break at this point: /usr/obj/usr/src/share/doc/usd/13.viref/troff.core ..and with this msg on the console... Jan 3 18:54:07 alouette /kernel: pid 54505 (troff), uid 0: exited on signal 11 (core dumped) Jan 3 18:54:07 alouette /kernel: pid 54523 (troff), uid 0: exited on signal 11 (core dumped) Even a fresh cvsup (after rm-ing all my srcs and usr/obj) does not help. Any pointer what this 13.viref thing is and how I can sort that out will be highly appreciated. -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. Blessed are they who can laugh at themselves, for they shall never cease to be amused. (contributed by Chris Johnston) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 23: 6:29 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 23:06:27 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id ED73F37B400 for ; Wed, 3 Jan 2001 23:06:23 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14E4S9-000NrH-00 for freebsd-stable@freebsd.org; Thu, 4 Jan 2001 10:04:50 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.16 #1) id 14E4TV-000DWk-00 for freebsd-stable@freebsd.org; Thu, 04 Jan 2001 10:06:13 +0300 Date: Thu, 4 Jan 2001 10:06:13 +0300 From: Odhiambo Washington To: freebsd-stable@freebsd.org Subject: Re: Problem with Syslog and Stable Message-ID: <20010104100613.B51777@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , freebsd-stable@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 "Lawrence Farr" on Wed, Jan 03, 2001 at 04:10:19PM -0000 X-Operating-System: FreeBSD poeza.iconnect.co.ke 3.5-STABLE FreeBSD 3.5-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: Odhiambo Washington Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Lawrence Farr [20010103 19:10]: writing on the subject 'Problem with Syslog and Stable' =>I am getting a lot of: => =>Jan 3 16:04:55 frogger syslogd: '/' in "/dev//dev/tty" => =>in /var/log/messages, and my daily run output has: => =>Local system status: =>uptime: /dev//dev/tty: No such file or directory => 2:36AM up 12 days, 9:55, 5 users, load averages: 0.03, 0.01, 0.00 => =>In it. => =>Issuing the w command gives me: => =>w: /dev//dev/tty: No such file or directory => 4:07PM up 12 days, 23:26, 6 users, load averages: 0.00, 0.00, 0.00 =>etc. => =>Im getting this on multiple machines that I have, and all have been built =>from there own sources to stable on different days/weeks, and a =>mergemaster -a run. => =>Anyone got any ideas where to start looking? Sounds quite a rare situation, unless there is a file that you've moved around while adapting it to each machine - and that file could be having a small issue within. I'm thinking of a situation where you do not want to manually edit your syslog.conf for every individual machine and so just copy one syslog.conf from machine A into machines B and C, which then end up inheriting the small typo in syslog.conf. You could start from there but that's a guess. -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. Cloquet hated reality but realized it was still the only place to get a good steak. -Woody Allen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 3 23:54:38 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 23:54:34 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 5F6BB37B404 for ; Wed, 3 Jan 2001 23:54:34 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f047sUW55674; Wed, 3 Jan 2001 23:54:30 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Jan 2001 23:54:30 -0800 (PST) From: Matt Dillon Message-Id: <200101040754.f047sUW55674@earth.backplane.com> To: Marc Culler , freebsd-stable@FreeBSD.ORG Subject: NFSv3 O_EXCL file create - protocol spec & solution (was Re: Bug in NFSv3 client) References: <20010103155533.B71238@math.uic.edu> <200101032243.f03Mhar51440@earth.backplane.com> <200101032308.f03N84f51776@earth.backplane.com> <200101032322.f03NMTK51973@earth.backplane.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The RFC (1813) says that the exclusive-file-create NFS op passes a verifier. It says, and I quote: "One aspect of the NFS version 3 protocol CREATE procedure warrants particularly careful consideration: the mechanism introduced to support the reliable exclusive creation of regular files. The mechanism comes into play when how.mode is EXCLUSIVE. In this case, how.verf contains a verifier that can reasonably be expected to be unique. A combination of a client identifier, perhaps the client network address, and a unique number generated by the client, perhaps the RPC transaction identifier, may be appropriate." What that means is that the verifier can be anything. Here's why the FreeBSD server was storing the verifier as the file access time: "verifier must be stored in stable storage to prevent erroneous failure on retransmission of the request. It is assumed that an exclusive create is being performed because exclusive semantics are critical to the application. Because of the expected usage, exclusive CREATE does not rely solely on the normally volatile duplicate request cache for storage of the verifier. The duplicate request cache in volatile storage does not survive a crash and may actually flush on a long network partition, opening failure windows. In the UNIX local file system environment, the expected storage location for the verifier on creation is the metadata (time stamps) of the file. For this reason, an exclusive file create may not include initial attributes because the server would have nowhere to store the verifier." Ahhh, so now we know why FreeBSD is passing the IP address of the interface plus a 'unique' number! Or trying anyway. And also: "Once the client has performed a successful exclusive create, it must issue a SETATTR to set the correct file attributes. Until it does so, it should not rely upon any of the file attributes, since the server implementation may need to overload file metadata to store the verifier." What this means is that the FreeBSD client is supposed to call SETATTR to set the correct file attributes after the O_EXCL open succeeds. It is in fact doing this, but the 'atime' attribute in the 'vap' structure is not initialized, so the SETATTR call never actually fixes up the access time. Solaris probably shouldn't be generating an error for the 'bogus' time specification, as that can race with an O_EXCL create, but I think fixing the FreeBSD clients to do the proper SETATTR should solve the problem. I've included the patch below. The patch will fix FreeBSD clients. I will commit it to -current now and to -stable in two days if there aren't any problems. (Throw away any previous patches you might have applied). -Matt Index: nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.150 diff -u -r1.150 nfs_vnops.c --- nfs_vnops.c 2000/01/05 00:32:18 1.150 +++ nfs_vnops.c 2001/01/04 07:48:37 @@ -1436,8 +1436,21 @@ } if (newvp) vput(newvp); - } else if (v3 && (fmode & O_EXCL)) + } else if (v3 && (fmode & O_EXCL)) { + /* + * We are normally called with only a partially initialized + * VAP. Since the NFSv3 spec says that server may use the + * file attributes to store the verifier, the spec requires + * us to do a SETATTR RPC. FreeBSD servers store the verifier + * in atime, but we can't really assume that all servers will + * so we ensure that our SETATTR sets both atime and mtime. + */ + if (vap->va_mtime.tv_sec == VNOVAL) + vfs_timestamp(&vap->va_mtime); + if (vap->va_atime.tv_sec == VNOVAL) + vap->va_atime = vap->va_mtime; error = nfs_setattrrpc(newvp, vap, cnp->cn_cred, cnp->cn_proc); + } if (!error) { if (cnp->cn_flags & MAKEENTRY) cache_enter(dvp, newvp, cnp); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 0:17:48 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 00:17:47 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hypernet.hyper.net (hypernet.hyper.gr [193.218.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 083A537B400 for ; Thu, 4 Jan 2001 00:17:43 -0800 (PST) Received: from escape.gr (patrinos-2.hyper.gr [193.218.2.19]) by hypernet.hyper.net (8.9.3/8.9.3/Hypernet-0.1) with ESMTP id KAA26502 for ; Thu, 4 Jan 2001 10:15:11 +0200 Message-ID: <3A5432C3.95A65586@escape.gr> Date: Thu, 04 Jan 2001 10:22:29 +0200 From: dxoch Organization: ESCAPE Services X-Mailer: Mozilla 4.7 (Macintosh; I; PPC) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Vinum Question Content-Type: text/plain; charset=iso-8859-7; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using RAID-1 Vinum volumes, without any problem till now, but i never succeed to use a Vinum volume as a root partition. Is it possible, and how? (I hope this is the place to ask something like that) -Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 1:18:16 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 01:18:15 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E52F237B400 for ; Thu, 4 Jan 2001 01:18:14 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA93313; Thu, 4 Jan 2001 01:18:13 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f049ICk67493; Thu, 4 Jan 2001 01:18:12 -0800 (PST) (envelope-from obrien) Date: Thu, 4 Jan 2001 01:18:11 -0800 From: "David O'Brien" To: Roman Shterenzon Cc: stable@FreeBSD.ORG Subject: Re: C++ threaded programs Message-ID: <20010104011811.A67473@dragon.nuxi.com> Reply-To: stable@FreeBSD.ORG References: <20010103103755.A62189@dragon.nuxi.com> <978563809.3a53b2e186ca1@webmail.harmonic.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <978563809.3a53b2e186ca1@webmail.harmonic.co.il>; from roman@harmonic.co.il on Thu, Jan 04, 2001 at 01:16:49AM +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: obrien@NUXI.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 01:16:49AM +0200, Roman Shterenzon wrote: > On the other side, I tested Daniel's patch - i.e. -nostdlib in libstdc++ > and it works fine for everything I've tested it with - the only It matters ZILCH that that patch worked for you. What that patch does is just wrong. It was posted to help us pin down the problematic area. I need feedback on *my* current patch, nothing else. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 1:20:22 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 01:20:21 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id DF96D37B400 for ; Thu, 4 Jan 2001 01:20:20 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA93323; Thu, 4 Jan 2001 01:20:20 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f049KII67518; Thu, 4 Jan 2001 01:20:18 -0800 (PST) (envelope-from obrien) Date: Thu, 4 Jan 2001 01:20:18 -0800 From: "David O'Brien" To: Erich Zigler Cc: stable@freebsd.org Subject: Re: C++ threaded programs Message-ID: <20010104012018.B67473@dragon.nuxi.com> Reply-To: stable@freebsd.org References: <20010103103755.A62189@dragon.nuxi.com> <20010103212150.A43624@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010103212150.A43624@superhero.org>; from erichz@superhero.org on Wed, Jan 03, 2001 at 09:21:50PM -0600 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: obrien@NUXI.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 09:21:50PM -0600, Erich Zigler wrote: > > I have been unable to get anyone I've directly asked to actually test it > > (that emailed me saying they have a problem with the current state of the > > world). > > Here is what happened after test1.. This is a program called mq3 it is > written in C++ and uses qt's threaded library. > > I applied your patch, rebuilt my world. I fail to see you say my app filed on a *stock* world, and in these way(s). Thus if I don't know what you're starting with, this feedback isn't very helpful. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 1:23: 4 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 01:23:02 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A949D37B400 for ; Thu, 4 Jan 2001 01:23:02 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA93341; Thu, 4 Jan 2001 01:23:01 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f049MoS67538; Thu, 4 Jan 2001 01:22:50 -0800 (PST) (envelope-from obrien) Date: Thu, 4 Jan 2001 01:22:50 -0800 From: "David O'Brien" To: "David W. Chapman Jr." Cc: Jim King , stable@FreeBSD.ORG Subject: Re: Threaded C++ Question Message-ID: <20010104012249.C67473@dragon.nuxi.com> Reply-To: stable@FreeBSD.ORG References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> <20010103103948.A62250@dragon.nuxi.com> <00e201c075be$8a500570$524c8486@jking> <00d601c075bf$643e9440$931576d8@inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00d601c075bf$643e9440$931576d8@inethouston.net>; from dwcjr@inethouston.net on Wed, Jan 03, 2001 at 01:57:24PM -0600 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: obrien@NUXI.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 01:57:24PM -0600, David W. Chapman Jr. wrote: > That was the same problem I encountered (*sarcasm*) Well that was very helpful. How about telling me how *_I_* can experience it? I'm about to give up and just drop fixing this as no one is able to give me any feedback. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 1:24:53 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 01:24:51 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0E83C37B400 for ; Thu, 4 Jan 2001 01:24:51 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA93353; Thu, 4 Jan 2001 01:24:50 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f049On267549; Thu, 4 Jan 2001 01:24:49 -0800 (PST) (envelope-from obrien) Date: Thu, 4 Jan 2001 01:24:48 -0800 From: "David O'Brien" To: Erich Zigler Cc: stable@FreeBSD.ORG Subject: Re: Threaded C++ Question Message-ID: <20010104012448.D67473@dragon.nuxi.com> Reply-To: stable@FreeBSD.ORG References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> <20010102175034.B43962@superhero.org> <20010103104042.B62250@dragon.nuxi.com> <20010103125418.C5283@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010103125418.C5283@superhero.org>; from erichz@superhero.org on Wed, Jan 03, 2001 at 12:54:18PM -0600 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: obrien@NUXI.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 12:54:18PM -0600, Erich Zigler wrote: > > > But I am in the process of porting several C++ apps that are exhibiting > > > truely strange behavior. And I was wondering if this could be the > > > cause. > > I will post a patch -- will you test it? > > Yes. For the test should I compile the conflicting program before the make > world or after it? Both. Save the first one (built with stock world) and also try that on the new world along with the binary built on the new world. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 1:54:29 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 01:54:26 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id C973637B400 for ; Thu, 4 Jan 2001 01:54:25 -0800 (PST) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 3E52B2CE71; Thu, 4 Jan 2001 11:54:16 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.1/8.11.1) id f049qhj17809; Thu, 4 Jan 2001 11:52:43 +0200 (EET) (envelope-from vallo) Date: Thu, 4 Jan 2001 11:52:43 +0200 From: Vallo Kallaste To: Greg Lehey Cc: Josef Karthauser , Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? Message-ID: <20010104115243.A17420@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20010102230107.A559@basildon.homerun> <20010103102943.A770@tao.org.uk> <20010103214829.X4336@wantadilla.lemis.com> <20010103172844.D13221@myhakas.matti.ee> <20010104094938.B4336@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010104094938.B4336@wantadilla.lemis.com>; from grog@lemis.com on Thu, Jan 04, 2001 at 09:49:38AM +1030 Sender: vallo@myhakas.matti.ee Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 09:49:38AM +1030, Greg Lehey wrote: > > so.. What I can do to help you besides installing latest -stable? Do > > you have some formalized test procedures or anything to prove the > > stability of raid-5 configuration? > > No testing can prove stability, only instability :-) If you were able > to get file system corruption, go and check how you did it and see if > you can do it again. Don't forget the information I asked for in > http://www.vinumvm.org/vinum/how-to-debug.html. Hmh, ok. My wording was indeed odd. Does anybody know how I can "crash" the raid-5 volume _without_ removing hot-swap disk from enclosure? Camcontrol stop only stops the disk for a moment, then it spins up again. I don't want to physically remove disk because it's risky business and probably can be one source of problems I had with raid-5 volume. There should be another way. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 1:59: 9 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 01:59:03 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 3A86A37B400 for ; Thu, 4 Jan 2001 01:59:03 -0800 (PST) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: postfix [port 1589]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <113555-224>; Thu, 4 Jan 2001 10:58:56 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id D3C7C13631; Thu, 4 Jan 2001 10:58:45 +0100 (CET) From: Daniel Lang To: Greg Lehey Cc: freebsd-stable@freebsd.org Subject: Re: kern/21148: multiple crashes while using vinum Message-ID: <20010104105845.A14755@atrbg11.informatik.tu-muenchen.de> References: <200101012239.f01MdiH40906@freefall.freebsd.org> <20010103145232.B10169@atrbg11.informatik.tu-muenchen.de> <20010104105428.D4336@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20010104105428.D4336@wantadilla.lemis.com>; from grog@lemis.com on Thu, Jan 04, 2001 at 01:25:57AM +0000 X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Sender: langd@informatik.tu-muenchen.de Date: Thu, 4 Jan 2001 10:58:46 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Greg, Greg Lehey wrote on Thu, Jan 04, 2001 at 01:25:57AM +0000: [..] > As my closing message says, the reason I closed the PR was: > > >> No feedback from submitter. > > I sent you a message on 10 September 2000 asking for additional > information. I received none. There's no reason to get all upset I've sent _two_ direct replies. If you have not received them, then maybe some MX had a problem? If you decided they still did not contain any of the information you need, or have been malformed/mutilated, etc. a short hint would have been appreciated. The first was: [..] Date: Sun, 10 Sep 2000 16:18:11 +0200 Message-ID: <20000910161811.A56954@atrbg11.informatik.tu-muenchen.de> [..] Still in the archives at: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=4693+0+archive/2000/freebsd-bugs/20000917.freebsd-bugs It includes three stack traces then with full debugging symbols. The next day, I sent a followup: Date: Mon, 11 Sep 2000 13:54:21 +0200 Message-ID: <20000911135421.C58840@atrbg11.informatik.tu-muenchen.de> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=77649+0+archive/2000/freebsd-bugs/20000917.freebsd-bugs They have been sent to you personally and to freebsd-bugs. The second one as a pr-followup too. Alas, I omitted freebsd-gnats-submit on the first reply. > now, or make claims about my intentions. This was just a dead PR, and > you've made it clear, both before and now, that you have no intention > of following up on it. This is not a question of "ignorant morons" or > "trust". Sorry, I'm not upset, even if it sounded that way, and I would not dare to speculate about your intentions. My apologies. My memory and my Mailfolders tell me, I did try to be helpful and did indeed follow your request from September 10, to provide you with additional information. I did not hear from you since then. If the reason is, that they still did not meet your requirements, I'm sorry that I would have needed some more hints. IMHO the lacking information was a valid backtrace, which I supplied. So my intention then was indeed to following up on it. After I did not hear anything from you, I even emailed Søren Schmidt, the ATA guy, because I suspected that the bug was in the ATA driver (turned out to be unlikely because scsi-only systems showed similar problems). Even now, I'm still interested in helping to fix the problem, but I may not be able to help with crash-dumps at the moment. [..] > Yes, this looks very much like the other issues. But you must > understand that there's nothing I can do without further information. Agreed. [..] > The trouble with that is that this only happens when the system is > very active, and there are thousands of potential buffer headers which > could be trashed. I do have a trace facility within Vinum, but even > with that it's difficult to figure out what's going on. No doubt. [..] > If you mean that the same part of the buffer header gets smashed every > time, yes, this is reliably reproducible (well, in other words, when > it happens (at random), it happens in the same place every time). It > may mean that Vinum is doing it, but as far as I can tell it's always > 6 words being zeroed out, and I don't do that anywhere in Vinum. The > other possibility, which I consider most likely, is that the data > structures accidentally get freed and used by some other driver (or, > possibly, that some other driver freed them first and then continued > using them). This would explain the observed correlation with the fxp > driver. This is indeed interesting, and maybe a reason why dmesg is not utterly useless. ;) My boxes have a fxp NIC, as well: [..] fxp0: port 0xff80-0xff9f mem 0xfe900000-0xfe9fffff,0xfe2ff000-0xfe2fffff irq 11 at device 12.0 on pci0 [..] [..] > Well, I sent you a message on 10 September 2000, asking for additional > information. You didn't send it to me. See above. I at least tried. :-) [..] > Correct. I have no doubt about it. But some bugs are difficult to > find, and I need help. Ok. Here we are. Unfortunately we should have had this discussion already in September, when the issue was more current to many of us. :-/ However, I've got a twin box, which is not in production at the moment, but currently runs Slowlaris X86. I'm going to put a current FreeBSD on it, and if I find some time and enough disks, I will set up a raid5 again. Maybe we can still find the nasty bugger. Unfortunately I cannot tell, when I find time to do this, it may still take a month or two. Best regards, Daniel -- IRCnet: Mr-Spock - ceterum censeo Microsoftinem esse delendam - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 2: 5:56 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 02:05:53 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 269A237B400 for ; Thu, 4 Jan 2001 02:05:52 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id LAA74185; Thu, 4 Jan 2001 11:05:50 +0100 (CET) (envelope-from des@ofug.org) Sender: des@ofug.org X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Philippe CASIDY Cc: freebsd-stable@freebsd.org Subject: Re: What's new with xdm and 4.2 ? References: <200012291830.eBTIUs501454@greatoak.home> From: Dag-Erling Smorgrav Date: 04 Jan 2001 11:05:50 +0100 In-Reply-To: Philippe CASIDY's message of "Fri, 29 Dec 2000 19:30:54 +0100 (CET)" Message-ID: Lines: 13 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Philippe CASIDY writes: > On 27 Dec, Dag-Erling Smorgrav wrote: > > "Patrick M. Hausen" writes: > > > Make sure you have entries for all local network interfaces in > > > /etc/hosts. > > ...or add '-nolisten tcp' to the X command line in your Xservers file. > Can you tell me where I can found more information about this option? The X man pages. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 2:32:37 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 02:32:35 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hobbits.brel.com (hobbits.brel.com [203.127.231.61]) by hub.freebsd.org (Postfix) with ESMTP id 1875137B400 for ; Thu, 4 Jan 2001 02:32:35 -0800 (PST) Received: by hobbits.brel.com (Postfix, from userid 1001) id EF8983333; Thu, 4 Jan 2001 18:32:31 +0800 (SGT) Date: Thu, 4 Jan 2001 18:32:31 +0800 From: Calvin NG To: "David W. Chapman Jr." Cc: Jim King , stable@FreeBSD.ORG Subject: Re: Threaded C++ Question Message-ID: <20010104183231.F63359@brel.com> References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> <20010103103948.A62250@dragon.nuxi.com> <00e201c075be$8a500570$524c8486@jking> <00d601c075bf$643e9440$931576d8@inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00d601c075bf$643e9440$931576d8@inethouston.net>; from dwcjr@inethouston.net on Wed, Jan 03, 2001 at 01:57:24PM -0600 Sender: calvinng@hobbits.brel.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I get that numerous time too. However, if I run mozilla as root once, things (I think components and dun no what) will get registered properly. After that, the "startup segfault" never happen for me anymore as normal user. Hope this helps. Regards, /calvin lines with :> are quotes from David W. Chapman Jr.'s email :> That was the same problem I encountered :> :> > As of a couple weeks ago Mozilla M18 running on several flavors of 4.2 :> > (RELEASE and a couple different -stable's) would segfault immediately on :> > startup every time. This happened when I built it using the port, and :> when :> > I used the binary from mozilla.org. I haven't tried it since then, due to :> > the messages here about unresolved library bugs being the cause of the :> > problem. :> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 3: 5:22 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 03:05:15 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id 9D53C37B400 for ; Thu, 4 Jan 2001 03:05:12 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id NAA02146; Thu, 4 Jan 2001 13:02:29 +0200 To: Matt DeLapp Subject: Re: 4.2-STABLE - Fatal trap 12 Message-ID: <978606149.3a5458457a94a@webmail.harmonic.co.il> Date: Thu, 04 Jan 2001 13:02:29 +0200 (IST) From: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Matt DeLapp : > I'm having lockup problems with a Compaq Prolinea 5100. It's an > old Pentium-100 that's been working fine with 3.3. It's locked > up 6 times in the last month or so since 4.2 was installed. > The machine is currently using sources cvsupped 12/25/00 at > about 20:45 (-0600). I've tried to come up with kernel debug > information but since it's my first stab at this I'm sure it's > incomplete. I'd appreciate any pointers here. I probably happends in one of the modules. Please send the output of kldstat command. Also, try to "add-symbol-file /modules/suspect.ko" I'm not sure about the command, since I don't know how the offsets will be treated. You can take a look for example at: /usr/src/sys/modules/vinum/.gdbinit.vinum.paths > root@dws-ccs: {163} gdb -k > 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 "i386-unknown-freebsd". > (kgdb) symbol-file kernel.debug > Reading symbols from kernel.debug...done. > (kgdb) exec-file /home/matt/worf/kernel.0 > (kgdb) core-file /home/matt/worf/vmcore.0 > IdlePTD 3948544 > initial pcb at 325a40 > panicstr: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x56c0cf00 > fault code= supervisor read, page not present > instruction pointer= 0x8:0xc0187b90 > stack pointer = 0x10:0xc87eee34 > frame pointer = 0x10:0xc87eee58 > code segment= base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 2658 (sendmail) > interrupt mask = net tty > trap number= 12 > panic: page fault > > syncing disks... 25 25 19 9 > done > Uptime: 1d0h28m44s > > dumping to dev #da/0x20001, offset 32768 > dump 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 > 26 25 24 23 22 21 20 > 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 > --- > #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:469 > 469if (dumping++) { > (kgdb) where > #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:469 > #1 0xc016b427 in boot (howto=256) at > /usr/src/sys/kern/kern_shutdown.c:309 > #2 0xc016b7a4 in poweroff_wait (junk=0xc02eec6f, howto=-935448096) > at /usr/src/sys/kern/kern_shutdown.c:556 > #3 0xc02a3625 in trap_fatal (frame=0xc87eedf4, eva=1455476480) > at /usr/src/sys/i386/i386/trap.c:951 > #4 0xc02a32fd in trap_pfault (frame=0xc87eedf4, usermode=0, > eva=1455476480) > at /usr/src/sys/i386/i386/trap.c:844 > #5 0xc02a2eb7 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, > tf_edi = 0, tf_esi = 0, > tf_ebp = -931205544, tf_isp = -931205600, tf_ebx = 1, tf_edx = > 1455476480, > tf_ecx = 16, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = > -1072137328, > tf_cs = 8, tf_eflags = 66054, tf_esp = -1052230016, tf_ss = > -935448096}) > at /usr/src/sys/i386/i386/trap.c:443 > #6 0xc0187b90 in sosend (so=0xc754b9c0, addr=0x0, uio=0xc87eeed8, > top=0x0, control=0x0, > flags=0, p=0xc83e31e0) at /usr/src/sys/kern/uipc_socket.c:564 > #7 0xc017c57c in soo_write (fp=0xc1483e80, uio=0xc87eeed8, > cred=0xc13cbf00, flags=0, > p=0xc83e31e0) at /usr/src/sys/kern/sys_socket.c:79 > #8 0xc01791bd in dofilewrite (p=0xc83e31e0, fp=0xc1483e80, fd=7, > buf=0x80f6000, > nbyte=15325, offset=-1, flags=0) at /usr/src/sys/sys/file.h:159 > #9 0xc0179076 in write (p=0xc83e31e0, uap=0xc87eef80) > at /usr/src/sys/kern/sys_generic.c:328 > #10 0xc02a38d1 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = 135225344, > tf_esi = 673498632, tf_ebp = -1077957204, tf_isp = -931205164, > tf_ebx = 673425000, > tf_edx = 673498632, tf_ecx = 673383208, tf_eax = 4, tf_trapno = 0, > tf_err = 2, > tf_eip = 673384524, tf_cs = 31, tf_eflags = 663, tf_esp = > -1077957248, tf_ss = 47}) > at /usr/src/sys/i386/i386/trap.c:1150 > #11 0xc0295aa5 in Xint0x80_syscall () > #12 0x2822e54a in ?? () > #13 0x2822e4b9 in ?? () > #14 0x805d224 in ?? () > #15 0x808c197 in ?? () > #16 0x805b1a4 in ?? () > #17 0x8058570 in ?? () > #18 0x805831c in ?? () > #19 0x8068dfd in ?? () > ---Type to continue, or q to quit--- > #20 0x804bffd in ?? () > (kgdb) > > > > dmesg output: > > Copyright (c) 1992-2000 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.2-STABLE #0: Tue Jan 2 14:10:14 MST 2001 > matt@dws-ccs.jcsd1.k12.wy.us:/usr/obj/usr/src/sys/WORF > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 100227805 Hz > CPU: Pentium/P54C (100.23-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x525 Stepping = 5 > Features=0x1bf > real memory = 50331648 (49152K bytes) > config> en ed0 > config> po ed0 0x280 > config> ir ed0 5 > config> iom ed0 0xd8000 > config> f ed0 0 > config> q > avail memory = 44941312 (43888K bytes) > bios32: Bad BIOS32 Service Directory > Preloaded elf kernel "kernel" at 0xc03a5000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc03a509c. > Intel Pentium detected, installing workaround for F00F bug > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0 on motherboard > pci0: on pcib0 > pci0: (vendor=0x0e11, dev=0x1000) at 0.0 irq 128 > pci0: at 10.0 irq 11 > xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x1080-0x10ff mem > 0x41000000-0x4100007f irq 11 at device 13.0 on pci0 > xl0: Ethernet address: 00:50:04:07:87:23 > miibus0: on xl0 > xlphy0: <3Com internal media interface> on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > vx0: <3COM 3C595 Fast Etherlink III PCI> port 0x1000-0x101f irq 11 at > device 14.0 on pci0 > utp/tx[*tx*] address 00:a0:24:76:b0:b4 > vx0: driver is using old-style compatability shims > isab0: at device 15.0 on > pci0 > isa0: on isab0 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > aha0 at port 0x330-0x333 irq 10 drq 5 on isa0 > aha0: AHA-1542CF FW Rev. E.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 > CCBs > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1: configured irq 3 not in bitmap of probed irqs 0 > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > plip0: on ppbus0 > ed0 at port 0x280-0x29f iomem 0xd8000 irq 5 drq 0 on isa0 > ed0: address 00:00:e8:5f:07:36, type NE2000 (16 bit) > IP packet filtering initialized, divert enabled, rule-based forwarding > enabled, default to deny, unlimited logging > Waiting 15 seconds for SCSI devices to settle > Mounting root from ufs:/dev/da0s1a > da0 at aha0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 3.300MB/s transfers > da0: 1010MB (2069860 512 byte sectors: 64H 32S/T 1010C) > da1 at aha0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 3.300MB/s transfers > da1: 1010MB (2069860 512 byte sectors: 64H 32S/T 1010C) > da2 at aha0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 3.300MB/s transfers > da2: 2049MB (4197405 512 byte sectors: 64H 32S/T 2049C) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 3:45: 1 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 03:44:54 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc2.occa.home.com (ha1.rdc2.occa.home.com [24.2.8.66]) by hub.freebsd.org (Postfix) with ESMTP id ABF0337B400; Thu, 4 Jan 2001 03:44:53 -0800 (PST) Received: from home.com ([24.1.137.95]) by mail.rdc2.occa.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010104114453.TDMD24030.mail.rdc2.occa.home.com@home.com>; Thu, 4 Jan 2001 03:44:53 -0800 Message-ID: <3A546233.DB234C09@home.com> Date: Thu, 04 Jan 2001 03:44:51 -0800 From: Ty X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: questions@freebsd.org, stable@freebsd.org Subject: Re: sblive installed, but no sound in 4.2 References: <5.0.2.1.0.20010102024319.00a4ea40@pop.gmx.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thanks for the reply, I gave that a try but alas no luck. I'm now dual booting into mandrake, mandrake has no problem at all dealing with the sblive, it sounds great weird. thanks again! Andreas Ntaflos wrote: > > hi > everything you did seems right, i have an sb live working under fbsd 4.2. > maybe it helps if you do a MAKEDEV all in /dev after rebuilding the kernel > (as this should always be done after building a new kernel), before you do > a MAKEDEV snd0. > > that's the only step i could imagine you forgot, as everything else is what > i did too, and my sound works very well under 4.2 > > regards > Andreas Ntaflos > > At 12:06 01.01.2001 -0800, you wrote: > >Hello, > > > >I believe I have my sound blaster live correctly installed under feebsd > >4.2 yet I can't hear any audio. I do have the mixer settings up. > >i recompiled the kernel with > >device pcm > >(and i have device pci in already) > > > >then rebooted and did a > >cd /dev > >./MAKDEV snd0 > > > >cat /dev/sndstat > > > >shows: > > > >FreeBSD Audio Driver (newpcm) Dec 31 2000 12:36:40 > >Installed devices: > >pcm0: at io 0xd000 irq 10 (4p/3r channels duplex) > > > >Mixer shows > > > >Mixer vol is currently set to 62:62 > >Mixer pcm is currently set to 100:100 > >Mixer speaker is currently set to 100:100 > >Mixer line is currently set to 75:75 > >Mixer mic is currently set to 80:80 > >Mixer cd is currently set to 69:69 > >Mixer rec is currently set to 0:0 > >Mixer line1 is currently set to 75:75 > >Mixer phin is currently set to 69:69 > >Mixer phout is currently set to 97:97 > >Mixer video is currently set to 100:100bash-2.04# cat /dev/sndstat > > > >help, is there something i'm missing here? I've put the volume to 100% on > >everything including speakers and I don't hear a peep, no matter what type > >of audio I attempt to play. > > > >thank you! > > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 3:50:31 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 03:50:25 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail1.javanet.com (mail1.javanet.com [205.219.162.10]) by hub.freebsd.org (Postfix) with ESMTP id 986C737B400; Thu, 4 Jan 2001 03:50:24 -0800 (PST) Received: from wintermute.sekt7.org (146-115-75-83.c6-0.brl-ubr1.sbo-brl.ma.cable.rcn.com [146.115.75.83]) by mail1.javanet.com (8.9.3/8.9.2) with ESMTP id GAA24258; Thu, 4 Jan 2001 06:50:12 -0500 (EST) Date: Thu, 4 Jan 2001 06:53:39 -0500 (EST) From: Evan S X-Sender: kaworu@wintermute.sekt7 To: Ty Cc: questions@freebsd.org, stable@freebsd.org Subject: Re: sblive installed, but no sound in 4.2 In-Reply-To: <3A546233.DB234C09@home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, I think I had the same problem with my SB Live. I run a Dual Celeron. When I would use xmms to play mp3s, nothing would come out of the speakers, even though when I used cat /dev/sndstat it showed a correctly detected and configured SB Live, on irq 18, which used to work fine in Linux. Finally, out of curiosity, I opened up the case and moved my SB Live to PCI slot 2. Then it was on irq 16, and it worked. :-) Maybe this will work for you Evan Sarmiento (kaworu@sektor7.ath.cx) http://sekt7.org/es On Thu, 4 Jan 2001, Ty wrote: > thanks for the reply, I gave that a try but alas no luck. > > I'm now dual booting into mandrake, mandrake has no problem at all > dealing with the sblive, it sounds great weird. > > thanks again! > > > Andreas Ntaflos wrote: > > > > hi > > everything you did seems right, i have an sb live working under fbsd 4.2. > > maybe it helps if you do a MAKEDEV all in /dev after rebuilding the kernel > > (as this should always be done after building a new kernel), before you do > > a MAKEDEV snd0. > > > > that's the only step i could imagine you forgot, as everything else is what > > i did too, and my sound works very well under 4.2 > > > > regards > > Andreas Ntaflos > > > > At 12:06 01.01.2001 -0800, you wrote: > > >Hello, > > > > > >I believe I have my sound blaster live correctly installed under feebsd > > >4.2 yet I can't hear any audio. I do have the mixer settings up. > > >i recompiled the kernel with > > >device pcm > > >(and i have device pci in already) > > > > > >then rebooted and did a > > >cd /dev > > >./MAKDEV snd0 > > > > > >cat /dev/sndstat > > > > > >shows: > > > > > >FreeBSD Audio Driver (newpcm) Dec 31 2000 12:36:40 > > >Installed devices: > > >pcm0: at io 0xd000 irq 10 (4p/3r channels duplex) > > > > > >Mixer shows > > > > > >Mixer vol is currently set to 62:62 > > >Mixer pcm is currently set to 100:100 > > >Mixer speaker is currently set to 100:100 > > >Mixer line is currently set to 75:75 > > >Mixer mic is currently set to 80:80 > > >Mixer cd is currently set to 69:69 > > >Mixer rec is currently set to 0:0 > > >Mixer line1 is currently set to 75:75 > > >Mixer phin is currently set to 69:69 > > >Mixer phout is currently set to 97:97 > > >Mixer video is currently set to 100:100bash-2.04# cat /dev/sndstat > > > > > >help, is there something i'm missing here? I've put the volume to 100% on > > >everything including speakers and I don't hear a peep, no matter what type > > >of audio I attempt to play. > > > > > >thank you! > > > > > > > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > > >with "unsubscribe freebsd-questions" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 4: 8:11 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 04:08:08 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cebu.visayan.com (CEBU.VISAYAN.COM [204.227.192.225]) by hub.freebsd.org (Postfix) with ESMTP id 52C7137B698 for ; Thu, 4 Jan 2001 04:08:07 -0800 (PST) Received: from localhost (matt@localhost) by cebu.visayan.com (8.8.8/8.8.8) with SMTP id FAA04606; Thu, 4 Jan 2001 05:07:52 -0700 (MST) (envelope-from matt@visayan.com) Date: Thu, 4 Jan 2001 05:07:52 -0700 (MST) From: Matt DeLapp To: Roman Shterenzon Cc: Matt DeLapp , freebsd-stable@FreeBSD.ORG Subject: Re: 4.2-STABLE - Fatal trap 12 In-Reply-To: <978606149.3a5458457a94a@webmail.harmonic.co.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 Jan 2001, Roman Shterenzon wrote: > I probably happends in one of the modules. > Please send the output of kldstat command. > Also, try to "add-symbol-file /modules/suspect.ko" > I'm not sure about the command, since I don't know how the offsets will be > treated. You can take a look for example at: > /usr/src/sys/modules/vinum/.gdbinit.vinum.paths matt@worf: {101} kldstat Id Refs Address Size Name 1 1 0xc0100000 2a329c kernel I'll take a look at the example. Thanks. Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 5:44:36 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 05:44:34 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from gallions-reach.inpharmatica.co.uk (gallions-reach.inpharmatica.co.uk [193.115.214.5]) by hub.freebsd.org (Postfix) with ESMTP id 762CC37B402 for ; Thu, 4 Jan 2001 05:44:33 -0800 (PST) Received: from mailhost.inpharmatica.co.uk (euston.inpharmatica.co.uk [193.115.214.6]) by gallions-reach.inpharmatica.co.uk (8.9.3/8.9.3) with ESMTP id NAA28323; Thu, 4 Jan 2001 13:44:25 GMT (envelope-from m.seaman@inpharmatica.co.uk) Received: from w-hampstead.inpharmatica.co.uk (root@w-hampstead.inpharmatica.co.uk [192.168.122.87]) by mailhost.inpharmatica.co.uk (8.11.1/8.11.1) with ESMTP id f04DiNr42869; Thu, 4 Jan 2001 13:44:24 GMT (envelope-from m.seaman@inpharmatica.co.uk) Received: from inpharmatica.co.uk (matthew@localhost [127.0.0.1]) by w-hampstead.inpharmatica.co.uk (8.9.3/8.9.3) with ESMTP id NAA04459; Thu, 4 Jan 2001 13:44:23 GMT X-Authentication-Warning: w-hampstead.inpharmatica.co.uk: Host matthew@localhost [127.0.0.1] claimed to be inpharmatica.co.uk Sender: m.seaman@inpharmatica.co.uk Message-ID: <3A547E37.846A303F@inpharmatica.co.uk> Date: Thu, 04 Jan 2001 13:44:23 +0000 From: Matthew Seaman X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.17-desktop i586) X-Accept-Language: en-GB, en MIME-Version: 1.0 To: Bill Fumerola Cc: Chris BeHanna , FreeBSD-Stable Subject: Re: Roadmap for perl upgrades to STABLE? References: <200012260828.eBQ8SFF09546@gratis.grondar.za> <20001226231547.R72273@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > > On Wed, Dec 27, 2000 at 12:08:53AM -0500, Chris BeHanna wrote: > > > Not that I'm a fan of the GPL, but wouldn't importation of gmake > > into the toolchain that gets installed by default help this problem > > along enormously? > > What can it do that bmake can't? > Automatically generate dependencies and then apply them as part of a higher level target all in the same `make' invocation? ie. `make depend' can be a sub-target of `make all'. That's about the only feature of gmake I've ever used and missed having in BSD make. Matthew -- Certe, Toto, sentio nos in Kansate non iam adesse. Dr. Matthew Seaman, Inpharmatica Ltd, 60 Charlotte St, London, W1T 2NU Tel: +44 20 7631 4644 x229 Fax: +44 20 7631 4844 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 5:50:41 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 05:50:38 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from pobox.rwwa.com (pobox.rwwa.com [216.254.75.81]) by hub.freebsd.org (Postfix) with ESMTP id D1D1837B400 for ; Thu, 4 Jan 2001 05:50:37 -0800 (PST) Received: from rwwa.com (spooky.rwwa.com [192.124.97.13]) by pobox.rwwa.com (8.9.3/8.9.3) with ESMTP id JAA73970; Thu, 4 Jan 2001 09:09:21 -0500 (EST) (envelope-from witr@rwwa.com) Message-Id: <200101041409.JAA73970@pobox.rwwa.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Erich Zigler Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Threaded C++ Question In-Reply-To: Your message of "Tue, 02 Jan 2001 13:10:12 CST." <20010102131012.A1922@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Jan 2001 08:50:41 -0500 From: Robert Withrow Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG erichz@superhero.org said: :-In reading through the archives I have seen several emails regarding :-the problems people have experienced with MySQL, and Mozilla on 4.2 :-systems. Why aren't serious problems like this reported in the 4.2 errata? (The term I've seen used here is "completely broken" for C++ threading.) Why even *have* an errata if, as seems to be the case, RELEASE users are expected to scan through zillions of messages in these mailing lists to get the information that naive people like me would expect to get in an errata listing? I propose that the following be added to the 4.2 errata: "The use of multithreading with C++ programs is completely broken in this release. No fix or workaround is available at this time." --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 5:53:57 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 05:53:55 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id 5279337B400 for ; Thu, 4 Jan 2001 05:53:54 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id PAA02265; Thu, 4 Jan 2001 15:49:52 +0200 To: Matt DeLapp Subject: Re: 4.2-STABLE - Fatal trap 12 Message-ID: <978616192.3a547f8086cc0@webmail.harmonic.co.il> Date: Thu, 04 Jan 2001 15:49:52 +0200 (IST) From: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Matt DeLapp : > On Thu, 4 Jan 2001, Roman Shterenzon wrote: > > > I probably happends in one of the modules. > > Please send the output of kldstat command. > > Also, try to "add-symbol-file /modules/suspect.ko" > > I'm not sure about the command, since I don't know how the offsets > will be > > treated. You can take a look for example at: > > /usr/src/sys/modules/vinum/.gdbinit.vinum.paths > > matt@worf: {101} kldstat > Id Refs Address Size Name > 1 1 0xc0100000 2a329c kernel > > > I'll take a look at the example. Thanks. You don't need to. It seems that there's only kernel loaded. That means that the return address was overwritten I guess. As you can see, the backtrace is resolved to the certain depth and not more. > Matt > --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 5:57: 6 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 05:57:05 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id C712A37B400 for ; Thu, 4 Jan 2001 05:57:04 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id B9B7C315F; Thu, 4 Jan 2001 13:56:54 +0000 (GMT) Date: Thu, 4 Jan 2001 13:56:54 +0000 From: Josef Karthauser To: Greg Lehey Cc: Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? Message-ID: <20010104135654.F481@tao.org.uk> Mail-Followup-To: Josef Karthauser , Greg Lehey , Thomas Seck , freebsd-stable@FreeBSD.ORG References: <20010102230107.A559@basildon.homerun> <20010103102943.A770@tao.org.uk> <20010103214829.X4336@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010103214829.X4336@wantadilla.lemis.com>; from grog@lemis.com on Wed, Jan 03, 2001 at 09:48:29PM +1030 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 09:48:29PM +1030, Greg Lehey wrote: > > > > As far as I'm aware there are no problems using vinum for raid 0. > > > > As far as I understand from Greg he's not aware of many people who > > are having problems with raid 5. > > Probably. If you know of somebody I don't know of, please let me > know. I know of two other parties who were having trouble. They've both moved away to other solutions - one moved to linux :(. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 6:43:55 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 06:43:53 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from apollo.retec.net (apollo.retec.net [207.99.22.10]) by hub.freebsd.org (Postfix) with ESMTP id 7C0CF37B400; Thu, 4 Jan 2001 06:43:52 -0800 (PST) Received: from newken (dhcp113.retec.net [207.99.22.113]) by apollo.retec.net (8.9.3/8.9.0) with SMTP id JAA29941; Thu, 4 Jan 2001 09:35:27 -0500 (EST) Message-ID: <017401c0765c$5ea1ba60$711663cf@icarz.com> From: "Ken Menzel" To: "Max Khon" , "Daniel Eischen" Cc: , References: Subject: Re: C++ threaded programs Date: Thu, 4 Jan 2001 09:41:05 -0500 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Max, did you commit your patch to current or stable? Did you decide not to commit it? I did not see the commit in stable yet. I saw David Obrien's patch, but was too busy to try it yesterday. But I am now confused as to who is going to commit the/a/some fix! Is there a specific person who is the threads lib maintainer? I will try David's patch as well. I will do that anyway as I have a busy test machine I can put it on. Main comment without a patch MySQL segfaults after a short period. With your patch it runs fine! I'm going to try David's and get back to him later today. I want to thank everyone on this list for posting patches quickly and not upsetting the -stable with commits that haven't been well tested. The only reason I read this list is to watch for problems and patches! And the spirit of cooperation is very high, Thanks max, and thanks david. Ken ----------------------------------------------------- Ken Menzel ICQ# 9325188 www.icarz.com kenm@icarz.com ----- Original Message ----- From: "Max Khon" To: "Daniel Eischen" Cc: ; Sent: Wednesday, January 03, 2001 3:03 PM Subject: Re: C++ threaded programs > hi, there! > > On Wed, 3 Jan 2001, Daniel Eischen wrote: > > > > > Can you tell me what do you plan on "C++ threaded programs > > > > segfault" issue? > > > > > > Still fixing issues. > > > Compiling -static is broken with my latest patch. > > > Dan and I have a 2nd patch we are reviewing and testing. > > > > BTW, it passes all my tests. If it passes all yours, I'd say > > commit it. > > this patch differs from my patch only in a.out compatibility bits and > -fpic vs. -fPIC flags when compiling libgcc.a. So I am all for committing > it (sorry really have no time to rebuild world one more time) > > /fjoe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 6:56:23 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 06:56:21 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id DE34437B698 for ; Thu, 4 Jan 2001 06:56:17 -0800 (PST) Received: (qmail 92802 invoked by uid 1003); 4 Jan 2001 14:56:13 -0000 Date: Thu, 4 Jan 2001 16:56:13 +0200 From: Neil Blakey-Milner To: Matthew Seaman Cc: Bill Fumerola , Chris BeHanna , FreeBSD-Stable Subject: Re: Roadmap for perl upgrades to STABLE? Message-ID: <20010104165613.A91031@mithrandr.moria.org> References: <200012260828.eBQ8SFF09546@gratis.grondar.za> <20001226231547.R72273@elvis.mu.org> <3A547E37.846A303F@inpharmatica.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A547E37.846A303F@inpharmatica.co.uk>; from m.seaman@inpharmatica.co.uk on Thu, Jan 04, 2001 at 01:44:23PM +0000 X-Operating-System: FreeBSD 4.1-STABLE i386 X-URL: http://mithrandr.moria.org/nbm/ Sender: nbm@rucus.ru.ac.za Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu 2001-01-04 (13:44), Matthew Seaman wrote: > Bill Fumerola wrote: > > > > On Wed, Dec 27, 2000 at 12:08:53AM -0500, Chris BeHanna wrote: > > > > > Not that I'm a fan of the GPL, but wouldn't importation of gmake > > > into the toolchain that gets installed by default help this problem > > > along enormously? > > > > What can it do that bmake can't? > > > > Automatically generate dependencies and then apply them as part of a higher > level target all in the same `make' invocation? ie. `make depend' can be a > sub-target of `make all'. That's about the only feature of gmake I've ever > used and missed having in BSD make. all: .depend ? (that is to say, that's what it sounds like, I'm probably not parsing what you mean properly.) Neil -- Neil Blakey-Milner nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 7:12: 9 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 07:12:03 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from www0q.netaddress.usa.net (www0q.netaddress.usa.net [204.68.24.46]) by hub.freebsd.org (Postfix) with SMTP id BDFBE37B402 for ; Thu, 4 Jan 2001 07:12:02 -0800 (PST) Received: (qmail 8443 invoked by uid 60001); 4 Jan 2001 15:11:56 -0000 Message-ID: <20010104151156.8442.qmail@www0q.netaddress.usa.net> Received: from 204.68.24.46 by www0q for [64.40.199.178] via web-mailer(34FM.0700.4B.01) on Thu Jan 4 15:11:56 GMT 2001 Date: 4 Jan 01 10:11:56 EST From: Umesh Kumar To: freebsd-stable@freebsd.org Subject: NFS Server on 4.2 Stable X-Mailer: USANET web-mailer (34FM.0700.4B.01) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have been trying to run an NFS server on my 4.2 Stable machine but the = NFS server capability refuses to start. In rc.conf I have: portmap_enable=3D"YES" nfs_server_enable=3D"YES" But on reboot, kernel gives the message: Jan 2 19:39:13 topaz nfsd:[107]: can't register with udp portmap and mountd times out. Consequently the NFS server is never enabled :-( The machine I am trying to enable 4.2Stable is a web/email server machine= and all interfaces are working properly and pinging is also successful. The ifconfig -a output is as follows: dc0: flags=3D8843 mtu 1500 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::2a0:ccff:fe5a:f411%dc0 prefixlen 64 scopeid 0x1 ether 00:a0:cc:5a:f4:11 media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP none lp0: flags=3D8810 mtu 1500 lo0: flags=3D8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xffffff00 ppp0: flags=3D8010 mtu 1500 sl0: flags=3Dc010 mtu 552 faith0: flags=3D8000 mtu 1500 gif0: flags=3D8010 mtu 1280 gif1: flags=3D8010 mtu 1280 gif2: flags=3D8010 mtu 1280 gif3: flags=3D8010 mtu 1280 ----------------------------------------------------------------- I looked up similar problems in the mail archives of this and freebsd-questions, but I could not find a solution. Sorry if this is a repetition. Thanks, Umesh PS: I am not subscribed to this list, so it will great if you CC'ed me on= your replies. ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=3D= 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 7:34:38 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 07:34:31 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from gallions-reach.inpharmatica.co.uk (gallions-reach.inpharmatica.co.uk [193.115.214.5]) by hub.freebsd.org (Postfix) with ESMTP id 4313837B402 for ; Thu, 4 Jan 2001 07:34:30 -0800 (PST) Received: from mailhost.inpharmatica.co.uk (euston.inpharmatica.co.uk [193.115.214.6]) by gallions-reach.inpharmatica.co.uk (8.9.3/8.9.3) with ESMTP id PAA29226; Thu, 4 Jan 2001 15:34:18 GMT (envelope-from m.seaman@inpharmatica.co.uk) Received: from w-hampstead.inpharmatica.co.uk (root@w-hampstead.inpharmatica.co.uk [192.168.122.87]) by mailhost.inpharmatica.co.uk (8.11.1/8.11.1) with ESMTP id f04FYHr44704; Thu, 4 Jan 2001 15:34:18 GMT (envelope-from m.seaman@inpharmatica.co.uk) Received: from inpharmatica.co.uk (matthew@localhost [127.0.0.1]) by w-hampstead.inpharmatica.co.uk (8.9.3/8.9.3) with ESMTP id PAA04531; Thu, 4 Jan 2001 15:34:17 GMT X-Authentication-Warning: w-hampstead.inpharmatica.co.uk: Host matthew@localhost [127.0.0.1] claimed to be inpharmatica.co.uk Sender: m.seaman@inpharmatica.co.uk Message-ID: <3A5497F9.728D6CA@inpharmatica.co.uk> Date: Thu, 04 Jan 2001 15:34:17 +0000 From: Matthew Seaman X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.17-desktop i586) X-Accept-Language: en-GB, en MIME-Version: 1.0 To: Neil Blakey-Milner Cc: Bill Fumerola , Chris BeHanna , FreeBSD-Stable Subject: Re: Roadmap for perl upgrades to STABLE? References: <200012260828.eBQ8SFF09546@gratis.grondar.za> <20001226231547.R72273@elvis.mu.org> <3A547E37.846A303F@inpharmatica.co.uk> <20010104165613.A91031@mithrandr.moria.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neil Blakey-Milner wrote: > > On Thu 2001-01-04 (13:44), Matthew Seaman wrote: > > Bill Fumerola wrote: > > > > > > On Wed, Dec 27, 2000 at 12:08:53AM -0500, Chris BeHanna wrote: > > > > > > > Not that I'm a fan of the GPL, but wouldn't importation of gmake > > > > into the toolchain that gets installed by default help this problem > > > > along enormously? > > > > > > What can it do that bmake can't? > > > > > > > Automatically generate dependencies and then apply them as part of a higher > > level target all in the same `make' invocation? ie. `make depend' can be a > > sub-target of `make all'. That's about the only feature of gmake I've ever > > used and missed having in BSD make. > > all: .depend ? > > (that is to say, that's what it sounds like, I'm probably not parsing > what you mean properly.) Um... no. I don't think I explained myself clearly enough. The GNU make info page says it like this: > Generating Prerequisites Automatically > ====================================== > [talking about the use of `cc -M file.c'...] > > With old `make' programs, it was traditional practice to use this > compiler feature to generate prerequisites on demand with a command like > `make depend'. That command would create a file `depend' containing > all the automatically-generated prerequisites; then the makefile could > use `include' to read them in (*note Include::). > > In GNU `make', the feature of remaking makefiles makes this practice > obsolete--you need never tell `make' explicitly to regenerate the > prerequisites, because it always regenerates any makefile that is out > of date. *Note Remaking Makefiles::. and later on: > How Makefiles Are Remade > ======================== > > Sometimes makefiles can be remade from other files, such as RCS or > SCCS files. If a makefile can be remade from other files, you probably > want `make' to get an up-to-date version of the makefile to read in. > > To this end, after reading in all makefiles, `make' will consider > each as a goal target and attempt to update it. If a makefile has a > rule which says how to update it (found either in that very makefile or > in another one) or if an implicit rule applies to it (*note Using > Implicit Rules: Implicit Rules.), it will be updated if necessary. > After all makefiles have been checked, if any have actually been > changed, `make' starts with a clean slate and reads all the makefiles > over again. (It will also attempt to update each of them over again, > but normally this will not change them again, since they are already up > to date.) Matthew -- Certe, Toto, sentio nos in Kansate non iam adesse. Dr. Matthew Seaman, Inpharmatica Ltd, 60 Charlotte St, London, W1T 2NU Tel: +44 20 7631 4644 x229 Fax: +44 20 7631 4844 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 8: 3:20 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 08:03:18 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from yertle.kciLink.com (yertle.kciLink.com [208.184.13.195]) by hub.freebsd.org (Postfix) with ESMTP id 3605737B400 for ; Thu, 4 Jan 2001 08:03:18 -0800 (PST) Received: from onceler.kciLink.com (onceler.kciLink.com [208.184.13.196]) by yertle.kciLink.com (Postfix) with ESMTP id 504F42E440 for ; Thu, 4 Jan 2001 11:03:17 -0500 (EST) Received: (from khera@localhost) by onceler.kciLink.com (8.11.1/8.11.1) id f04G3HR00345; Thu, 4 Jan 2001 11:03:17 -0500 (EST) (envelope-from khera) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14932.40645.130709.857043@onceler.kciLink.com> Date: Thu, 4 Jan 2001 11:03:17 -0500 To: stable@FreeBSD.ORG Subject: Re: kldload: Exec format error, is 4.2 problem? In-Reply-To: <200101040528.f045SOI05021@henry.cs.adfa.edu.au> References: <200101040528.f045SOI05021@henry.cs.adfa.edu.au> X-Mailer: VM 6.88 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "WT" == Warren Toomey writes: WT> ld -Bshareable -o vmmon_up.ko setdef0.o vmmon_up.kld setdef1.o linux WT> By commenting out this flag, the file `linux' isn't used, and the module WT> can then be loaded by kldload. Also, vmware appears to work fine. Do you comment it out on both vmware2 modules and rtc module or just one of them? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 8:17: 2 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 08:16:58 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id A417137B404 for ; Thu, 4 Jan 2001 08:16:57 -0800 (PST) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id f04GGvf27324 for ; Thu, 4 Jan 2001 08:16:57 -0800 (PST) Received: from pau-amma.whistle.com( 207.76.205.64) by whistle.com via smap (V2.0) id xma027321; Thu, 4 Jan 2001 08:16:54 -0800 Received: (from dhw@localhost) by pau-amma.whistle.com (8.11.1/8.11.1) id f04GGsh72194 for stable@FreeBSD.ORG; Thu, 4 Jan 2001 08:16:54 -0800 (PST) Date: Thu, 4 Jan 2001 08:16:54 -0800 (PST) From: David Wolfskill Message-Id: <200101041616.f04GGsh72194@pau-amma.whistle.com> Subject: make vs. gmake (was: Re: Roadmap for perl upgrades to STABLE?) Cc: stable@FreeBSD.ORG In-Reply-To: <20001226231547.R72273@elvis.mu.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Tue, 26 Dec 2000 23:15:48 -0600 >From: Bill Fumerola >On Wed, Dec 27, 2000 at 12:08:53AM -0500, Chris BeHanna wrote: >> Not that I'm a fan of the GPL, but wouldn't importation of gmake >> into the toolchain that gets installed by default help this problem >> along enormously? >What can it do that bmake can't? Compile amanda 2.4.2. :-( [Ref. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=23328 -- seems that some Makefiles created by automake (which the amanda folks use) get created in a way that cause our make to behave in unexpected ways. I was able to generate a simpler test case that re-creates the problem (and it's in the PR), but have no fix, nor is it likely I will be able to devote the time required to become familiar enough with make's internals to get much of a clue anytime soon, unfortunately. I expect to be able to help test, though, and am quite willing to do that.] Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 8:53:29 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 08:53:27 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id D28D737B400 for ; Thu, 4 Jan 2001 08:53:26 -0800 (PST) Received: (qmail 46618 invoked from network); 4 Jan 2001 16:53:25 -0000 Received: from unknown (HELO prydn.tacni.net) (204.155.159.37) by 216.178.136.168 with SMTP; 4 Jan 2001 16:53:25 -0000 Received: (qmail 46143 invoked by uid 1001); 4 Jan 2001 16:53:26 -0000 Date: Thu, 4 Jan 2001 10:53:26 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Re: C++ threaded programs Message-ID: <20010104105326.A46062@superhero.org> References: <20010103103755.A62189@dragon.nuxi.com> <20010103212150.A43624@superhero.org> <20010104012018.B67473@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: <20010104012018.B67473@dragon.nuxi.com>; from TrimYourCc@NUXI.com on Thu, Jan 04, 2001 at 01:20:18AM -0800 X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: needo@prydn.tacni.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 01:20:18AM -0800, David O'Brien wrote: > > I applied your patch, rebuilt my world. > I fail to see you say my app filed on a *stock* world, and in these > way(s). Thus if I don't know what you're starting with, this feedback > isn't very helpful. My apologies, it was late, and I didnt get the message on what feedback you wanted till 12 hours after I posted the results of my test. Building with a stock world, I get the exact same cores and backtraces that I do after your patch. -- Erich Zigler If I worked as much as others, I would do as little as they. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 9:37:18 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 09:37:13 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id C0D4737B400 for ; Thu, 4 Jan 2001 09:37:12 -0800 (PST) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.1/8.11.0) with ESMTP id f04HevQ01535 for ; Thu, 4 Jan 2001 18:40:57 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Thu, 4 Jan 2001 18:40:57 +0100 (CET) From: "O. Hartmann" To: freebsd-stable@freebsd.org Subject: Still have a problem with make world ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, in spite of being overaged ... I still have this stupid problem; after starting a make buildworld compiler fails on of our machines: ------------ Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: Platform: osname=freebsd, osvers=4.0-current, archname=i386-freebsd name='FreeBSD freefall.FreeBSD.org 4.0-current FreeBSD 4.0-current #0: $Date$' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='', gccversion=2.95.2 19991024 (release) cppflags='' ccflags ='' stdchar='char', d_stdstdio=undef, usevfork=true intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='cc', ldflags ='-Wl,-E -lperl -lm ' libpth=/usr/lib libs=-lm -lc -lcrypt libc=, so=so, useshrplib=true, libperl=libperl.so.3 Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' -Wl,-R/usr/lib' cccdlflags='-DPIC -fpic', lddlflags='-Wl,-E -shared -lperl -lm ' rm -f .depend mkdep -f .depend -a -I/usr/vol1/src/gnu/usr.bin/perl/x2p/a2pl/../../../../../contrib/perl5/x2p -I/usr/obj/usr/vol1/src/gnu/usr.bin/perl/x2p/a2pl -I/usr/obj/usr/vol1/src/gnu/usr.bin/perl/x2p/a2pl/temp -I/usr/obj/usr/vol1/src/i386/usr/include /usr/vol1/src/gnu/usr.bin/perl/x2p/a2pl/../../../../../contrib/perl5/x2p/a2p.c /usr/vol1/src/gnu/usr.bin/perl/x2p/a2pl/../../../../../contrib/perl5/x2p/hash.c /usr/vol1/src/gnu/usr.bin/perl/x2p/a2pl/../../../../../contrib/perl5/x2p/str.c /usr/vol1/src/gnu/usr.bin/perl/x2p/a2pl/../../../../../contrib/perl5/x2p/util.c /usr/vol1/src/gnu/usr.bin/perl/x2p/a2pl/../../../../../contrib/perl5/x2p/walk.c cd /usr/vol1/src/gnu/usr.bin/perl/x2p/a2pl; make _EXTRADEPEND echo a2p: /usr/obj/usr/vol1/src/i386/usr/lib/libc.a >> .depend ===> gnu/usr.bin/perl/x2p/s2pl ===> gnu/usr.bin/perl/x2p/find2pl ===> gnu/usr.sbin 1 error *** Error code 2 1 error *** Error code 2 1 error ---------------- I read prior about a perl-failure in this manner ... For this I deleted /usr/obj and and cleaned /usr/src and got the sources again ... Can anybody help? Thanks in advance, Oliver - MfG O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver-Abteilung des IPA IT Netz- und Systembetreuung Johannes Gutenberg-Universitaet Mainz Becherweg 21 D-55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 10:25: 8 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 10:25:06 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.com (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id A79E737B400 for ; Thu, 4 Jan 2001 10:25:05 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.com (Postfix) with ESMTP id 51248177E9F for ; Thu, 4 Jan 2001 12:29:22 -0600 (CST) Message-ID: <009401c0767c$3e096800$931576d8@inethouston.net> From: "David W. Chapman Jr." To: References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> <20010103103948.A62250@dragon.nuxi.com> <00e201c075be$8a500570$524c8486@jking> <00d601c075bf$643e9440$931576d8@inethouston.net> <20010104012249.C67473@dragon.nuxi.com> Subject: Re: Threaded C++ Question Date: Thu, 4 Jan 2001 12:29:15 -0600 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cd /usr/ports/www/mozilla && make install then run "mozilla" then it core dumps, but this was about a week ago and haven't tried since. ----- Original Message ----- From: "David O'Brien" To: "David W. Chapman Jr." Cc: "Jim King" ; Sent: Thursday, January 04, 2001 3:22 AM Subject: Re: Threaded C++ Question > On Wed, Jan 03, 2001 at 01:57:24PM -0600, David W. Chapman Jr. wrote: > > That was the same problem I encountered > > (*sarcasm*) Well that was very helpful. How about telling me how *_I_* > can experience it? > > I'm about to give up and just drop fixing this as no one is able to give > me any feedback. > > -- > -- David (obrien@FreeBSD.org) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 10:47:55 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 10:47:52 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 97C9837B402 for ; Thu, 4 Jan 2001 10:47:48 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA96112; Thu, 4 Jan 2001 10:47:43 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f04IleB52577; Thu, 4 Jan 2001 10:47:40 -0800 (PST) (envelope-from obrien) Date: Thu, 4 Jan 2001 10:47:40 -0800 From: "David O'Brien" To: Ken Menzel Cc: Max Khon , Daniel Eischen , stable@FreeBSD.ORG Subject: Re: C++ threaded programs Message-ID: <20010104104740.D52458@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <017401c0765c$5ea1ba60$711663cf@icarz.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <017401c0765c$5ea1ba60$711663cf@icarz.com>; from kenm@icarz.com on Thu, Jan 04, 2001 at 09:41:05AM -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: obrien@NUXI.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 09:41:05AM -0500, Ken Menzel wrote: > Max, did you commit your patch to current or stable? Did you decide > not to commit it? Max is not a committer, and there were also some minor problems with the patch. Anyway, such changes have to go into -CURRENT first. > I did not see the commit in stable yet. I saw David Obrien's patch, > but was too busy to try it yesterday. But I am now confused as to who > is going to commit the/a/some fix! I am, as I said to use my patch over his (and the compiler is my responsibility). Enjoy! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 12: 0:56 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 12:00:53 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id 5446E37B400 for ; Thu, 4 Jan 2001 12:00:53 -0800 (PST) Received: (qmail 21564 invoked from network); 4 Jan 2001 20:00:52 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 4 Jan 2001 20:00:52 -0000 Sender: robin@FreeBSD.ORG Message-ID: <3A54D65C.B51CCCBE@gactr.uga.edu> Date: Thu, 04 Jan 2001 15:00:28 -0500 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: 4.2-stable buildworld problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok... i totalled scrapped my supfile /usr/src and /usr/obj and started all over again with a fresh stable-supfile (src-all), as i haven't been able to buildworld since sometime before christmas. buildworld plods along until: ===> gnu/usr.bin/groff/devX100 make: don't know how to make S. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error this is with the latest cvs. ideas? -- ------------------------------------ Robin P. Blanchard Network Engineering & Support Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 12:49:20 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 12:49:18 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A4CCA37B400 for ; Thu, 4 Jan 2001 12:49:17 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 4 Jan 2001 20:49:16 +0000 (GMT) Date: Thu, 4 Jan 2001 20:49:16 +0000 From: David Malone To: Umesh Kumar Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS Server on 4.2 Stable Message-ID: <20010104204916.A40033@walton.maths.tcd.ie> References: <20010104151156.8442.qmail@www0q.netaddress.usa.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010104151156.8442.qmail@www0q.netaddress.usa.net>; from economix@usa.net on Thu, Jan 04, 2001 at 10:11:56AM -0500 Sender: dwmalone@maths.tcd.ie Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 10:11:56AM -0500, Umesh Kumar wrote: > But on reboot, kernel gives the message: > Jan 2 19:39:13 topaz nfsd:[107]: can't register with udp portmap Might you have something in /etc/hosts.allow which stops people talking to the portmapper? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 13:19:15 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 13:19:10 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8600237B400 for ; Thu, 4 Jan 2001 13:19:10 -0800 (PST) Received: from mail.newst.irs.ru (newst.irs.ru [212.164.94.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 909EC6E3367 for ; Thu, 4 Jan 2001 13:19:08 -0800 (PST) Received: from lark.nsk.bsgdesign.com (lark.nsk.bsgdesign.com [192.168.3.21]) by mail.newst.irs.ru (8.11.1/8.11.0) with ESMTP id f04LGQp96563 for ; Fri, 5 Jan 2001 03:16:27 +0600 (NOVT) (envelope-from fjoe@newst.net) Date: Fri, 5 Jan 2001 03:16:08 +0600 (NOVT) From: Max Khon X-Sender: fjoe@localhost To: stable@freebsd.org Subject: ad0: WRITE command timeout tag=0 serv=0 - resetting Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-551075908-978642968=:62768" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-551075908-978642968=:62768 Content-Type: TEXT/PLAIN; charset=US-ASCII hi, there! Today I have installed latest -stable on a machine where previously I had 4.1-RELEASE working fine. after make installkernel/reboot I have got the following messages on console: ad0: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad0: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done The machine had cdrom drive: acd0: CDROM at ata0-slave using PIO4 After I have disconnected cdrom drive the machine booted ok. dmesg (after successful boot, without cdrom connected) attached. Unfortunately I do not have access to the console (the machine is located on another continent). /fjoe --0-551075908-978642968=:62768 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=dmesg Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=dmesg Tm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogQ29weXJpZ2h0IChjKSAx OTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4NCk5vdiAgMyAxMzowOTox OSBsYXJrIC9rZXJuZWw6IENvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4 MywgMTk4NiwgMTk4OCwgMTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0K Tm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogVGhlIFJlZ2VudHMgb2Yg dGhlIFVuaXZlcnNpdHkgb2YgQ2FsaWZvcm5pYS4gQWxsIHJpZ2h0cyByZXNl cnZlZC4NCk5vdiAgMyAxMzowOToxOSBsYXJrIC9rZXJuZWw6IEZyZWVCU0Qg NC4yLUJFVEEgIzA6IEZyaSBOb3YgIDMgMTI6NTI6MDEgTk9WVCAyMDAwDQpO b3YgIDMgMTM6MDk6MTkgbGFyayAva2VybmVsOiBmam9lQGFsZi5uc2suYnNn ZGVzaWduLmNvbTovdXNyL29iai91c3Ivc3JjL3N5cy9hbGYNCk5vdiAgMyAx MzowOToxOSBsYXJrIC9rZXJuZWw6IFRpbWVjb3VudGVyICJpODI1NCIgIGZy ZXF1ZW5jeSAxMTkzMjA3IEh6DQpOb3YgIDMgMTM6MDk6MTkgbGFyayAva2Vy bmVsOiBDUFU6IFBlbnRpdW0gSUkvUGVudGl1bSBJSSBYZW9uL0NlbGVyb24g KDUyNS4wMS1NSHogNjg2LWNsYXNzIENQVSkNCk5vdiAgMyAxMzowOToxOSBs YXJrIC9rZXJuZWw6IE9yaWdpbiA9ICJHZW51aW5lSW50ZWwiICBJZCA9IDB4 NjY1ICBTdGVwcGluZyA9IDUNCk5vdiAgMyAxMzowOToxOSBsYXJrIC9rZXJu ZWw6IEZlYXR1cmVzPTB4MTgzZjlmZjxGUFUsVk1FLERFLFBTRSxUU0MsTVNS LFBBRSxNQ0UsQ1g4LFNFUCxNVFJSLFBHRSxNQ0EsQ01PVixQQVQsUFNFMzYs TU1YLEZYU1I+DQpOb3YgIDMgMTM6MDk6MTkgbGFyayAva2VybmVsOiByZWFs IG1lbW9yeSAgPSAxMzQyMDEzNDQgKDEzMTA1NksgYnl0ZXMpDQpOb3YgIDMg MTM6MDk6MTkgbGFyayAva2VybmVsOiBhdmFpbCBtZW1vcnkgPSAxMjY5MTA0 NjQgKDEyMzkzNksgYnl0ZXMpDQpOb3YgIDMgMTM6MDk6MTkgbGFyayAva2Vy bmVsOiBQcmVsb2FkZWQgZWxmIGtlcm5lbCAia2VybmVsIiBhdCAweGMwMzNm MDAwLg0KTm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogUHJlbG9hZGVk IGVsZiBtb2R1bGUgIm5mcy5rbyIgYXQgMHhjMDMzZjA5Yy4NCk5vdiAgMyAx MzowOToxOSBsYXJrIC9rZXJuZWw6IFBlbnRpdW0gUHJvIE1UUlIgc3VwcG9y dCBlbmFibGVkDQpOb3YgIDMgMTM6MDk6MTkgbGFyayAva2VybmVsOiBhcG0w OiA8QVBNIEJJT1M+IG9uIG1vdGhlcmJvYXJkDQpOb3YgIDMgMTM6MDk6MTkg bGFyayAva2VybmVsOiBhcG06IGZvdW5kIEFQTSBCSU9TIHYxLjIsIGNvbm5l Y3RlZCBhdCB2MS4yDQpOb3YgIDMgMTM6MDk6MTkgbGFyayAva2VybmVsOiBu cHgwOiA8bWF0aCBwcm9jZXNzb3I+IG9uIG1vdGhlcmJvYXJkDQpOb3YgIDMg MTM6MDk6MTkgbGFyayAva2VybmVsOiBucHgwOiBJTlQgMTYgaW50ZXJmYWNl DQpOb3YgIDMgMTM6MDk6MTkgbGFyayAva2VybmVsOiBwY2liMDogPEludGVs IDgyNDQzQlggKDQ0MCBCWCkgaG9zdCB0byBQQ0kgYnJpZGdlPiBvbiBtb3Ro ZXJib2FyZA0KTm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogcGNpMDog PFBDSSBidXM+IG9uIHBjaWIwDQpOb3YgIDMgMTM6MDk6MTkgbGFyayAva2Vy bmVsOiBwY2liMTogPEludGVsIDgyNDQzQlggKDQ0MCBCWCkgUENJLVBDSSAo QUdQKSBicmlkZ2U+IGF0IGRldmljZSAxLjAgb24gcGNpMA0KTm92ICAzIDEz OjA5OjE5IGxhcmsgL2tlcm5lbDogcGNpMTogPFBDSSBidXM+IG9uIHBjaWIx DQpOb3YgIDMgMTM6MDk6MTkgbGFyayAva2VybmVsOiBwY2kxOiA8QVRJIE1h Y2g2NC1HTSBncmFwaGljcyBhY2NlbGVyYXRvcj4gYXQgMC4wIGlycSAxMA0K Tm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogaXNhYjA6IDxJbnRlbCA4 MjM3MUFCIFBDSSB0byBJU0EgYnJpZGdlPiBhdCBkZXZpY2UgNC4wIG9uIHBj aTANCk5vdiAgMyAxMzowOToxOSBsYXJrIC9rZXJuZWw6IGlzYTA6IDxJU0Eg YnVzPiBvbiBpc2FiMA0KTm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDog YXRhcGNpMDogPEludGVsIFBJSVg0IEFUQTMzIGNvbnRyb2xsZXI+IHBvcnQg MHhiODAwLTB4YjgwZiBhdCBkZXZpY2UgNC4xIG9uIHBjaTANCk5vdiAgMyAx MzowOToxOSBsYXJrIC9rZXJuZWw6IGF0YTA6IGF0IDB4MWYwIGlycSAxNCBv biBhdGFwY2kwDQpOb3YgIDMgMTM6MDk6MTkgbGFyayAva2VybmVsOiBwY2kw OiA8SW50ZWwgODIzNzFBQi9FQiAoUElJWDQpIFVTQiBjb250cm9sbGVyPiBh dCA0LjIgaXJxIDkNCk5vdiAgMyAxMzowOToxOSBsYXJrIC9rZXJuZWw6IGNo aXAxOiA8SW50ZWwgODIzNzFBQiBQb3dlciBtYW5hZ2VtZW50IGNvbnRyb2xs ZXI+IHBvcnQgMHhlODAwLTB4ZTgwZiBhdCBkZXZpY2UgNC4zIG9uIHBjaTAN Ck5vdiAgMyAxMzowOToxOSBsYXJrIC9rZXJuZWw6IHBjaTA6IDx1bmtub3du IGNhcmQ+ICh2ZW5kb3I9MHgxMGI3LCBkZXY9MHg5MDU1KSBhdCAxMi4wIGly cSAxMA0KTm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogZmRjMDogPE5F QyA3MjA2NUIgb3IgY2xvbmU+IGF0IHBvcnQgMHgzZjAtMHgzZjUsMHgzZjcg aXJxIDYgZHJxIDIgb24gaXNhMA0KTm92ICAzIDEzOjA5OjE5IGxhcmsgL2tl cm5lbDogZmRjMDogRklGTyBlbmFibGVkLCA4IGJ5dGVzIHRocmVzaG9sZA0K Tm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogZmQwOiA8MTQ0MC1LQiAz LjUiIGRyaXZlPiBvbiBmZGMwIGRyaXZlIDANCk5vdiAgMyAxMzowOToxOSBs YXJrIC9rZXJuZWw6IGF0a2JkYzA6IDxLZXlib2FyZCBjb250cm9sbGVyIChp ODA0Mik+IGF0IHBvcnQgMHg2MCwweDY0IG9uIGlzYTANCk5vdiAgMyAxMzow OToxOSBsYXJrIC9rZXJuZWw6IHBzbTA6IDxQUy8yIE1vdXNlPiBpcnEgMTIg b24gYXRrYmRjMA0KTm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogcHNt MDogbW9kZWwgR2VuZXJpYyBQUy8yIG1vdXNlLCBkZXZpY2UgSUQgMA0KTm92 ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogYXRrYmQwOiA8QVQgS2V5Ym9h cmQ+IGZsYWdzIDB4MSBpcnEgMSBvbiBhdGtiZGMwDQpOb3YgIDMgMTM6MDk6 MTkgbGFyayAva2VybmVsOiBrYmQwIGF0IGF0a2JkMA0KTm92ICAzIDEzOjA5 OjE5IGxhcmsgL2tlcm5lbDogdmdhMDogPEdlbmVyaWMgSVNBIFZHQT4gYXQg cG9ydCAweDNjMC0weDNkZiBpb21lbSAweGEwMDAwLTB4YmZmZmYgb24gaXNh MA0KTm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogc2MwOiA8U3lzdGVt IGNvbnNvbGU+IGF0IGZsYWdzIDB4MTAwIG9uIGlzYTANCk5vdiAgMyAxMzow OToxOSBsYXJrIC9rZXJuZWw6IHNjMDogVkdBIDwxNiB2aXJ0dWFsIGNvbnNv bGVzLCBmbGFncz0weDMwMD4NCk5vdiAgMyAxMzowOToxOSBsYXJrIC9rZXJu ZWw6IHNpbzAgYXQgcG9ydCAweDNmOC0weDNmZiBpcnEgNCBmbGFncyAweDEw IG9uIGlzYTANCk5vdiAgMyAxMzowOToxOSBsYXJrIC9rZXJuZWw6IHNpbzA6 IHR5cGUgMTY1NTBBDQpOb3YgIDMgMTM6MDk6MTkgbGFyayAva2VybmVsOiBz aW8xIGF0IHBvcnQgMHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhMA0KTm92ICAz IDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogc2lvMTogdHlwZSAxNjU1MEENCk5v diAgMyAxMzowOToxOSBsYXJrIC9rZXJuZWw6IHBwYzA6IDxQYXJhbGxlbCBw b3J0PiBhdCBwb3J0IDB4Mzc4LTB4MzdmIGlycSA3IG9uIGlzYTANCk5vdiAg MyAxMzowOToxOSBsYXJrIC9rZXJuZWw6IHBwYzA6IEdlbmVyaWMgY2hpcHNl dCAoRVBQL05JQkJMRSkgaW4gQ09NUEFUSUJMRSBtb2RlDQpOb3YgIDMgMTM6 MDk6MTkgbGFyayAva2VybmVsOiBwcGkwOiA8UGFyYWxsZWwgSS9PPiBvbiBw cGJ1czANCk5vdiAgMyAxMzowOToxOSBsYXJrIC9rZXJuZWw6IGxwdDA6IDxQ cmludGVyPiBvbiBwcGJ1czANCk5vdiAgMyAxMzowOToxOSBsYXJrIC9rZXJu ZWw6IGxwdDA6IEludGVycnVwdC1kcml2ZW4gcG9ydA0KTm92ICAzIDEzOjA5 OjE5IGxhcmsgL2tlcm5lbDogcGxpcDA6IDxQTElQIG5ldHdvcmsgaW50ZXJm YWNlPiBvbiBwcGJ1czANCk5vdiAgMyAxMzowOToxOSBsYXJrIC9rZXJuZWw6 IHNiYzA6IDxFU1MgRVMxODY4PiBhdCBwb3J0IDB4MjIwLTB4MjJmLDB4Mzg4 LTB4MzhiLDB4MzMwLTB4MzMxIGlycSA1IGRycSAxLDAgb24gaXNhMA0KTm92 ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogcGNtMTogPEVTUyAxOHh4IERT UD4gb24gc2JjMA0KTm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogYWQw OiAxMDMwME1CIDxGVUpJVFNVIE1QRDMxMDhBVD4gWzIwOTI4LzE2LzYzXSBh dCBhdGEwLW1hc3RlciBVRE1BMzMNCk5vdiAgMyAxMzowOToxOSBsYXJrIC9r ZXJuZWw6IE1vdW50aW5nIHJvb3QgZnJvbSB1ZnM6L2Rldi9hZDBzMWENCk5v diAgMyAxMzowOToxOSBsYXJrIC9rZXJuZWw6IHhsMDogPDNDb20gM2M5MDVC LVRYIEZhc3QgRXRoZXJsaW5rIFhMPiBwb3J0IDB4YjAwMC0weGIwN2YgbWVt IDB4ZTUwMDAwMDAtMHhlNTAwMDA3ZiBpcnEgMTAgYXQgZGV2aWNlIDEyLjAg b24gcGNpMA0KTm92ICAzIDEzOjA5OjE5IGxhcmsgL2tlcm5lbDogeGwwOiBj b3VsZG4ndCBtYXAgaW50ZXJydXB0DQpOb3YgIDMgMTM6MDk6MTkgbGFyayAv a2VybmVsOiBkZXZpY2VfcHJvYmVfYW5kX2F0dGFjaDogeGwwIGF0dGFjaCBy ZXR1cm5lZCA2DQo= --0-551075908-978642968=:62768-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 13:32:41 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 13:32:38 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.newst.irs.ru (newst.irs.ru [212.164.94.1]) by hub.freebsd.org (Postfix) with ESMTP id 034A037B400 for ; Thu, 4 Jan 2001 13:32:37 -0800 (PST) Received: from lark.nsk.bsgdesign.com (lark.nsk.bsgdesign.com [192.168.3.21]) by mail.newst.irs.ru (8.11.1/8.11.0) with ESMTP id f04LWYp96970 for ; Fri, 5 Jan 2001 03:32:36 +0600 (NOVT) (envelope-from fjoe@newst.net) Date: Fri, 5 Jan 2001 03:32:15 +0600 (NOVT) From: Max Khon X-Sender: fjoe@localhost To: stable@FreeBSD.ORG Subject: Re: ad0: WRITE command timeout tag=0 serv=0 - resetting In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1953493086-978643935=:62768" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1953493086-978643935=:62768 Content-Type: TEXT/PLAIN; charset=US-ASCII hi, there! On Fri, 5 Jan 2001, Max Khon wrote: > Today I have installed latest -stable on a machine where previously I had > 4.1-RELEASE working fine. > > after make installkernel/reboot I have got the following messages on > console: > > ad0: WRITE command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done > ad0: WRITE command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done > > The machine had cdrom drive: > acd0: CDROM at ata0-slave using PIO4 > > After I have disconnected cdrom drive the machine booted ok. > dmesg (after successful boot, without cdrom connected) attached. > Unfortunately I do not have access to the console (the machine is located > on another continent). sorry, I have attached wrong dmesg. correct dmesg in attachement. /fjoe --0-1953493086-978643935=:62768 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=dmesg Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=dmesg Q29weXJpZ2h0IChjKSAxOTkyLTIwMDEgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwg MTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0KCVRoZSBSZWdlbnRzIG9m IHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCByaWdodHMgcmVz ZXJ2ZWQuDQpGcmVlQlNEIDQuMi1TVEFCTEUgIzA6IFRodSBKYW4gIDQgMTU6 NDQ6NTggRVNUIDIwMDENCiAgICBhZG1pbkBtczM0Lm1haS5uZXQ6L3Vzci9v YmovdXNyL3NyYy9zeXMvR0VORVJJQw0KVGltZWNvdW50ZXIgImk4MjU0IiAg ZnJlcXVlbmN5IDExOTMxODIgSHoNCkNQVTogQU1ELUs2KHRtKSAzRCBwcm9j ZXNzb3IgKDUwMS4xNC1NSHogNTg2LWNsYXNzIENQVSkNCiAgT3JpZ2luID0g IkF1dGhlbnRpY0FNRCIgIElkID0gMHg1OGMgIFN0ZXBwaW5nID0gMTINCiAg RmVhdHVyZXM9MHg4MDIxYmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixNQ0Us Q1g4LFBHRSxNTVg+DQogIEFNRCBGZWF0dXJlcz0weDgwMDAwODAwPFNZU0NB TEwsM0ROb3chPg0KcmVhbCBtZW1vcnkgID0gMTM0MjAxMzQ0ICgxMzEwNTZL IGJ5dGVzKQ0KYXZhaWwgbWVtb3J5ID0gMTI2MzYxNjAwICgxMjM0MDBLIGJ5 dGVzKQ0KUHJlbG9hZGVkIGVsZiBrZXJuZWwgImtlcm5lbCIgYXQgMHhjMDQz ODAwMC4NCks2LWZhbWlseSBNVFJSIHN1cHBvcnQgZW5hYmxlZCAoMiByZWdp c3RlcnMpDQptZDA6IE1hbGxvYyBkaXNrDQpucHgwOiA8bWF0aCBwcm9jZXNz b3I+IG9uIG1vdGhlcmJvYXJkDQpucHgwOiBJTlQgMTYgaW50ZXJmYWNlDQpw Y2liMDogPEFjZXJMYWJzIE0xNTQxIChBbGFkZGluLVYpIFBDSSBob3N0IGJy aWRnZT4gb24gbW90aGVyYm9hcmQNCnBjaTA6IDxQQ0kgYnVzPiBvbiBwY2li MA0KcGNpYjE6IDxBY2VyTGFicyBNNTI0MyBQQ0ktUENJIGJyaWRnZT4gYXQg ZGV2aWNlIDEuMCBvbiBwY2kwDQpwY2kxOiA8UENJIGJ1cz4gb24gcGNpYjEN CnBjaTE6IDxOVmlkaWEvU0dTLVRob21zb24gUml2YTEyOCBncmFwaGljcyBh Y2NlbGVyYXRvcj4gYXQgMC4wIGlycSAxMQ0KY2hpcDE6IDxBY2VyTGFicyBN MTV4MyBQb3dlciBNYW5hZ2VtZW50IFVuaXQ+IGF0IGRldmljZSAzLjAgb24g cGNpMA0KaXNhYjA6IDxBY2VyTGFicyBNMTUzMyBwb3J0YWJsZSBQQ0ktSVNB IGJyaWRnZT4gYXQgZGV2aWNlIDcuMCBvbiBwY2kwDQppc2EwOiA8SVNBIGJ1 cz4gb24gaXNhYjANCnhsMDogPDNDb20gM2M5MDVDLVRYIEZhc3QgRXRoZXJs aW5rIFhMPiBwb3J0IDB4ZDgwMC0weGQ4N2YgbWVtIDB4ZDYwMDAwMDAtMHhk NjAwMDA3ZiBpcnEgNSBhdCBkZXZpY2UgMTAuMCBvbiBwY2kwDQp4bDA6IEV0 aGVybmV0IGFkZHJlc3M6IDAwOjUwOmRhOjkyOmI4OmVhDQptaWlidXMwOiA8 TUlJIGJ1cz4gb24geGwwDQp4bHBoeTA6IDwzYzkwNUMgMTAvMTAwIGludGVy bmFsIFBIWT4gb24gbWlpYnVzMA0KeGxwaHkwOiAgMTBiYXNlVCwgMTBiYXNl VC1GRFgsIDEwMGJhc2VUWCwgMTAwYmFzZVRYLUZEWCwgYXV0bw0KYXRhcGNp MDogPEFjZXJMYWJzIEFsYWRkaW4gQVRBMzMgY29udHJvbGxlcj4gcG9ydCAw eGQ0MDAtMHhkNDBmIGlycSAwIGF0IGRldmljZSAxNS4wIG9uIHBjaTANCmF0 YTA6IGF0IDB4MWYwIGlycSAxNCBvbiBhdGFwY2kwDQpmZGMwOiA8TkVDIDcy MDY1QiBvciBjbG9uZT4gYXQgcG9ydCAweDNmMC0weDNmNSwweDNmNyBpcnEg NiBkcnEgMiBvbiBpc2EwDQphdGtiZGMwOiA8S2V5Ym9hcmQgY29udHJvbGxl ciAoaTgwNDIpPiBhdCBwb3J0IDB4NjAsMHg2NCBvbiBpc2EwDQphdGtiZDA6 IDxBVCBLZXlib2FyZD4gZmxhZ3MgMHgxIGlycSAxIG9uIGF0a2JkYzANCmti ZDAgYXQgYXRrYmQwDQpwc20wOiA8UFMvMiBNb3VzZT4gaXJxIDEyIG9uIGF0 a2JkYzANCnBzbTA6IG1vZGVsIEdlbmVyaWMgUFMvMiBtb3VzZSwgZGV2aWNl IElEIDANCnZnYTA6IDxHZW5lcmljIElTQSBWR0E+IGF0IHBvcnQgMHgzYzAt MHgzZGYgaW9tZW0gMHhhMDAwMC0weGJmZmZmIG9uIGlzYTANCnNjMDogPFN5 c3RlbSBjb25zb2xlPiBhdCBmbGFncyAweDEwMCBvbiBpc2EwDQpzYzA6IFZH QSA8MTYgdmlydHVhbCBjb25zb2xlcywgZmxhZ3M9MHgzMDA+DQpzaW8wOiBj b25maWd1cmVkIGlycSA0IG5vdCBpbiBiaXRtYXAgb2YgcHJvYmVkIGlycXMg MA0Kc2lvMCBhdCBwb3J0IDB4M2Y4LTB4M2ZmIGlycSA0IGZsYWdzIDB4MTAg b24gaXNhMA0Kc2lvMDogdHlwZSA4MjUwDQpzaW8xOiBjb25maWd1cmVkIGly cSAzIG5vdCBpbiBiaXRtYXAgb2YgcHJvYmVkIGlycXMgMA0KcHBjMDogcGFy YWxsZWwgcG9ydCBub3QgZm91bmQuDQphZDA6IDk3ODdNQiA8V0RDIFdEMTAy QUE+IFsxOTg4NS8xNi82M10gYXQgYXRhMC1tYXN0ZXIgVURNQTMzDQpNb3Vu dGluZyByb290IGZyb20gdWZzOi9kZXYvYWQwczFhDQo= --0-1953493086-978643935=:62768-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 13:57:11 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 13:57:08 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from nisser.com (c0039.upc-c.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 93F7737B400 for ; Thu, 4 Jan 2001 13:56:53 -0800 (PST) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id WAA79292; Thu, 4 Jan 2001 22:55:24 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A54F14C.70C55E78@nisser.com> Date: Thu, 04 Jan 2001 22:55:24 +0100 From: Roelof Osinga Organization: Nisser - Nr. 1 in Veiligheid X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: dxoch Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Vinum Question References: <3A5432C3.95A65586@escape.gr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dxoch wrote: > > I am using RAID-1 Vinum volumes, without any problem till now, but i > never succeed to use a > Vinum volume as a root partition. Is it possible, and how? > (I hope this is the place to ask something like that) Last I looked it was not possible. Forgot the reason why, though. If interested then try the mailarchive, ought to be in there somewhere. Roelof -- Nisser home -- http://www.Nisser.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 14:40: 4 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 14:40:00 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.newst.irs.ru (newst.irs.ru [212.164.94.1]) by hub.freebsd.org (Postfix) with ESMTP id 4DFE737B400; Thu, 4 Jan 2001 14:39:59 -0800 (PST) Received: from lark.nsk.bsgdesign.com (lark.nsk.bsgdesign.com [192.168.3.21]) by mail.newst.irs.ru (8.11.1/8.11.0) with ESMTP id f04Mdtp98894; Fri, 5 Jan 2001 04:39:57 +0600 (NOVT) (envelope-from fjoe@newst.net) Date: Fri, 5 Jan 2001 04:39:37 +0600 (NOVT) From: Max Khon X-Sender: fjoe@localhost To: stable@freebsd.org Cc: obrien@freebsd.org Subject: C++ and threads Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! I have cvsupped to latest -stable and rebuilt world with latest patches posted by David O'Brien to freebsd-stable@ mailing list. I have rebuilt all my tests -- ACE wrappers, test program from PR/23252 (segfault in C++ multithreading program), test program from PR/21983 (linking shared objects with libgcc.a) All tests run just fine. I have also built mozilla from ports (patch-mi rev 1.2, patch-qt rev 1.3, without patch-an -- i.e. without -lgcc_r changes) -- runs just fine /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 14:52:16 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 14:52:13 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.orem.verio.net (gatekeeper.orem.verio.net [192.41.0.8]) by hub.freebsd.org (Postfix) with ESMTP id 8333D37B402 for ; Thu, 4 Jan 2001 14:52:13 -0800 (PST) Received: from mx.dmz.orem.verio.net (mx.dmz.orem.verio.net [10.1.1.10]) by gatekeeper.orem.verio.net (Postfix) with ESMTP id 3617E3BF116 for ; Thu, 4 Jan 2001 15:52:13 -0700 (MST) Received: from vespa.dmz.orem.verio.net (vespa.dmz.orem.verio.net [10.1.1.59]) by mx.dmz.orem.verio.net (8.11.1/8.11.1) with ESMTP id f04MqCn25893; Thu, 4 Jan 2001 15:52:12 -0700 (MST) (envelope-from fclift@verio.net) Date: Thu, 4 Jan 2001 16:14:24 -0700 (MST) From: Fred Clift X-Sender: fred@vespa.dmz.orem.verio.net To: Roelof Osinga Cc: dxoch , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum Question In-Reply-To: <3A54F14C.70C55E78@nisser.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 Jan 2001, Roelof Osinga wrote: >> dxoch wrote: >> never succeed to use a > Vinum volume as a root >> partition. Is it possible, and how? > Last I looked it was not possible. Forgot the reason why, though. > If interested then try the mailarchive, ought to be in there somewhere. From what I understand, the boot-loader doesn't grok vinum partitions. If you wanted to get really complicated, you could boot from an MD image for your root file-system and re-arrange things so that all the stuff that needs to be dynamic lives on a vinum partition and just use the MD image for booting. Then you're fairly insulated from disk-failure -- root is in memory and /usr + your other data is mirrored. It is a hassle though. Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 15: 9:39 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 15:09:37 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158]) by hub.freebsd.org (Postfix) with ESMTP id C17FE37B400 for ; Thu, 4 Jan 2001 15:09:35 -0800 (PST) Received: (from wkt@localhost) by henry.cs.adfa.edu.au (8.11.1/8.9.3) id f04NFuF07406; Fri, 5 Jan 2001 10:15:56 +1100 (EST) (envelope-from wkt) From: Warren Toomey Message-Id: <200101042315.f04NFuF07406@henry.cs.adfa.edu.au> Subject: Re: kldload: Exec format error, is 4.2 problem? In-Reply-To: <14932.40645.130709.857043@onceler.kciLink.com> from Vivek Khera at "Jan 4, 2001 11:03:17 am" To: Vivek Khera Date: Fri, 5 Jan 2001 10:15:56 +1100 (EST) Cc: stable@FreeBSD.ORG Reply-To: wkt@cs.adfa.edu.au X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article by Vivek Khera: > >>>>> "WT" == Warren Toomey writes: > WT> ld -Bshareable -o vmmon_up.ko setdef0.o vmmon_up.kld setdef1.o linux > > WT> By commenting out this flag, the file `linux' isn't used, and the module > WT> can then be loaded by kldload. Also, vmware appears to work fine. > > Do you comment it out on both vmware2 modules and rtc module or just > one of them? > Vivek Khera I'm thinking that I can't load modules that are linked with `linux' because I have the Linux emulation stuff built-in to my kernel, and not as a separate module. Can any module guru tell us exactly what the `linux' word does on the link line? Does it mean ``the linux kernel module is required to load this module''? If so, that's why I need to leave it off when I'm making these modules. Vivek, I can't load any modules that were linked with the `linux' option. Cheers, Warren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 15:31:11 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 15:31:09 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from nisser.com (c0039.upc-c.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 30B9937B400 for ; Thu, 4 Jan 2001 15:30:51 -0800 (PST) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id AAA79717; Fri, 5 Jan 2001 00:29:24 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A550755.7F25AE45@nisser.com> Date: Fri, 05 Jan 2001 00:29:25 +0100 From: Roelof Osinga Organization: Nisser - Nr. 1 in Veiligheid X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Fred Clift Cc: dxoch , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum Question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fred Clift wrote: > > On Thu, 4 Jan 2001, Roelof Osinga wrote: > > >> dxoch wrote: > > >From what I understand, the boot-loader doesn't grok vinum partitions. If > you wanted to get really complicated, you could boot from an MD image for > your root file-system and re-arrange things so that all the stuff that > needs to be dynamic lives on a vinum partition and just use the MD image > for booting. > > Then you're fairly insulated from disk-failure -- root is in memory and > /usr + your other data is mirrored. > > It is a hassle though. Something like that. Hassle it may be, but when that brown goo indeed hits the fan... Any, MO = Magneto-Optical thus MD would be Memory Disk? OTOH and referring to that shitty image, could also be a proctologist I guess ;). Haven't looked into that, was more thinking along the lines of a stack of floppies. If that bypasses the booting problem, works for me. Or I'm hoping it will anyway. One of these days I really must look into that. I had to boot a system just so some time ago, so I know it can be done. So if it is indeed just the loader that prevents the root from being under vinum's control... What could be a problem in this idyllic scenario is KLM. From what I've gather vinum prefers to be a KLM. Shouldn't really be a problem, but... Another one of those things I've successfully postponed . Roelof -- Home is where the (@) http://eboa.com/ is. Nisser home -- http://www.Nisser.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 15:51:35 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 15:51:33 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from danablue.vision.auc.dk (danablue.miba.auc.dk [130.225.49.152]) by hub.freebsd.org (Postfix) with ESMTP id 5CD7537B400 for ; Thu, 4 Jan 2001 15:51:32 -0800 (PST) Received: from ninka.miba.auc.dk (ninka.miba.auc.dk [130.225.49.13]) by danablue.vision.auc.dk (8.10.1/8.10.1) with ESMTP id f04NpTX12812; Fri, 5 Jan 2001 00:51:29 +0100 (MET) Received: (from madsp@localhost) by ninka.miba.auc.dk (8.10.1/8.10.1) id f04NpTZ07248; Fri, 5 Jan 2001 00:51:29 +0100 (MET) To: Max Khon Cc: stable@FreeBSD.ORG Subject: Re: ad0: WRITE command timeout tag=0 serv=0 - resetting References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit From: Mads Hugo Pedersen Date: 05 Jan 2001 00:51:28 +0100 In-Reply-To: Max Khon's message of "Fri, 5 Jan 2001 03:16:08 +0600 (NOVT)" Message-ID: <4w3ae963mgv.fsf@ninka.miba.auc.dk> Lines: 26 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Jan 2001, Max Khon uttered the following: > Today I have installed latest -stable on a machine where previously I > had 4.1-RELEASE working fine. > > after make installkernel/reboot I have got the following messages on > console: > > ad0: WRITE command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done > ad0: WRITE command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done I had a similar problem with an old chipset which did not support dma, so the controller (ata0) made a fallback to pio. I edited /etc/sysctl.conf and added this line: hw.atamodes=pio,pio,pio,pio You can check your dma settings with "sysctl -a hw.atamodes". /M@ds -- I give 100% at work: 12% Monday, 22% Tuesday, 38% Wednesday, 23% Thursday and 5% on Friday. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 16:43:35 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 16:43:31 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 4ABD937B400 for ; Thu, 4 Jan 2001 16:43:30 -0800 (PST) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id LAA13540 for ; Fri, 5 Jan 2001 11:43:23 +1100 (EST) (envelope-from carl@xena.ipaustralia.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma013524; Fri, 5 Jan 01 11:43:18 +1100 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.11.1/8.11.0) with ESMTP id f050hIi55923 for ; Fri, 5 Jan 2001 11:43:18 +1100 (EST) (envelope-from carl@xena.ipaustralia.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Fri, 5 Jan 2001 11:43:18 +1100 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: stable@freebsd.org Subject: Problems with Make Release! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A make release on the 4.2-STABLE branch is currently dying with; (cd /usr/src/etc/../share/man; make makedb; ) makewhatis /usr/share/man makewhatis:No such file or directory *** Error code 1 Stop in /usr/src/share/man. *** Error code 1 Stop in /usr/src/etc. *** Error code 1 Stop in /usr/src/release. Also "install -C" (ie compare before install) doesn't seem to work either. Anyone have any ideas on how to get around this? Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 17:30:48 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 17:30:44 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 6E29337B400 for ; Thu, 4 Jan 2001 17:30:43 -0800 (PST) Received: (qmail 26112 invoked by uid 0); 5 Jan 2001 01:30:41 -0000 Received: from p3e9bc23d.dip.t-dialin.net (HELO forge.local) (62.155.194.61) by mail.gmx.net (mail08) with SMTP; 5 Jan 2001 01:30:41 -0000 Received: from thomas by forge.local with local (Exim 3.16 #1 (Debian)) id 14ELhp-0000J0-00; Fri, 05 Jan 2001 02:30:09 +0100 Date: Fri, 5 Jan 2001 02:30:09 +0100 To: David Wolfskill Cc: stable@FreeBSD.ORG Subject: Re: make vs. gmake (was: Re: Roadmap for perl upgrades to STABLE?) Message-ID: <20010105023009.A1100@crow.dom2ip.de> Mail-Followup-To: tmoestl@gmx.net, David Wolfskill , stable@FreeBSD.ORG References: <20001226231547.R72273@elvis.mu.org> <200101041616.f04GGsh72194@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="OXfL5xGRrasGEqWY" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101041616.f04GGsh72194@pau-amma.whistle.com>; from dhw@whistle.com on Thu, Jan 04, 2001 at 08:16:54AM -0800 From: Thomas Moestl Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 04, 2001 at 08:16:54AM -0800, David Wolfskill wrote: > >> Not that I'm a fan of the GPL, but wouldn't importation of gmake > >> into the toolchain that gets installed by default help this problem > >> along enormously? > >What can it do that bmake can't? > Compile amanda 2.4.2. :-( > > [Ref. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=23328 -- seems that > some Makefiles created by automake (which the amanda folks use) get > created in a way that cause our make to behave in unexpected ways. I > was able to generate a simpler test case that re-creates the problem > (and it's in the PR), but have no fix, nor is it likely I will be able to > devote the time required to become familiar enough with make's internals > to get much of a clue anytime soon, unfortunately. I expect to be able > to help test, though, and am quite willing to do that.] I have attached a patch (against -CURRENT) that fixes the test case in the PR for me. It would be interesting to know how well it works with real-world examples like the amanda Makefile. I have just rolled a complete "make buildworld" with the patched make without problems. Anyone who is brave enough to try this should make a backup copy of his make anyway, because it is a pain to recover a broken make ;-) Feedback is very welcome! If there are no problems with the patch, I will submit a PR soon. - thomas --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="make.diff" *** src/usr.bin/make/suff.c~ Sat Dec 2 21:24:38 2000 --- src/usr.bin/make/suff.c Fri Jan 5 02:12:31 2001 *************** *** 460,467 **** { Lst_Concat (suffClean, sufflist, LST_CONCLINK); sufflist = Lst_Init(FALSE); ! sNum = 0; suffNull = emptySuff; } /*- --- 460,475 ---- { Lst_Concat (suffClean, sufflist, LST_CONCLINK); sufflist = Lst_Init(FALSE); ! sNum = 1; suffNull = emptySuff; + /* + * Clear suffNull's children list (the other suffixes are built new, but + * suffNull is used as is). + * NOFREE is used because all suffixes are are on the suffClean list. + * suffNull should not have parents. + */ + Lst_Destroy(suffNull->children, NOFREE); + suffNull->children = Lst_Init(FALSE); } /*- *************** *** 714,733 **** Suff *s = (Suff *) sp; char *cp; LstNode ln; ! Suff *s2; /* * First see if it is a transformation from this suffix. */ cp = SuffStrIsPrefix(s->name, transform->name); if (cp != (char *)NULL) { ! ln = Lst_Find(sufflist, (void *)cp, SuffSuffHasNameP); ! if (ln != NULL) { /* * Found target. Link in and return, since it can't be anything * else. */ - s2 = (Suff *)Lst_Datum(ln); SuffInsert(s2->children, s); SuffInsert(s->parents, s2); return(0); --- 722,746 ---- Suff *s = (Suff *) sp; char *cp; LstNode ln; ! Suff *s2 = NULL; /* * First see if it is a transformation from this suffix. */ cp = SuffStrIsPrefix(s->name, transform->name); if (cp != (char *)NULL) { ! if (cp[0] == '\0') /* null rule */ ! s2 = suffNull; ! else { ! ln = Lst_Find(sufflist, (void *)cp, SuffSuffHasNameP); ! if (ln != NULL) ! s2 = (Suff *)Lst_Datum(ln); ! } ! if (s2 != NULL) { /* * Found target. Link in and return, since it can't be anything * else. */ SuffInsert(s2->children, s); SuffInsert(s->parents, s2); return(0); *************** *** 2359,2365 **** void * s; void * dummy; { ! printf ("%s ", ((Suff *) s)->name); return (dummy ? 0 : 0); } --- 2372,2378 ---- void * s; void * dummy; { ! printf ("`%s' ", ((Suff *) s)->name); return (dummy ? 0 : 0); } --OXfL5xGRrasGEqWY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 18: 5:26 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 18:05:17 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from zircon.seattle.wa.us (sense-sea-CovadSub-0-228.oz.net [216.39.147.228]) by hub.freebsd.org (Postfix) with SMTP id 988B537B400 for ; Thu, 4 Jan 2001 18:05:16 -0800 (PST) Received: (qmail 2147 invoked by uid 100); 5 Jan 2001 02:05:11 -0000 From: Joe Kelsey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14933.11223.272173.869233@zircon.seattle.wa.us> Date: Thu, 4 Jan 2001 18:05:11 -0800 To: Evan S Cc: Ty , questions@freebsd.org, stable@freebsd.org Subject: Re: sblive installed, but no sound in 4.2 In-Reply-To: References: <3A546233.DB234C09@home.com> X-Mailer: VM 6.89 under Emacs 20.5.1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Evan S writes: > I think I had the same problem with my SB Live. I run a Dual Celeron. When > I would use xmms to play mp3s, nothing would come out of the speakers, > even though when I used cat /dev/sndstat it showed a correctly detected > and configured SB Live, on irq 18, which used to work fine in Linux. > > Finally, out of curiosity, I opened up the case and moved my SB Live to > PCI slot 2. Then it was on irq 16, and it worked. There are many issues with sound playing in fbsd, a lot of them depend heavily on what software you run. I run Gnome and I often get notices from software about not being able to open /dev/dsp. This is usually related to not having ESS configured correctly. I have also noticed that if I leave pysol running (even with the sound server disabled) it sucks up all the sound from any app started *after* pysol. Another thing to check is to hit the PAUSE key when your system boots and displays the PCI configuration. Study it carefully and look for things with the same interrupt. Theoretically, all PCI devices are supposed to be able to share interrupts, but in practice sblive can't handle it. Move the cards around and try again. I spent many hours pulling out what little hair I have left searching for these answers. If you are running Gnome, you have to enable sounds to get the esd started. Then you have to restart Gnome to get everything working. If you are running KDE, I have no thoughts to help you. /Joe > Evan Sarmiento (kaworu@sektor7.ath.cx) > http://sekt7.org/es > > On Thu, 4 Jan 2001, Ty wrote: > > > thanks for the reply, I gave that a try but alas no luck. > > > > I'm now dual booting into mandrake, mandrake has no problem at all > > dealing with the sblive, it sounds great weird. > > > > thanks again! > > > > > > Andreas Ntaflos wrote: > > > > > > hi > > > everything you did seems right, i have an sb live working under fbsd 4.2. > > > maybe it helps if you do a MAKEDEV all in /dev after rebuilding the kernel > > > (as this should always be done after building a new kernel), before you do > > > a MAKEDEV snd0. > > > > > > that's the only step i could imagine you forgot, as everything else is what > > > i did too, and my sound works very well under 4.2 > > > > > > regards > > > Andreas Ntaflos > > > > > > At 12:06 01.01.2001 -0800, you wrote: > > > >Hello, > > > > > > > >I believe I have my sound blaster live correctly installed under feebsd > > > >4.2 yet I can't hear any audio. I do have the mixer settings up. > > > >i recompiled the kernel with > > > >device pcm > > > >(and i have device pci in already) > > > > > > > >then rebooted and did a > > > >cd /dev > > > >./MAKDEV snd0 > > > > > > > >cat /dev/sndstat > > > > > > > >shows: > > > > > > > >FreeBSD Audio Driver (newpcm) Dec 31 2000 12:36:40 > > > >Installed devices: > > > >pcm0: at io 0xd000 irq 10 (4p/3r channels duplex) > > > > > > > >Mixer shows > > > > > > > >Mixer vol is currently set to 62:62 > > > >Mixer pcm is currently set to 100:100 > > > >Mixer speaker is currently set to 100:100 > > > >Mixer line is currently set to 75:75 > > > >Mixer mic is currently set to 80:80 > > > >Mixer cd is currently set to 69:69 > > > >Mixer rec is currently set to 0:0 > > > >Mixer line1 is currently set to 75:75 > > > >Mixer phin is currently set to 69:69 > > > >Mixer phout is currently set to 97:97 > > > >Mixer video is currently set to 100:100bash-2.04# cat /dev/sndstat > > > > > > > >help, is there something i'm missing here? I've put the volume to 100% on > > > >everything including speakers and I don't hear a peep, no matter what type > > > >of audio I attempt to play. > > > > > > > >thank you! > > > > > > > > > > > > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > > > >with "unsubscribe freebsd-questions" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 20:28: 2 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 20:28:00 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.64.180.171]) by hub.freebsd.org (Postfix) with ESMTP id 8DEA937B400 for ; Thu, 4 Jan 2001 20:28:00 -0800 (PST) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id UAA89903; Thu, 4 Jan 2001 20:27:33 -0800 (PST) (envelope-from richw) Date: Thu, 4 Jan 2001 20:27:33 -0800 (PST) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Re: ad0: WRITE command timeout tag=0 serv=0 - resetting Message-ID: <20010105041405.89714.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: richw@wyattearp.stanford.edu Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Max Khon wrote: > > ad0: WRITE command timeout tag=0 serv=0 - resetting > > ata0: resetting devices .. done > > ad0: WRITE command timeout tag=0 serv=0 - resetting > > ata0: resetting devices .. done Mads Hugo Pedersen replied: > I had a similar problem with an old chipset which did not > support dma, so the controller (ata0) made a fallback to > pio. I edited /etc/sysctl.conf and added this line: > hw.atamodes=pio,pio,pio,pio I had the same problem with an old motherboard which claimed to support DMA (but didn't). Setting PIO in /etc/sysctl.conf wasn't good enough, because the timeouts started happening while mounting file systems, which happens before /etc/sysctl.conf is processed. I ended up adding a "sysctl" command to /etc/rc.conf in order to get it done soon enough. I had to use the program's full path (/sbin/sysctl), and I should probably also add ">/dev/null 2>&1" to the command so the output will be discarded. Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 20:38:24 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 20:38:20 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id BB4A537B404 for ; Thu, 4 Jan 2001 20:38:19 -0800 (PST) Received: (qmail 19938173 invoked from network); 5 Jan 2001 04:38:17 -0000 Received: from s011.dhcp212-229.cybercable.fr (HELO gits.dyndns.org) ([212.198.229.11]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 5 Jan 2001 04:38:17 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.1/8.11.1) id f054cGN03464; Fri, 5 Jan 2001 05:38:17 +0100 (CET) (envelope-from root) From: Cyrille Lefevre Message-Id: <200101050438.f054cGN03464@gits.dyndns.org> Subject: Re: bin/19635: add -c for grand total to df(1), like du(1) does To: freebsd-stable@FreeBSD.org, freebsd-current@FreeBSD.org Date: Fri, 5 Jan 2001 05:38:16 +0100 (CET) Cc: will@FreeBSD.org Reply-To: clefevre@citeweb.net Organization: ACME X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi everybody and Happy New Year, anybody to commit http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19635 ? one of the reasons it was not commited was due to an overflow problem which has been fixed since. thanks by advance.. Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 21:36:22 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 21:36:21 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 2ED2937B400 for ; Thu, 4 Jan 2001 21:36:18 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.0/8.11.0) id f055Z3A76978; Fri, 5 Jan 2001 07:35:03 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200101050535.f055Z3A76978@zibbi.icomtek.csir.co.za> Subject: Re: Is make release broken? In-Reply-To: from Carl Makin at "Jan 3, 2001 02:02:29 pm" To: carl@xena.ipaustralia.gov.au (Carl Makin) Date: Fri, 5 Jan 2001 07:35:03 +0200 (SAT) Cc: stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: jhay@zibbi.icomtek.csir.co.za Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm trying to roll a -stable snapshot using "make release" and it's dying > consistantly when it tries to run mkwhatis across the /usr/share/man > directories. > > Is anyone else having problems with make release at the moment? No problem here. Have you disabled perl maybe? zibbi:/users/jhay # file `which makewhatis` /usr/bin/makewhatis: perl commands text John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 21:47:47 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 21:47:45 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id BD16137B400 for ; Thu, 4 Jan 2001 21:47:43 -0800 (PST) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id QAA26452; Fri, 5 Jan 2001 16:46:39 +1100 (EST) (envelope-from carl@xena.ipaustralia.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma026436; Fri, 5 Jan 01 16:46:30 +1100 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.11.1/8.11.0) with ESMTP id f055kUJ59829; Fri, 5 Jan 2001 16:46:30 +1100 (EST) (envelope-from carl@xena.ipaustralia.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Fri, 5 Jan 2001 16:46:30 +1100 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: John Hay Cc: stable@FreeBSD.ORG Subject: Re: Is make release broken? In-Reply-To: <200101050535.f055Z3A76978@zibbi.icomtek.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi John, *bing* On Fri, 5 Jan 2001, John Hay wrote: > > > > I'm trying to roll a -stable snapshot using "make release" and it's dying > > consistantly when it tries to run mkwhatis across the /usr/share/man > > directories. > > > > Is anyone else having problems with make release at the moment? > > No problem here. Have you disabled perl maybe? > > zibbi:/users/jhay # file `which makewhatis` > /usr/bin/makewhatis: perl commands text I have "NOPERL=true" in make.conf for my own buildworlds and forgot it was also used in make release. I'm just restarting it now! Thanks! Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 22:15:51 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 22:15:46 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (dhcp244.osd.bsdi.com [204.216.28.244]) by hub.freebsd.org (Postfix) with ESMTP id 7C72137B400 for ; Thu, 4 Jan 2001 22:15:46 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f056SHt02906; Thu, 4 Jan 2001 22:28:23 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101050628.f056SHt02906@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Rune Mossige" Cc: heckfordj@psi-domain.co.uk, freebsd-stable@FreeBSD.ORG Subject: Re: ASUS A7V and promise problems, SOLVED In-reply-to: Your message of "Tue, 02 Jan 2001 18:32:37 +0100." <005b01c074e2$03d9a500$2aa17dd4@kleppst.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Jan 2001 22:28:17 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The UHCI driver (at least) is very fragile in the presence of interrupts it's not expecting, or if the hardware is not behaving exactly as predicted (eg. it hasn't been initialised by the BIOS properly). In the general case, interrupt sharing between those two devices should actually work, and for your other (PCI) devices, you shouldn't have any problems with shared interrupts. > My problems about the promise appears to have been solved....it was an IRQ > conflict between the 3COM 3C905C and the onboard USB controller, both using > irq5. Why this caused the disks on the promise (irq 10) to fail, I do not > know.....Now I just ned to figure out how to get all adapters (SoundBlaster > Live!, 3com network adapter and RIVA TNT AGP adapter) to coexist happily > with their own IRQ's. > ----- Original Message ----- > From: "Rune Mossige" > To: > Cc: > Sent: 2. januar 2001 17:22 > Subject: Re: ASUS A7V and promise problems > > > > The Promise identifies itself as 'UltraDMA (tm) v2.01 (Build 33)' > > > > Prior to the BIOS upgrade earlier today from 1004d to 1005a, it identified > > itself as 'v2.01 (Build 28)' > > > > Is that the same version? This board boots, and dmesg output looks proper > to > > me. > > > > ----- Original Message ----- > > From: "Jamie Heckford" > > To: "Rune Mossige" > > Cc: > > Sent: 2. januar 2001 16:21 > > Subject: Re: ASUS A7V and promise problems > > > > > > > We had to send back about 50 ABit boards because they had the same > problem > > > on > > > ATA100 - Wouldnt boot FreeBSD, Linux, Windoze anything. > > > > > > Maybe the problem has affected the ASUS boards as well - would be > > > interesting > > > to know if they use the same / v. similar firmware. > > > > > > The problems we had were that we were not able to boot of any IDE/ATAPI > > > devices, we > > > installed FreeBSD using boot floppys and Network, however when booting > > from > > > an > > > IDE device no luck. > > > > > > Maybe dodgy, could be a BIOS issue. > > > > > > J > > > > > > On 2001.01.02 14:49:10 +0000 Rune Mossige wrote: > > > > I just bought myself a Christmas present, a new ASUS A7V, Amd Athlon > > 750, > > > > onboard Promise, and 2 x IBM-DTLA-30745 45GB ATA100 disks. > > > > > > > > In order to install FreeBSD 4.2, I also installed an older 540MB IDE > > > > disk. > > > > > > > > FreeBSD 4.2 was CVSUP'ed and buildworld/installworld done on 31. > > December > > > > 2000. > > > > > > > > FreeBSD boots fine, and finds the promise and disks. But, whenever > try > > > > to > > > > access the disks, the box freeze solid after 2-4 seconds....a hard > reset > > > > is > > > > required. > > > > > > > > New BIOS are also installed (1005a) with no luck. I have also reduced > > all > > > > relevant speed settings in the bios, with no luck. > > > > > > > > The disks are connected with brand new ATA100 cables. > > > > > > > > There is a working fan on the CPU, and I do not think it is too hot. > The > > > > BIOS reports MB at 33C and CPU at 41C. Both disks are primary on their > > > > own > > > > Promise channel. > > > > > > > > Is there anyone who have some hints as to what might be wrong? I have > > > > rebuilt the kernel (GENERIC) and enabled debug. Everything else is > left > > > > as > > > > defaults. But, there is no core, no debug, nothing. Just solid freeze. > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 22:16: 5 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 22:16:04 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail1.rdc1.il.home.com (mail1.rdc1.il.home.com [24.2.1.76]) by hub.freebsd.org (Postfix) with ESMTP id BEFA237B402 for ; Thu, 4 Jan 2001 22:16:03 -0800 (PST) Received: from marx.marvic.chum ([24.17.229.11]) by mail1.rdc1.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010105061602.EVOC17339.mail1.rdc1.il.home.com@marx.marvic.chum> for ; Thu, 4 Jan 2001 22:16:02 -0800 Received: (from vcardona@localhost) by marx.marvic.chum (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id AAA30600 for freebsd-stable@freebsd.org; Fri, 5 Jan 2001 00:17:36 -0600 Date: Fri, 5 Jan 2001 00:17:36 -0600 From: "Victor R. Cardona" To: freebsd-stable@freebsd.org Subject: errors during installworld Message-ID: <20010105001736.A30380@home.com> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everyone, I cvsuped yesterday (1/4/01), and had problems during the installword part. I keep getting "error code 1" in various parts of /usr/src/share/doc. These are solved by going into the specified directory and running make. I also noticed these errors appearing in other areas off the installworld process. Unfortunately, I do not have access to my computer right now or I would be more explicit. Has anyone else experienced these problems? Victor Cardona -- GPG Key fingerprint = 62B1 7995 A830 432C 74E8 1337 EDDB E682 3C76 7404 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 4 22:19:18 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 22:19:15 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail1.rdc1.il.home.com (mail1.rdc1.il.home.com [24.2.1.76]) by hub.freebsd.org (Postfix) with ESMTP id 9DB8737B400 for ; Thu, 4 Jan 2001 22:19:15 -0800 (PST) Received: from marx.marvic.chum ([24.17.229.11]) by mail1.rdc1.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010105061915.EWPB17339.mail1.rdc1.il.home.com@marx.marvic.chum> for ; Thu, 4 Jan 2001 22:19:15 -0800 Received: (from vcardona@localhost) by marx.marvic.chum (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id AAA30655 for freebsd-stable@freebsd.org; Fri, 5 Jan 2001 00:20:49 -0600 Date: Fri, 5 Jan 2001 00:20:49 -0600 From: "Victor R. Cardona" To: freebsd-stable@freebsd.org Subject: termcap Message-ID: <20010105002049.B30380@home.com> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everyone, I have been experiencing problems on 4.x-STABLE for the last couple of days. /etc/termcap exists, and it points to a real termcap file. However applications such as vi refuse to startup saying termcap does not exist, or cannot be opened. Does anyone have any ideas as to how to fix this? Thanks, Victor Cardona -- GPG Key fingerprint = 62B1 7995 A830 432C 74E8 1337 EDDB E682 3C76 7404 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 0: 7:42 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 00:07:41 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from ciberteca.infocentre.gva.es (ciberteca.infocentre.gva.es [195.57.208.34]) by hub.freebsd.org (Postfix) with ESMTP id A60CD37B400 for ; Fri, 5 Jan 2001 00:07:40 -0800 (PST) Received: from infocentre.gva.es ([195.57.208.172]) by ciberteca.infocentre.gva.es (Netscape Messaging Server 3.6) with ESMTP id AAA334 for ; Fri, 5 Jan 2001 09:07:32 +0100 Message-ID: <3A5580BE.11F7CD60@infocentre.gva.es> Date: Fri, 05 Jan 2001 09:07:27 +0100 From: "Jose Luis Arbona Orovay" X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "stable@FreeBSD.ORG" Subject: Aptiva CDROM boot Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My new brand IBM Aptiva model 2178 is unable to boot from specific FreeBSD CDROM boot. I've tested to boot from another bootable CDROM (OpenBSD, Linux RedHat :-(, and it works well with no problem, but when I try to boot from FreeBSD CDROM appears the post state 7F and stops booting, keyboard works but booting doesn't continue and I must reboot and retry with the floppies. I (supposely) assume the problem is located at the BIOS, not in FreeBSD itself, BIOS cannot launch 2.88Mb CDROM boot images but I would like a workaround or similar. Thanks in advance. Jose Luis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 1: 2:37 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 01:02:35 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id 99A0D37B400 for ; Fri, 5 Jan 2001 01:02:34 -0800 (PST) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f0592Wq89862 for ; Fri, 5 Jan 2001 10:02:33 +0100 (CET) Received: from rose.lpthe.jussieu.fr (root@[134.157.10.102]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f0592W328900 for ; Fri, 5 Jan 2001 10:02:32 +0100 (MET) Received: (from michel@localhost) by rose.lpthe.jussieu.fr (8.11.1/8.11.1) id f0592Vv00431 for freebsd-stable@FreeBSD.ORG; Fri, 5 Jan 2001 10:02:31 +0100 (CET) (envelope-from michel) Date: Fri, 5 Jan 2001 10:02:31 +0100 From: Michel Talon To: freebsd-stable@FreeBSD.ORG Subject: Re: termcap Message-ID: <20010105100231.A411@lpthe.jussieu.fr> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <20010105002049.B30380@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20010105002049.B30380@home.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 05, 2001 at 12:20:49AM -0600, Victor R. Cardona wrote: > Hi everyone, > > I have been experiencing problems on 4.x-STABLE for the last couple of > days. /etc/termcap exists, and it points to a real termcap file. However > applications such as vi refuse to startup saying termcap does not exist, > or cannot be opened. Does anyone have any ideas as to how to fix this? > > Thanks, > Victor Cardona Have you run cap_mkdb /etc/termcap ? -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 1:16:47 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 01:16:45 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from oyeindia.com (unknown [202.54.85.43]) by hub.freebsd.org (Postfix) with ESMTP id 6ECFC37B400 for ; Fri, 5 Jan 2001 01:16:31 -0800 (PST) Received: from forseti.rocklines.oyeindia.com ([192.168.1.53] helo=forseti.oyeindia.com) by oyeindia.com with esmtp (Exim 3.16 #2) id 14ET18-0005x5-00 for stable@freebsd.org; Fri, 05 Jan 2001 14:48:34 +0530 Message-Id: <4.3.2.20010105144142.00a9aee0@mail.oyeindia.com> X-Sender: vikas-oyeindia.com@mail.oyeindia.com X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Fri, 05 Jan 2001 14:49:17 +0530 To: stable@freebsd.org From: Vikaas BV Subject: D-Link DFE-530TX config on FreeBSD/Linux Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, There is this queer problem while configuring the D-Link DFE-530TX network card on some systems. A clone of this card/chipset seems to be installed on several HP based desktop systems (Brio). In Linux, the symptom appears to be that the driver recognizes the card and loads but fails to detect the interrupt and in FreeBSD, the module seems to throw an error no 6 (could not map memory...). The problem seems to stem from certain BIOS settings. I was able to get the card working by changing the following BIOS settings: 1. Type of OS to Non-PNP. 2. Reset Configuration data under the PCI setup. Thanks & Regards vikas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 4: 3:40 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 04:03:38 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hypernet.hyper.net (hypernet.hyper.gr [193.218.1.1]) by hub.freebsd.org (Postfix) with ESMTP id A3A2337B400 for ; Fri, 5 Jan 2001 04:03:35 -0800 (PST) Received: from escape.gr (patrinos-2.hyper.gr [193.218.2.19]) by hypernet.hyper.net (8.9.3/8.9.3/Hypernet-0.1) with ESMTP id OAA21169 for ; Fri, 5 Jan 2001 14:00:50 +0200 Message-ID: <3A55B92E.A570E938@escape.gr> Date: Fri, 05 Jan 2001 14:08:20 +0200 From: dxoch Organization: ESCAPE Services X-Mailer: Mozilla 4.7 (Macintosh; I; PPC) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: Vinum Question Content-Type: text/plain; charset=iso-8859-7; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the responce. Till now i am having separate root and swap partitions in each of my two disks, and all my other stuff lives in a vinum mirrored volume. This way i am fairly protected against crashes, but this setup is complicated and difficult to maintain. (If the disk that has the active root partition crashes i must reboot. If the other one chrashes the system continues whitout problem (SCSI disks)) Is there is any chance that vinum-related options in the loader.conf (vinum_load ="YES") can help me to boot from a vimum volume, or this is completely irrelevant? -Jim Xochellis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 4:43:56 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 04:43:54 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 17C9237B400 for ; Fri, 5 Jan 2001 04:43:54 -0800 (PST) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: postfix [port 2719]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <113840-223>; Fri, 5 Jan 2001 13:43:42 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 6BD0113631; Fri, 5 Jan 2001 13:43:30 +0100 (CET) From: Daniel Lang To: Cameron Grant , freebsd-stable@freebsd.org Subject: Soundblaster 128 problems Message-ID: <20010105134330.D17176@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Sender: langd@informatik.tu-muenchen.de Date: Fri, 5 Jan 2001 13:43:31 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've recently bought a Soundblaster 128 PCI. Unfortunately it doesn't seem to work properly. Environment: FreeBSD 4.2-STABLE, using pcm driver. The driver detects the card (which looks correct) like: [..] pcm0: port 0xb800-0xb83f irq 9 at device 13.0 on pci0 (port, irq and device may vary) I rebuilt snd0 and pcaudio in /dev. Now I get sound, but not correct. If try to play an mpeg-file via mpg123 (new installed of course, including required libraries), it plays it, but it sounds very slow, distorted and single-channel. I tried something different. I use another box as answering machine, which provides me some G.711 A-Law files. I played them with g711conf -a < file > /dev/audio This worked, too, but in this case too fast. Like a tape that is listened to, while in fastforward. I have two other machines, one with a Soundblaster 16 (ISA) and one with a Soundblaster AWE 64 (ISA, too). Both work perfectly with pcm (and play the same files in a correct way). To play from CD via the direct-cable works of course. Maybe I am missing something, like a sysctl parameter, or something to setup the driver in a way ? Or maybe the hardware is broken ? How could I test it (well with a M$ box maybe *pain*)... Any hints are appreciated. Best regards, Daniel -- IRCnet: Mr-Spock - May His Shadow fall upon thee - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 5:12:47 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 05:12:44 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 7129237B6A0 for ; Fri, 5 Jan 2001 05:12:44 -0800 (PST) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: postfix [port 2741]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <113655-220>; Fri, 5 Jan 2001 14:12:34 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 9647213631; Fri, 5 Jan 2001 14:12:24 +0100 (CET) From: Daniel Lang To: dxoch , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum Question Message-ID: <20010105141224.E17176@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A55B92E.A570E938@escape.gr> X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Sender: langd@informatik.tu-muenchen.de Date: Fri, 5 Jan 2001 14:12:25 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Jim, [..] > Is there is any chance that vinum-related options in the loader.conf > (vinum_load ="YES") > can help me to boot from a vimum volume, or this is completely > irrelevant? I guess so. I know of 'vinum_load="YES"' only in /etc/rc.conf, not loader.conf or kernel.conf. Although I guess you could immediately load the vinum.ko, before booting the kernel (i.e. load the kernel, load the module along with other modules like splash, then boot the kernel), but this does not help you to boot from a vinum device. The problem is, that in FreeBSD, the bootstrap loaders and the kernel reside in the root-partition. The booting process is described very good in http://www.freebsd.org/handbook/boot.html You will notice that each stage just knows as much about the the disks/filesystem as it needs. So boot1 knows about the disklabel and slices to find boot2 boot2 knows about about UFS/FFS to find /boot/loader or /kernel. Themselves they reside in the MBR, or the boot-sector of the slice. Although loader is more sophisticated, it does not know about vinum, too. The first thing to know about vinum is the kernel with the vinum module loaded. In order to really boot from a vinum device, previous stages also have to know (at least something) about vinum devices. This is not the case, and I guess very difficult to implement. If you look at other OSes which allow booting from managed volumes, you may notice, that they have a special boot-filesystem (e.g. /stand, /boot), which must meet certain requirements, (like contigous block allocation, the first partition on disk/slice, etc). I guess it would be really painful to try to provide this functionality, with many drawbacks (I guess most in code-stability), huge effort required and little advantages. If you need average security agains disk-crashes, you can keep your data in vinum-volumes and back up the root-partition on a regular basis e.g. with dd. If you really need more security, go and buy a SCSI-SCSI raid-controller, which is seen as one or more single disks, independent of its real disks and configuration. You save yourself lots of trouble. Ok, this is just my opinion, based on some experience. Best regards, Daniel -- IRCnet: Mr-Spock - Burn them to ashes, then burn the ashes. - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 5:44:52 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 05:44:51 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from alchemistry.net (alchemistry.net [160.79.102.254]) by hub.freebsd.org (Postfix) with ESMTP id 1CD9B37B400 for ; Fri, 5 Jan 2001 05:44:51 -0800 (PST) Received: from [192.168.0.1] (helo=shark) by alchemistry.net with smtp (Exim 3.20 #1) id 14EXAZ-000PaV-00 for freebsd-stable@FreeBSD.ORG; Fri, 05 Jan 2001 08:44:35 -0500 Message-ID: <004201c0771d$a3c5a590$0100a8c0@krel.org> From: "Ilya" To: References: <20010105141224.E17176@atrbg11.informatik.tu-muenchen.de> Subject: bind in Stable 4.2 Date: Fri, 5 Jan 2001 08:44:34 -0500 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I noticed that in 4.2S named is looking for named-xfer in /usr/local/libexec but the file is located in /usr/libexec. i know i can create a link or copy the file, but its just a work around. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 5:46:48 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 05:46:45 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id 1EF3437B400 for ; Fri, 5 Jan 2001 05:46:41 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14EXB2-0002u0-00; Fri, 5 Jan 2001 16:45:04 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.16 #1) id 14EXCL-000Id4-00; Fri, 05 Jan 2001 16:46:25 +0300 Date: Fri, 5 Jan 2001 16:46:25 +0300 From: Odhiambo Washington To: FBSD-STABLE Cc: Robin_Blanchard@gactr.uga.edu Subject: Re: 4.2-stable buildworld problem Message-ID: <20010105164625.B71302@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , FBSD-STABLE , Robin_Blanchard@gactr.uga.edu References: <3A54D65C.B51CCCBE@gactr.uga.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A54D65C.B51CCCBE@gactr.uga.edu>; from "Robin P. Blanchard" on Thu, Jan 04, 2001 at 03:00:28PM -0500 X-Operating-System: FreeBSD poeza.iconnect.co.ke 3.5-STABLE FreeBSD 3.5-STABLE X-Location: Mombasa, KE, East Africa Sender: Odhiambo Washington Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Robin P. Blanchard [20010104 23:01]: writing on the subject '4.2-stable buildworld problem' Robin> ok... Robin> i totalled scrapped my supfile /usr/src and /usr/obj Robin> and started all over again with a fresh stable-supfile (src-all), Robin> as i haven't been able to buildworld since sometime before christmas. Robin> buildworld plods along until: Robin> Robin> ===> gnu/usr.bin/groff/devX100 Robin> make: don't know how to make S. Stop Robin> *** Error code 2 Robin> 1 error Robin> *** Error code 2 Robin> 1 error Robin> *** Error code 2 Robin> 1 error Robin> *** Error code 2 Robin> 1 error Robin> *** Error code 2 Robin> 1 error Robin> *** Error code 2 Robin> 1 error I had errors most of the time and mostly with troff and had even cleared /usr/src and /usr/obj but did not help until I followed an advise - cd /usr/src/gnu/usr.bin/groff make make install After that I could build and install. I'm also runninf 4.2-S HTH -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. Argue for your limitations and sure enough they're yours. -Richard Bach (contributed by Chris Johnston) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 6: 6:12 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 06:06:09 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from smtp.hccnet.nl (smtp.hccnet.nl [193.172.127.93]) by hub.freebsd.org (Postfix) with ESMTP id 194EE37B402 for ; Fri, 5 Jan 2001 06:06:09 -0800 (PST) Received: from parmenides.utp.net by smtp.hccnet.nl via uds57-123.dial.hccnet.nl [193.173.123.57] with ESMTP id PAA21637 (8.8.5/1.13); Fri, 5 Jan 2001 15:06:04 +0100 (MET) Received: by parmenides.utp.net (Postfix, from userid 1005) id 6CD9614E; Fri, 5 Jan 2001 15:04:55 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by parmenides.utp.net (Postfix) with ESMTP id 303E014D; Fri, 5 Jan 2001 15:04:55 +0100 (CET) Date: Fri, 5 Jan 2001 15:04:55 +0100 (CET) From: Janko van Roosmalen To: Odhiambo Washington Cc: FBSD-STABLE Subject: Re: 4.2-STABLE build fails In-Reply-To: <20010104095534.A51777@poeza.iconnect.co.ke> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 Jan 2001, Odhiambo Washington wrote: > Hi > I've seen much of this discussed here but mine seems to break at this > point: > > /usr/obj/usr/src/share/doc/usd/13.viref/troff.core > > ..and with this msg on the console... > > Jan 3 18:54:07 alouette /kernel: pid 54505 (troff), uid 0: exited on > signal 11 (core dumped) > Jan 3 18:54:07 alouette /kernel: pid 54523 (troff), uid 0: exited on > signal 11 (core dumped) > > > Even a fresh cvsup (after rm-ing all my srcs and usr/obj) does not help. > Any pointer what this 13.viref thing is and how I can sort that out will > be highly appreciated. > > > -Wash The FreeBSD faq mentions that signal 11 points to hardware problems. ===Janko van Roosmalen - Vught - Netherlands=== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 6:21:52 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 06:21:49 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hypernet.hyper.net (hypernet.hyper.gr [193.218.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 731B337B400 for ; Fri, 5 Jan 2001 06:21:46 -0800 (PST) Received: from escape.gr (patrinos-2.hyper.gr [193.218.2.19]) by hypernet.hyper.net (8.9.3/8.9.3/Hypernet-0.1) with ESMTP id QAA23813; Fri, 5 Jan 2001 16:18:30 +0200 Message-ID: <3A55D971.42FB0B16@escape.gr> Date: Fri, 05 Jan 2001 16:25:56 +0200 From: dxoch Organization: ESCAPE Services X-Mailer: Mozilla 4.7 (Macintosh; I; PPC) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Lang , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum Question References: <20010105141224.E17176@atrbg11.informatik.tu-muenchen.de> Content-Type: text/plain; charset=iso-8859-7; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Lang wrote: > Hi Jim, > > [..] > > Is there is any chance that vinum-related options in the loader.conf > > (vinum_load ="YES") > > can help me to boot from a vimum volume, or this is completely > > irrelevant? > > I guess so. I know of 'vinum_load="YES"' only in /etc/rc.conf, > not loader.conf or kernel.conf. > vi /boot/defaults/loader.conf and you will find: vinum_load="NO" > > Although I guess you could immediately load the vinum.ko, > before booting the kernel (i.e. load the kernel, load the > module along with other modules like splash, then boot the kernel), > but this does not help you to boot from a vinum device. > > The problem is, that in FreeBSD, the bootstrap loaders and the > kernel reside in the root-partition. > The booting process is described very good in > > http://www.freebsd.org/handbook/boot.html > > You will notice that each stage just knows as much about the > the disks/filesystem as it needs. > So boot1 knows about the disklabel and slices to find boot2 > boot2 knows about about UFS/FFS to find /boot/loader or > /kernel. Themselves they reside in the MBR, or the boot-sector > of the slice. > > Although loader is more sophisticated, it does not know about vinum, I thought the same myself byt, in that case, what is the purpose of the vinum_load option ? > > too. The first thing to know about vinum is the kernel with the vinum > module loaded. In order to really boot from a vinum device, > previous stages also have to know (at least something) about vinum > devices. This is not the case, and I guess very difficult to > implement. If you look at other OSes which allow booting from > managed volumes, you may notice, that they have a special > boot-filesystem (e.g. /stand, /boot), which must meet certain > requirements, (like contigous block allocation, the first partition > on disk/slice, etc). I guess it would be really painful to > try to provide this functionality, with many drawbacks > (I guess most in code-stability), huge effort required and > little advantages. > If you need average security agains disk-crashes, you can keep your > data in vinum-volumes and back up the root-partition on a regular > basis e.g. with dd. If you really need more security, go and > buy a SCSI-SCSI raid-controller, which is seen as one or more > single disks, independent of its real disks and configuration. > You save yourself lots of trouble. > > Ok, this is just my opinion, based on some experience. I dont dissagree at all, but this is not for me to deside. Thank you very much Daniel. > > > Best regards, > Daniel > -- > IRCnet: Mr-Spock - Burn them to ashes, then burn the ashes. - > *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 6:45:18 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 06:45:16 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 9F84B37B402 for ; Fri, 5 Jan 2001 06:45:15 -0800 (PST) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: postfix [port 2777]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <112539-224>; Fri, 5 Jan 2001 15:45:09 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 345A813631; Fri, 5 Jan 2001 15:45:08 +0100 (CET) From: Daniel Lang To: dxoch Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Vinum Question Message-ID: <20010105154507.F17176@atrbg11.informatik.tu-muenchen.de> References: <20010105141224.E17176@atrbg11.informatik.tu-muenchen.de> <3A55D971.42FB0B16@escape.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A55D971.42FB0B16@escape.gr>; from dxoch@escape.gr on Fri, Jan 05, 2001 at 03:21:55PM +0000 X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Sender: langd@informatik.tu-muenchen.de Date: Fri, 5 Jan 2001 15:45:09 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, dxoch wrote on Fri, Jan 05, 2001 at 03:21:55PM +0000: [..] > vi /boot/defaults/loader.conf and you will find: vinum_load="NO" True I missed that... [..] > > Although I guess you could immediately load the vinum.ko, > > before booting the kernel (i.e. load the kernel, load the > > module along with other modules like splash, then boot the kernel), > > but this does not help you to boot from a vinum device. [..] > > Although loader is more sophisticated, it does not know about vinum, > > I thought the same myself byt, in that case, > what is the purpose of the vinum_load option ? As I said, to load the module before booting the kernel. Just as the other modules. As the module is loaded into the _kernel_ not into 'loader' or anything you cannot use it until the kernel booted. I guess it makes little difference, if you load the klm at this stage or later. Nearly all parts of the system, that need a specific module, load it on demand, if its not present at startup (ipf doesn't unfortunately ;)). And you can load many via /etc/rc* There may be situations in which it is required or at least of advantage if the module is loaded before booting. Although you can set the root-device in loader.conf, it probably won't work to set it to a vinum device. Best regards, Daniel -- IRCnet: Mr-Spock - Der Schatten von Hasenfuss ist ziemlich dunkel - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 7:18:31 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 07:18:28 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from bbnrel4.net.external.hp.com (bbnrel4.net.external.hp.com [155.208.254.68]) by hub.freebsd.org (Postfix) with ESMTP id 2632C37B402 for ; Fri, 5 Jan 2001 07:18:28 -0800 (PST) Received: from hpcpbla.bri.hp.com (hpcpbla.bri.hp.com [15.144.112.65]) by bbnrel4.net.external.hp.com (Postfix) with ESMTP id A48C321E2E; Fri, 5 Jan 2001 16:18:24 +0100 (MET) Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53]) by hpcpbla.bri.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id PAA03446; Fri, 5 Jan 2001 15:18:16 GMT Received: (from keithj@localhost) by sse0691.bri.hp.com (8.11.1/8.9.3) id f05FIhf06869; Fri, 5 Jan 2001 15:18:43 GMT (envelope-from keithj) Date: Fri, 5 Jan 2001 15:18:43 +0000 From: Keith Jones To: Janko van Roosmalen Cc: Odhiambo Washington , FBSD-STABLE Subject: Re: 4.2-STABLE build fails Message-ID: <20010105151843.A6570@moose.bri.hp.com> Mail-Followup-To: Keith Jones , Janko van Roosmalen , Odhiambo Washington , FBSD-STABLE References: <20010104095534.A51777@poeza.iconnect.co.ke> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from acs.van.roosmalen@hccnet.nl on Fri, Jan 05, 2001 at 03:04:55PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 05, 2001 at 03:04:55PM +0100, Janko van Roosmalen wrote: > > I've seen much of this discussed here but mine seems to break at this > > point: > > > > /usr/obj/usr/src/share/doc/usd/13.viref/troff.core > > > > ..and with this msg on the console... > > > > Jan 3 18:54:07 alouette /kernel: pid 54505 (troff), uid 0: exited on > > signal 11 (core dumped) > > Jan 3 18:54:07 alouette /kernel: pid 54523 (troff), uid 0: exited on > > signal 11 (core dumped) > > > > > > Even a fresh cvsup (after rm-ing all my srcs and usr/obj) does not help. > > Any pointer what this 13.viref thing is and how I can sort that out will > > be highly appreciated. > > The FreeBSD faq mentions that signal 11 points to hardware problems. Could people please STOP spreading this myth that all Signal 11's during 'make world' are a result of hardware problems. It is highly misleading. How would you feel if you acted on this advice and shelled out your hard-earned cash for new hardware only to find that it was a software problem after all? The chances are that if a signal occurs as the result of running a particular program (in this case 'troff'), it's likely to be the version of that program or a shared library on which it depends that is broken somehow on the user's machine, not the user's hardware. You could try manually recompiling and installing 'troff' et al. (located in the directory /usr/src/contrib/groff) then rerunning 'make world'. -- Keith Jones E-Business Service Introduction, GBIT-EMEA (Bristol) E: keith_jones@non.hp.com T: [+44 117] 312-7602 I don't speak for Hewlett-Packard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 7:52: 7 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 07:52:05 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc2.il.home.com (ha2.rdc2.il.home.com [24.2.1.36]) by hub.freebsd.org (Postfix) with ESMTP id D7E0B37B400 for ; Fri, 5 Jan 2001 07:52:04 -0800 (PST) Received: from marx.marvic.chum ([24.17.229.11]) by mail.rdc2.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010105155204.VFLM618.mail.rdc2.il.home.com@marx.marvic.chum> for ; Fri, 5 Jan 2001 07:52:04 -0800 Received: (from vcardona@localhost) by marx.marvic.chum (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id JAA06438 for freebsd-stable@FreeBSD.ORG; Fri, 5 Jan 2001 09:53:41 -0600 Date: Fri, 5 Jan 2001 09:53:41 -0600 From: "Victor R. Cardona" To: freebsd-stable@FreeBSD.ORG Subject: Re: termcap Message-ID: <20010105095341.A6413@home.com> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <20010105002049.B30380@home.com> <20010105100231.A411@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010105100231.A411@lpthe.jussieu.fr>; from michel@lpthe.jussieu.fr on Fri, Jan 05, 2001 at 10:02:31AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 05, 2001 at 10:02:31AM +0100, Michel Talon wrote: > On Fri, Jan 05, 2001 at 12:20:49AM -0600, Victor R. Cardona wrote: > > Hi everyone, > > > > I have been experiencing problems on 4.x-STABLE for the last couple of > > days. /etc/termcap exists, and it points to a real termcap file. However > > applications such as vi refuse to startup saying termcap does not exist, > > or cannot be opened. Does anyone have any ideas as to how to fix this? > > > > Thanks, > > Victor Cardona > > Have you run cap_mkdb /etc/termcap ? Yes I have. I did that when I noticed that applications couldn't find termcap. Sorry, I should have mentioned that earlier. Victor Cardona -- GPG Key fingerprint = 62B1 7995 A830 432C 74E8 1337 EDDB E682 3C76 7404 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 8: 5:24 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 08:05:17 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 6097437B402 for ; Fri, 5 Jan 2001 08:05:17 -0800 (PST) Received: from [172.17.1.121] (warp-core.skynet.be [195.238.2.25]) by apoq.skynet.be (Postfix) with ESMTP id 21FDD9C9B; Fri, 5 Jan 2001 17:05:03 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: Date: Fri, 5 Jan 2001 17:04:47 +0100 To: Greg Lehey From: Brad Knowles Subject: Problems with corrupted vinum devices... Cc: Andy De Petter , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I've read the man page, the vinum debugging page at , searched the archives of the stable mailing list, and still haven't found anything that would appear to address the situation we've just started experiencing. Many months ago, we had a Diablo USENET news spool/reader server that was up and operating fine, taking a slave feed from another news spool server, until such time as I was able to get separate reader-only servers working. I had separate /usr/news/history and /usr/news/spool filesystems set up on their own vinum RAID 1+0 volumes (striped and mirrored across slices on each of the four logical units that were exported from the drive array), as well as a set of four spool directories on their own "raw" slices of those same logical units. The hardware configuration is a Dell PowerEdge 1300 with dual 450Mhz processors with 1GB of ECC RAM, running 4.1-STABLE (I last did a make update on Aug 8 16:27, according to the logfiles I keep), with an IBM DDRS-39130D DC2A drive as the boot disk. No changes (that I know of) have been made to the system sources since this time, including vinum. Unfortunately, we ran into problems with the mail system, and had to "borrow" half of the drives in the external drive array that was attached to the news spool server. I copied the data from the spool directories on the two logical units that would be disappearing to the other pair of spool directories that would be remaining, and then I broke the mirrors and pulled out half the drives and moved them over to the other drive array we have on the mail system. I was very careful to pull out drives associated with only the two logical units I had copied the data from, and that this would not cause any stripes to be broken. Fast forward to the next millenium, and we finally have the replacements for the disks in place, and we're starting the process of trying to revive this machine. Even though we created the slices and the partitions correctly, we still weren't able to get vinum to recognize the restored disk devices correctly, and I wasn't aware of the page at . So, instead, I just copied all the data from the two filesystems that had been mirrored and striped, and then did a "resetconfig". I then re-created the vinum configuration with exactly the same parameters as I had used the first time, and was able to get vinum to init and bring online the "restored" disk devices and rebuild the mirrors, etc.... We then put filesystems on everything, and copied all the files back to their correct locations. So far as we could tell, this seemed to have worked perfectly, and we were done. However, at some point within the next couple of hours (we're not quite sure when), the machine crashed, and vinum failed to come up on the reboot. We had to comment out the /etc/fstab entries that referred to the vinum volumes, and since then have been trying to debug the problems as to why vinum can't find or start any devices at all. Following the instructions at , I tried pulling the file log information as specified. The exact command I used was (line-wrapped for readability): $ for i in /dev/da2s1e /dev/da2s2e /dev/da3s1e \ /dev/da3s2e /dev/da4s1e /dev/da4s2e /dev/da5s1e \ /dev/da5s2e; do (dd if=$i skip=8 count=6|tr -d \ '\000-\011\200-\377'; echo) >> brad.log; done The first two disk devices (da2 & da3) produced gibberish. The last two disk devices (da4 & da5) produced reasonably intelligible output, but instead of "IN VINO" as the first seven characters, I got "NO VINO" instead. A compressed version of the log file available is via my personal anonymous ftp space -- see . Yes, I know this file is trivially small, but if I compress it then I can make sure that no one attempts to transfer it in ASCII mode, and that if they do then they get what they deserve. ;-) From the time when I did the resetconfig until now, here is the contents of /var/log/vinum_history: 5 Jan 2001 12:36:58.476142 resetconfig 5 Jan 2001 12:37:04.663644 *** Created devices *** 5 Jan 2001 12:37:10.622895 quit 5 Jan 2001 12:37:19.576839 *** vinum started *** 5 Jan 2001 12:37:19.577725 create -f /etc/vinum.conf drive d1 device /dev/da2s1e drive d2 device /dev/da3s1e drive d3 device /dev/da4s1e drive d4 device /dev/da5s1e drive d5 device /dev/da2s2e drive d6 device /dev/da3s2e drive d7 device /dev/da4s2e drive d8 device /dev/da5s2e volume history plex org striped 32m sd length 0 drive d1 sd length 0 drive d2 plex org striped 32m sd length 0 drive d3 sd length 0 drive d4 volume spool plex org striped 32m sd length 0 drive d8 sd length 0 drive d7 plex org striped 32m sd length 0 drive d6 sd length 0 drive d5 5 Jan 2001 12:37:19.659734 *** Created devices *** 5 Jan 2001 12:37:42.812629 *** vinum started *** 5 Jan 2001 12:37:44.711438 ls -v 5 Jan 2001 12:37:53.114029 start d6 5 Jan 2001 12:37:59.311274 start d5 5 Jan 2001 12:38:07.602677 ls -v 5 Jan 2001 12:38:13.014144 start spool.p1.s1 5 Jan 2001 12:38:26.887609 exit 5 Jan 2001 12:38:28.403601 quit 5 Jan 2001 12:41:32.279534 *** vinum started *** 5 Jan 2001 12:41:33.542050 ls -v 5 Jan 2001 12:41:46.965537 initialize spool.p1.s0 5 Jan 2001 12:41:49.561185 init spool.p1.s0 5 Jan 2001 12:41:54.304397 ls -v 5 Jan 2001 12:42:11.275776 init history.p1.s0 5 Jan 2001 12:42:12.599953 init history.p1.s1 5 Jan 2001 12:42:16.010292 ls -v 5 Jan 2001 12:48:07.540908 *** vinum started *** 5 Jan 2001 12:48:08.955230 ls -v 5 Jan 2001 12:52:45.324897 ls -v 5 Jan 2001 12:38:13.014144 start spool.p1.s1 5 Jan 2001 13:00:18.560459 *** vinum started *** 5 Jan 2001 13:00:20.138779 ls -v 5 Jan 2001 13:00:47.388334 *** vinum started *** 5 Jan 2001 13:00:48.383848 ls -v 5 Jan 2001 16:32:55.861137 *** vinum started *** 5 Jan 2001 16:32:55.869648 start 5 Jan 2001 15:35:02.271176 *** vinum started *** 5 Jan 2001 15:35:03.369950 ls 5 Jan 2001 15:35:04.178968 ls -v 5 Jan 2001 15:36:18.528618 *** vinum started *** 5 Jan 2001 15:36:21.619565 start 5 Jan 2001 15:36:46.720739 ls -v 5 Jan 2001 15:36:49.123128 ls -V 5 Jan 2001 15:37:00.724413 ls -p 5 Jan 2001 15:37:03.958826 ls -P 5 Jan 2001 15:39:24.212310 *** vinum started *** 5 Jan 2001 15:39:24.213161 start 5 Jan 2001 15:53:52.092618 *** vinum started *** 5 Jan 2001 15:53:53.778854 start 5 Jan 2001 15:54:01.699490 quit 5 Jan 2001 16:07:19.846860 *** vinum started *** 5 Jan 2001 16:07:19.847727 makedev 5 Jan 2001 16:07:19.848473 *** Created devices *** 5 Jan 2001 16:07:25.074358 *** vinum started *** 5 Jan 2001 16:07:26.330688 start 5 Jan 2001 16:08:27.987415 *** vinum started *** 5 Jan 2001 16:08:27.988301 read /dev/da2s1e From the time of the reboot ending with the time vinum was unable to read the last device, in /var/log/messages I find: Jan 5 15:53:34 baloo /BALOO: SMP: AP CPU #1 Launched! Jan 5 15:53:34 baloo /BALOO: Waiting 5 seconds for SCSI devices to settle Jan 5 15:53:34 baloo /BALOO: da2 at ahc0 bus 0 target 6 lun 0 Jan 5 15:53:34 baloo /BALOO: da2: Fixed Direct Access SCSI-2 device Jan 5 15:53:34 baloo /BALOO: da2: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 5 15:53:34 baloo /BALOO: da2: 68235MB (139745280 512 byte sectors: 255H 63S/T 8698C) Jan 5 15:53:34 baloo /BALOO: da4 at ahc1 bus 0 target 5 lun 0 Jan 5 15:53:34 baloo /BALOO: da4: Fixed Direct Access SCSI-2 device Jan 5 15:53:34 baloo /BALOO: da4: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 5 15:53:34 baloo /BALOO: da4: 68235MB (139745280 512 byte sectors: 255H 63S/T 8698C) Jan 5 15:53:34 baloo /BALOO: da3 at ahc0 bus 0 target 6 lun 1 Jan 5 15:53:34 baloo /BALOO: da3: Fixed Direct Access SCSI-2 device Jan 5 15:53:34 baloo /BALOO: da3: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 5 15:53:34 baloo /BALOO: da3: 68235MB (139745280 512 byte sectors: 255H 63S/T 8698C) Jan 5 15:53:34 baloo /BALOO: da5 at ahc1 bus 0 target 5 lun 1 Jan 5 15:53:34 baloo /BALOO: da5: Fixed Direct Access SCSI-2 device Jan 5 15:53:34 baloo /BALOO: da5: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 5 15:53:34 baloo /BALOO: da5: 68235MB (139745280 512 byte sectors: 255H 63S/T 8698C) Jan 5 15:53:34 baloo /BALOO: Mounting root from ufs:/dev/da1s1a Jan 5 15:53:34 baloo /BALOO: da1 at ahc2 bus 0 target 1 lun 0 Jan 5 15:53:34 baloo /BALOO: da1: Fixed Direct Access SCSI-2 device Jan 5 15:53:34 baloo /BALOO: da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 5 15:53:34 baloo /BALOO: da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) Jan 5 15:53:34 baloo /BALOO: vinum: loaded Jan 5 15:53:34 baloo /BALOO: vinum: reading configuration from /dev/da5s2e Jan 5 15:53:34 baloo /BALOO: vinum_scandisk: /dev/da5s2e is down Jan 5 15:53:34 baloo /BALOO: vinum: Can't read device /dev/da5s2e, error 5 Jan 5 15:53:34 baloo /BALOO: vinum: updating configuration from /dev/da2s2e Jan 5 15:53:34 baloo /BALOO: vinum_scandisk: /dev/da2s2e is down Jan 5 15:53:34 baloo /BALOO: vinum: Can't read device /dev/da2s2e, error 5 Jan 5 15:53:34 baloo /BALOO: vinum: updating configuration from /dev/da3s1e Jan 5 15:53:34 baloo /BALOO: vinum_scandisk: /dev/da3s1e is down Jan 5 15:53:34 baloo /BALOO: vinum: Can't read device /dev/da3s1e, error 5 Jan 5 15:53:34 baloo /BALOO: vinum: updating configuration from /dev/da3s2e Jan 5 15:53:35 baloo /BALOO: vinum_scandisk: /dev/da3s2e is down Jan 5 15:53:35 baloo /BALOO: vinum: Can't read device /dev/da3s2e, error 5 Jan 5 15:53:35 baloo /BALOO: vinum: updating configuration from /dev/da4s1e Jan 5 15:53:35 baloo /BALOO: vinum_scandisk: /dev/da4s1e is down Jan 5 15:53:35 baloo /BALOO: vinum: Can't read device /dev/da4s1e, error 5 Jan 5 15:53:35 baloo /BALOO: vinum: updating configuration from /dev/da4s2e Jan 5 15:53:35 baloo /BALOO: vinum_scandisk: /dev/da4s2e is down Jan 5 15:53:35 baloo /BALOO: vinum: Can't read device /dev/da4s2e, error 5 Jan 5 15:53:35 baloo /BALOO: vinum: updating configuration from /dev/da5s1e Jan 5 15:53:35 baloo /BALOO: vinum_scandisk: /dev/da5s1e is down Jan 5 15:53:35 baloo /BALOO: vinum: Can't read device /dev/da5s1e, error 5 Jan 5 15:53:35 baloo /BALOO: vinum: updating configuration from /dev/da2s1e Jan 5 15:53:35 baloo /BALOO: vinum_scandisk: /dev/da2s1e is down Jan 5 15:53:35 baloo /BALOO: vinum: Can't read device /dev/da2s1e, error 5 Jan 5 15:53:35 baloo /BALOO: vinum: couldn't read configuration Unfortunately, I'm at a loss as to understand where to go next in terms of debugging this matter. Any and all help you can provide is appreciated. Thanks! -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 8:20: 9 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 08:20:04 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id C82AB37B400 for ; Fri, 5 Jan 2001 08:19:59 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14EZZH-000B8j-00; Fri, 5 Jan 2001 19:18:15 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.16 #1) id 14EZaW-000JBV-00; Fri, 05 Jan 2001 19:19:32 +0300 Date: Fri, 5 Jan 2001 19:19:32 +0300 From: Odhiambo Washington To: Janko van Roosmalen Cc: FBSD-STABLE Subject: Re: 4.2-STABLE build fails Message-ID: <20010105191932.A73628@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , Janko van Roosmalen , FBSD-STABLE References: <20010104095534.A51777@poeza.iconnect.co.ke> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from "Janko van Roosmalen" on Fri, Jan 05, 2001 at 03:04:55PM +0100 X-Operating-System: FreeBSD poeza.iconnect.co.ke 3.5-STABLE FreeBSD 3.5-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: Odhiambo Washington Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Janko van Roosmalen [20010105 17:06]: writing on the subject 'Re: 4.2-STABLE build fails' Janko> On Thu, 4 Jan 2001, Odhiambo Washington wrote: Janko> Janko> > Hi Janko> > I've seen much of this discussed here but mine seems to break at this Janko> > point: Janko> > Janko> > /usr/obj/usr/src/share/doc/usd/13.viref/troff.core Janko> > Janko> > ..and with this msg on the console... Janko> > Janko> > Jan 3 18:54:07 alouette /kernel: pid 54505 (troff), uid 0: exited on Janko> > signal 11 (core dumped) Janko> > Jan 3 18:54:07 alouette /kernel: pid 54523 (troff), uid 0: exited on Janko> > signal 11 (core dumped) Janko> > Janko> > Janko> > Even a fresh cvsup (after rm-ing all my srcs and usr/obj) does not help. Janko> > Any pointer what this 13.viref thing is and how I can sort that out will Janko> > be highly appreciated. Janko> > Janko> > Janko> > -Wash Janko> Janko> The FreeBSD faq mentions that signal 11 points to hardware problems. Apparently I did blow up the machine and did a fresh cvsup, built troff by hand before buildworld and installworld and I went away with it. I multiboot the bos with ALL those Windows versions (Win98/NT4 SERVER/2000 SERVER) and they never complained. Kent Stewart also pointed me towards this very direction and I just got apprehensive but all I could start with is a blower. Let's give it some time maybe the monster will ultimately rear its head;-) -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. All newspaper editorial writers ever do is come down from the hills after the battle is over and shoot the wounded. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 8:44:48 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 08:44:44 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id D5C1237B400 for ; Fri, 5 Jan 2001 08:44:43 -0800 (PST) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id RAA17887; Fri, 5 Jan 2001 17:44:03 +0100 (CET) Message-Id: <200101051644.RAA17887@midten.fast.no> To: blk@skynet.be Cc: grog@lemis.com, andy.depetter@ops.skynet.be, freebsd-stable@FreeBSD.ORG Subject: Re: Problems with corrupted vinum devices... From: Tor.Egge@fast.no In-Reply-To: Your message of "Fri, 5 Jan 2001 17:04:47 +0100" References: X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 05 Jan 2001 17:44:02 +0100 Sender: Tor.Egge@fast.no Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However, at some point within the next couple of hours (we're not > quite sure when), the machine crashed, and vinum failed to come up on > the reboot. We had to comment out the /etc/fstab entries that > referred to the vinum volumes, and since then have been trying to > debug the problems as to why vinum can't find or start any devices at > all. I suggest increasing INITIAL_DRIVES in vinumvar.h to avoid array resize and the associated race conditions. When I tried to configure vinum to use 14 disks yesterday, the machine immediately crashed with a trap 12 in response to 'vinum create'. I bumped INITIAL_DRIVES to 16 to avoid the drive array resize that caused the problem. I bumped INITIAL_SUBDISKS_IN_PLEX too, just to be safe. To avoid similar races with RAID-5 under high load or with softupdates, I had to bump INITIAL_LOCKS to avoid a fatal range lock array resize. For 4.2-STABLE, I'm currently using the following patch to implement the workarounds: diff -ru /tmp/vinum/vinumlock.c ./vinumlock.c --- /tmp/vinum/vinumlock.c Mon May 22 18:21:37 2000 +++ ./vinumlock.c Thu Jan 4 20:07:06 2001 @@ -249,7 +249,7 @@ #endif plex->lockwaits++; /* waited one more time */ tsleep((void *) lock->stripe, PRIBIO, "vrlock", 2 * hz); - lock = plex->lock; /* start again */ + lock = plex->lock - 1; /* start again */ foundlocks = 0; pos = NULL; } @@ -288,6 +288,12 @@ unlockrange(int plexno, struct rangelock *lock) { daddr_t lockaddr; + struct plex *plex; + + plex = &PLEX[plexno]; + if (lock < &plex->lock[0] || lock >= &plex->lock[plex->alloclocks]) + panic("vinum: rangelock %p on plex %d invalid, not between %p and %p", + lock, plexno, &plex->lock[0], &plex->lock[plex->alloclocks]); #ifdef VINUMDEBUG if (debug & DEBUG_LASTREQS) diff -ru /tmp/vinum/vinumvar.h ./vinumvar.h --- /tmp/vinum/vinumvar.h Mon May 22 18:21:37 2000 +++ ./vinumvar.h Thu Jan 4 19:12:01 2001 @@ -158,15 +158,15 @@ * probably too small. */ - INITIAL_DRIVES = 4, + INITIAL_DRIVES = 16, INITIAL_VOLUMES = 4, INITIAL_PLEXES = 8, INITIAL_SUBDISKS = 16, - INITIAL_SUBDISKS_IN_PLEX = 4, /* number of subdisks to allocate to a plex */ + INITIAL_SUBDISKS_IN_PLEX = 16, /* number of subdisks to allocate to a plex */ INITIAL_SUBDISKS_IN_DRIVE = 4, /* number of subdisks to allocate to a drive */ INITIAL_DRIVE_FREELIST = 16, /* number of entries in drive freelist */ PLEX_REGION_TABLE_SIZE = 8, /* number of entries in plex region tables */ - INITIAL_LOCKS = 256, /* number of locks to allocate to a plex */ + INITIAL_LOCKS = 4096, /* number of locks to allocate to a plex */ MAX_REVIVE_BLOCKSIZE = MAXPHYS, /* maximum revive block size */ DEFAULT_REVIVE_BLOCKSIZE = 65536, /* default revive block size */ VINUMHOSTNAMELEN = 32, /* host name field in label */ - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 9:23:17 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 09:23:15 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from pogo.caustic.org (pogo.caustic.org [208.44.193.69]) by hub.freebsd.org (Postfix) with ESMTP id 8BE9F37B402 for ; Fri, 5 Jan 2001 09:23:15 -0800 (PST) Received: from localhost (jan@localhost) by pogo.caustic.org (8.11.0/ignatz) with ESMTP id f05HNE473427 for ; Fri, 5 Jan 2001 09:23:14 -0800 (PST) Date: Fri, 5 Jan 2001 09:23:14 -0800 (PST) From: "f.johan.beisser" To: freebsd-stable@freebsd.org Subject: SCSI device timeouts. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i've been having a problem as of late, that's not really gone away. from the console log: (da0:ahc0:0:0:0): SCB 0x3 - timed out while idle, SEQADDR == 0x4 STACK == 0x1, 0x174, 0x15e, 0x0 i get one of these errors, and after that, the disk does not recover at all. in this case, it's my main disk. any thoughts or advice on this? -- fjb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 9:26: 4 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 09:26:00 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 9885A37B400 for ; Fri, 5 Jan 2001 09:26:00 -0800 (PST) Received: from [172.17.1.121] (warp-core.skynet.be [195.238.2.25]) by apoq.skynet.be (Postfix) with ESMTP id 4A6EF9A99; Fri, 5 Jan 2001 18:25:57 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200101051644.RAA17887@midten.fast.no> References: <200101051644.RAA17887@midten.fast.no> Date: Fri, 5 Jan 2001 18:25:29 +0100 To: Tor.Egge@fast.no From: Brad Knowles Subject: Re: Problems with corrupted vinum devices... Cc: grog@lemis.com, andy.depetter@ops.skynet.be, freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:44 PM +0100 2001/1/5, Tor.Egge@fast.no wrote: > I suggest increasing INITIAL_DRIVES in vinumvar.h to avoid array > resize and the associated race conditions. When I tried to configure > vinum to use 14 disks yesterday, the machine immediately crashed with > a trap 12 in response to 'vinum create'. I bumped INITIAL_DRIVES to > 16 to avoid the drive array resize that caused the problem. I bumped > INITIAL_SUBDISKS_IN_PLEX too, just to be safe. IIRC, there is a hard limit of 32 physical disks that you can define, but I've only defined eight. So, I'm below both the absolute limit I am aware of, and the limit you apparently ran into. We haven't had any problems with vinum create, so I don't think that increasing INITIAL_DRIVES or INITIAL_SUBDISKS_IN_PLEX is going to help. > To avoid similar races with RAID-5 under high load or with > softupdates, I had to bump INITIAL_LOCKS to avoid a fatal range lock > array resize. We're not using RAID-5, but we are using softupdates. I'll have to look into the code and see if this patch makes sense for us, and I may end up doing a "make update" to bring us up to the latest OS sources, etc... before I try much of anything else. Thanks! -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 9:39:19 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 09:39:13 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 5821537B400 for ; Fri, 5 Jan 2001 09:39:13 -0800 (PST) Received: from [172.17.1.121] (warp-core.skynet.be [195.238.2.25]) by trinity.skynet.be (Postfix) with ESMTP id 43D7C18085; Fri, 5 Jan 2001 18:39:11 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200101051644.RAA17887@midten.fast.no> References: <200101051644.RAA17887@midten.fast.no> Date: Fri, 5 Jan 2001 18:39:02 +0100 To: Tor.Egge@fast.no From: Brad Knowles Subject: Re: Problems with corrupted vinum devices... Cc: grog@lemis.com, andy.depetter@ops.skynet.be, freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:44 PM +0100 2001/1/5, Tor.Egge@fast.no wrote: > diff -ru /tmp/vinum/vinumvar.h ./vinumvar.h > --- /tmp/vinum/vinumvar.h Mon May 22 18:21:37 2000 > +++ ./vinumvar.h Thu Jan 4 19:12:01 2001 > @@ -158,15 +158,15 @@ > * probably too small. > */ > > - INITIAL_DRIVES = 4, > + INITIAL_DRIVES = 16, > INITIAL_VOLUMES = 4, > INITIAL_PLEXES = 8, > INITIAL_SUBDISKS = 16, > - INITIAL_SUBDISKS_IN_PLEX = 4, /* number of >subdisks to allocate to a plex */ > + INITIAL_SUBDISKS_IN_PLEX = 16, /* number of >subdisks to allocate to a plex */ > INITIAL_SUBDISKS_IN_DRIVE = 4, /* number of >subdisks to allocate to a drive */ > INITIAL_DRIVE_FREELIST = 16, /* number of entries >in drive freelist */ > PLEX_REGION_TABLE_SIZE = 8, /* number of >entries in plex region tables */ > - INITIAL_LOCKS = 256, /* number of locks to >allocate to a plex */ > + INITIAL_LOCKS = 4096, /* number of locks to >allocate to a plex */ > MAX_REVIVE_BLOCKSIZE = MAXPHYS, /* maximum revive >block size */ > DEFAULT_REVIVE_BLOCKSIZE = 65536, /* default >revive block size */ > VINUMHOSTNAMELEN = 32, /* host name field in label */ Let's look again at the full comment block before this segment of code: | /* | * the number of object entries to cater for initially, and also the | * value by which they are incremented. It doesn't take long | * to extend them, so theoretically we could start with 1 of each, but | * it's untidy to allocate such small areas. These values are | * probably too small. | */ Theoretically, changing the initial values should have no impact whatsoever on the ability (or lack thereof) to create devices, so long as you're not exceeding the specified maximums. Vinum should automatically extend the necessary data structures beyond these initial defaults, if the need should arise. If vinum isn't doing this, then the code to do those extensions is faulty and it should be fixed instead. The more I think about this, the less I think that this has anything at all to do with either the problems you experienced, or the problems we're having. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 10:17:38 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 10:17:35 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay3.inwind.it (relay3.inwind.it [212.141.53.74]) by hub.freebsd.org (Postfix) with ESMTP id 0A52037B404 for ; Fri, 5 Jan 2001 10:17:30 -0800 (PST) Received: from bartequi.ottodomain.org (62.98.154.81) by relay3.inwind.it (5.1.056) id 3A40BF860032134E; Fri, 5 Jan 2001 19:09:47 +0100 From: Salvo Bartolotta Date: Fri, 05 Jan 2001 18:11:55 GMT Message-ID: <20010105.18115500@bartequi.ottodomain.org> Subject: Re: 4.2-STABLE build fails To: Keith Jones Cc: Janko van Roosmalen , Odhiambo Washington , FBSD-STABLE In-Reply-To: <20010105151843.A6570@moose.bri.hp.com> References: <20010104095534.A51777@poeza.iconnect.co.ke> <20010105151843.A6570@moose.bri.hp.com> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 1/5/01, 4:18:43 PM, Keith Jones wrote=20 regarding Re: 4.2-STABLE build fails: > On Fri, Jan 05, 2001 at 03:04:55PM +0100, Janko van Roosmalen wrote: > > > I've seen much of this discussed here but mine seems to break at t= his > > > point: > > > > > > /usr/obj/usr/src/share/doc/usd/13.viref/troff.core > > > > > > ..and with this msg on the console... > > > > > > Jan 3 18:54:07 alouette /kernel: pid 54505 (troff), uid 0: exited= on > > > signal 11 (core dumped) > > > Jan 3 18:54:07 alouette /kernel: pid 54523 (troff), uid 0: exited= on > > > signal 11 (core dumped) > > > > > > > > > Even a fresh cvsup (after rm-ing all my srcs and usr/obj) does not= =20 help. > > > Any pointer what this 13.viref thing is and how I can sort that ou= t=20 will > > > be highly appreciated. > > > > The FreeBSD faq mentions that signal 11 points to hardware problems.= > Could people please STOP spreading this myth that all Signal 11's=20 during > 'make world' are a result of hardware problems. It is highly=20 misleading.=20 Dear FreeBSD'ers, I have seen a number of programs fail and display other signals as=20 well. However, in those cases, I think it definitely does NOT depend=20 on my hardware. ;-)) In fact, that hardware runs make release (!) operations, it compiles=20 megaports (which megaports take more time than make world itself),=20 and, needless to say, it performs make world operations as well. In the light of the foregoing, I don't worry at all... Just my 2 picoEuro. Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 10:23:54 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 10:23:48 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 44C3B37B404 for ; Fri, 5 Jan 2001 10:23:48 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id KAA01701; Fri, 5 Jan 2001 10:23:31 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda01698; Fri Jan 5 10:23:13 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.1/8.9.1) id f05IN8N01182; Fri, 5 Jan 2001 10:23:08 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdjV1156; Fri Jan 5 10:22:23 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f05IMMZ65134; Fri, 5 Jan 2001 10:22:22 -0800 (PST) Message-Id: <200101051822.f05IMMZ65134@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdr64938; Fri Jan 5 10:21:25 2001 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.2-RELEASE X-Sender: cy To: "f.johan.beisser" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SCSI device timeouts. In-reply-to: Your message of "Fri, 05 Jan 2001 09:23:14 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Jan 2001 10:21:25 -0800 Sender: cy@uumail.gov.bc.ca Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "f.joha n.beisser" writes: > > i've been having a problem as of late, that's not really gone away. > > from the console log: > (da0:ahc0:0:0:0): SCB 0x3 - timed out while idle, SEQADDR == 0x4 > STACK == 0x1, 0x174, 0x15e, 0x0 > > i get one of these errors, and after that, the disk does not recover at > all. in this case, it's my main disk. > > any thoughts or advice on this? I just had this problem on one of my machines at home last week. It turned out that the disk had 6 bad blocks that the disk's firmware would not reassign, probably because the error was a hard error. As I didn't want to purchase another disk (I have a mortgage to pay off), a read/verify to reassign the bad blocks solved the problem. If I had this problem here at work, I'd have replaced the disk. As and aside, if you want to take a look at your SCSI disk's primary (from the factory) and grown (detected by the disk's firmware or through a read/verification) defect lists issue, camcontrol defects 0:0:0 -f phys -P camcontrol defects 0:0:0 -f phys -G Replace 0:0:0 with the physical address of the disk you want to display defects for. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 11: 3:35 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 11:03:31 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from smtp.hccnet.nl (smtp.hccnet.nl [193.172.127.93]) by hub.freebsd.org (Postfix) with ESMTP id EA30737B402 for ; Fri, 5 Jan 2001 11:03:30 -0800 (PST) Received: from parmenides.utp.net by smtp.hccnet.nl via uds82-123.dial.hccnet.nl [193.173.123.82] with ESMTP id UAA20503 (8.8.5/1.13); Fri, 5 Jan 2001 20:03:25 +0100 (MET) Received: by parmenides.utp.net (Postfix, from userid 1005) id 3D84914D; Fri, 5 Jan 2001 20:02:23 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by parmenides.utp.net (Postfix) with ESMTP id EEBCF12E; Fri, 5 Jan 2001 20:02:22 +0100 (CET) Date: Fri, 5 Jan 2001 20:02:22 +0100 (CET) From: Janko van Roosmalen To: Keith Jones Cc: Janko van Roosmalen , Odhiambo Washington , FBSD-STABLE Subject: Re: 4.2-STABLE build fails In-Reply-To: <20010105151843.A6570@moose.bri.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Jan 2001, Keith Jones wrote: > On Fri, Jan 05, 2001 at 03:04:55PM +0100, Janko van Roosmalen wrote: > > > > I've seen much of this discussed here but mine seems to break at this > > > point: > > > > > > /usr/obj/usr/src/share/doc/usd/13.viref/troff.core > > > > > > ..and with this msg on the console... > > > > > > Jan 3 18:54:07 alouette /kernel: pid 54505 (troff), uid 0: exited on > > > signal 11 (core dumped) > > > Jan 3 18:54:07 alouette /kernel: pid 54523 (troff), uid 0: exited on > > > signal 11 (core dumped) > > > > > > > > > Even a fresh cvsup (after rm-ing all my srcs and usr/obj) does not help. > > > Any pointer what this 13.viref thing is and how I can sort that out will > > > be highly appreciated. > > > > The FreeBSD faq mentions that signal 11 points to hardware problems. > > Could people please STOP spreading this myth that all Signal 11's during > 'make world' are a result of hardware problems. It is highly misleading. How > would you feel if you acted on this advice and shelled out your hard-earned > cash for new hardware only to find that it was a software problem after all? > > The chances are that if a signal occurs as the result of running a particular > program (in this case 'troff'), it's likely to be the version of that program > or a shared library on which it depends that is broken somehow on the user's > machine, not the user's hardware. > > You could try manually recompiling and installing 'troff' et al. (located > in the directory /usr/src/contrib/groff) then rerunning 'make world'. > -- > Keith Jones > E-Business Service Introduction, GBIT-EMEA (Bristol) > E: keith_jones@non.hp.com > T: [+44 117] 312-7602 > > I don't speak for Hewlett-Packard. I think the faq is rather balanced regarding this and points to slow memory, and recommends adapting memory timings in the BIOS. It could be the temperature. Odhiambo lives in Kenia. It is summer there. Recompiling your system in those climatic conditions is the equivalent of a burn-in test. I remember a post from someone who reported a hefty increase increase of the CPU temperature while building world. Many computer "hardware" problems can be fixed by just refitting cables, checking if they have sharp bends, pressing chips in sockets or cleaning card contacts with a pencil eraser if you do not have a contact enhancing spray. Another source can be power. There could have been a surge or sag. Years ago I worked as a temp in a shop where they anodized and welded aluminium. They had some weird problems with their Apple II which were solved by using an UPS. Notwithstanding this, you still have a point. Maybe time to adjust the FAQ?. I am not a native speaker so I have an excuse to not volunteer ;) ===Janko van Roosmalen - Vught - Netherlands=== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 15:47:56 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 15:47:54 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id AD66D37B400 for ; Fri, 5 Jan 2001 15:47:52 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id BBD166A918; Sat, 6 Jan 2001 10:17:50 +1030 (CST) Date: Sat, 6 Jan 2001 10:17:50 +1030 From: Greg Lehey To: Tor.Egge@fast.no Cc: blk@skynet.be, andy.depetter@ops.skynet.be, freebsd-stable@FreeBSD.ORG Subject: Re: Problems with corrupted vinum devices... Message-ID: <20010106101750.Z48589@wantadilla.lemis.com> References: <200101051644.RAA17887@midten.fast.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101051644.RAA17887@midten.fast.no>; from Tor.Egge@fast.no on Fri, Jan 05, 2001 at 05:44:02PM +0100 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 5 January 2001 at 17:44:02 +0100, Tor.Egge@fast.no wrote: >> However, at some point within the next couple of hours (we're not >> quite sure when), the machine crashed, and vinum failed to come up on >> the reboot. We had to comment out the /etc/fstab entries that >> referred to the vinum volumes, and since then have been trying to >> debug the problems as to why vinum can't find or start any devices at >> all. > > I suggest increasing INITIAL_DRIVES in vinumvar.h to avoid array > resize and the associated race conditions. When I tried to configure > vinum to use 14 disks yesterday, the machine immediately crashed with > a trap 12 in response to 'vinum create'. I bumped INITIAL_DRIVES to > 16 to avoid the drive array resize that caused the problem. I bumped > INITIAL_SUBDISKS_IN_PLEX too, just to be safe. I don't think these issues are related. I'm still trying to figure out what Brad did, but my best guess is some problem with the disk labelling. > To avoid similar races with RAID-5 under high load or with > softupdates, I had to bump INITIAL_LOCKS to avoid a fatal range lock > array resize. > > For 4.2-STABLE, I'm currently using the following patch to implement > the workarounds: Wait for me to test it and I'll commit it. At this stage I don't think there's any great advantage in distributing patches. 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-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 15:49:56 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 15:49:54 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id E4E6E37B400 for ; Fri, 5 Jan 2001 15:49:52 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 8A8126A90D; Sat, 6 Jan 2001 10:19:51 +1030 (CST) Date: Sat, 6 Jan 2001 10:19:51 +1030 From: Greg Lehey To: Brad Knowles Cc: Tor.Egge@fast.no, andy.depetter@ops.skynet.be, freebsd-stable@FreeBSD.ORG Subject: Re: Problems with corrupted vinum devices... Message-ID: <20010106101951.A48589@wantadilla.lemis.com> References: <200101051644.RAA17887@midten.fast.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from blk@skynet.be on Fri, Jan 05, 2001 at 06:25:29PM +0100 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 5 January 2001 at 18:25:29 +0100, Brad Knowles wrote: > At 5:44 PM +0100 2001/1/5, Tor.Egge@fast.no wrote: > >> I suggest increasing INITIAL_DRIVES in vinumvar.h to avoid array >> resize and the associated race conditions. When I tried to configure >> vinum to use 14 disks yesterday, the machine immediately crashed with >> a trap 12 in response to 'vinum create'. I bumped INITIAL_DRIVES to >> 16 to avoid the drive array resize that caused the problem. I bumped >> INITIAL_SUBDISKS_IN_PLEX too, just to be safe. > > IIRC, there is a hard limit of 32 physical disks that you can > define, but I've only defined eight. I've removed that limit in -CURRENT. >> To avoid similar races with RAID-5 under high load or with >> softupdates, I had to bump INITIAL_LOCKS to avoid a fatal range lock >> array resize. > > We're not using RAID-5, but we are using softupdates. I'll have > to look into the code and see if this patch makes sense for us, and I > may end up doing a "make update" to bring us up to the latest OS > sources, etc... before I try much of anything else. No, the patch addresses a different problem. This is also a configuration problem, so it has nothing to do with soft updates. 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-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 15:52: 3 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 15:51:59 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7FF3737B400 for ; Fri, 5 Jan 2001 15:51:58 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 24C306A90D; Sat, 6 Jan 2001 10:21:57 +1030 (CST) Date: Sat, 6 Jan 2001 10:21:57 +1030 From: Greg Lehey To: Brad Knowles Cc: Tor.Egge@fast.no, andy.depetter@ops.skynet.be, freebsd-stable@FreeBSD.ORG Subject: Re: Problems with corrupted vinum devices... Message-ID: <20010106102157.B48589@wantadilla.lemis.com> References: <200101051644.RAA17887@midten.fast.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from blk@skynet.be on Fri, Jan 05, 2001 at 06:39:02PM +0100 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 5 January 2001 at 18:39:02 +0100, Brad Knowles wrote: > At 5:44 PM +0100 2001/1/5, Tor.Egge@fast.no wrote: > >> diff -ru /tmp/vinum/vinumvar.h ./vinumvar.h >> --- /tmp/vinum/vinumvar.h Mon May 22 18:21:37 2000 >> +++ ./vinumvar.h Thu Jan 4 19:12:01 2001 > Let's look again at the full comment block before this segment of code: > >> /* >> * the number of object entries to cater for initially, and also the >> * value by which they are incremented. It doesn't take long >> * to extend them, so theoretically we could start with 1 of each, but >> * it's untidy to allocate such small areas. These values are >> * probably too small. >> */ > > Theoretically, changing the initial values should have no impact > whatsoever on the ability (or lack thereof) to create devices, so > long as you're not exceeding the specified maximums. Vinum should > automatically extend the necessary data structures beyond these > initial defaults, if the need should arise. If vinum isn't doing > this, then the code to do those extensions is faulty and it should be > fixed instead. Correct. It's broken, and Tor's patch is a workaround. > The more I think about this, the less I think that this has > anything at all to do with either the problems you experienced, or > the problems we're having. I'm quite sure they're related to the problems Tor has been experiencing. But, as I've said, they're different. 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-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 15:53:25 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 15:53:23 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from anarchy.io.com (anarchy.io.com [199.170.88.101]) by hub.freebsd.org (Postfix) with ESMTP id 222E737B400 for ; Fri, 5 Jan 2001 15:53:23 -0800 (PST) Received: from dumpster.io.com.io.com (aus-as3-069.io.com [208.2.106.69]) by anarchy.io.com (8.9.3/8.9.3) with SMTP id RAA14659 for ; Fri, 5 Jan 2001 17:53:20 -0600 To: freebsd-stable@FreeBSD.ORG Subject: xfm port can't find Xaw3d.6 From: Lars Eighner Date: 05 Jan 2001 18:03:22 -0600 Message-ID: <86itntv96c.fsf@dumpster.io.com> Lines: 21 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Capitol Reef" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I try to make install xfm, it complains that it cannot find Xaw3d.6 and dies. Well, it is right. There is no Xaw3d.6 or libXaw3d.6 . I have deinstalled and reinstalled Xaw3d-1.5. I have cvsupped the ports. I have even deleted the whole ports tree and downloaded a fresh ports.tar.gz. Nothing seems to work. Either the port of xfm cannot find Xaw3d at all, makes it, but cannot install it because it is already installed - which causes the make of xfm die, or it cannot find Xaw3d.6 and dies. I have forced pkg registration of Xaw3d-1.5, I have manually deinstalled Xaw3d-1.5 before reinstalling. Nothing seems to work. I did follow the instructions in the Xaw3d port regarding moving the old widgets to Xaw2d and creating a symbolic link to Xaw3d. So, what's the deal? -- Lars Eighner eighner@io.com http://www.io.com/~eighner/ Give me chastity and continence, but not just now. -- St. Augustine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 16:28: 8 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 16:28:06 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id E67C037B400 for ; Fri, 5 Jan 2001 16:28:04 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 98EAE6A90D; Sat, 6 Jan 2001 10:58:02 +1030 (CST) Date: Sat, 6 Jan 2001 10:58:02 +1030 From: Greg Lehey To: Daniel Lang Cc: dxoch , freebsd-stable@FreeBSD.ORG Subject: Loading Vinum at boot time (was: Vinum Question) Message-ID: <20010106105802.E48589@wantadilla.lemis.com> References: <20010105141224.E17176@atrbg11.informatik.tu-muenchen.de> <3A55D971.42FB0B16@escape.gr> <20010105154507.F17176@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010105154507.F17176@atrbg11.informatik.tu-muenchen.de>; from dl@leo.org on Fri, Jan 05, 2001 at 03:45:09PM +0000 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 5 January 2001 at 15:45:09 +0000, Daniel Lang wrote: > dxoch wrote on Fri, Jan 05, 2001 at 03:21:55PM +0000: >>> Although loader is more sophisticated, it does not know about vinum, >> >> I thought the same myself byt, in that case, >> what is the purpose of the vinum_load option ? > > As I said, to load the module before booting the kernel. > Just as the other modules. As the module is loaded into > the _kernel_ not into 'loader' or anything you cannot use it > until the kernel booted. > > I guess it makes little difference, if you load the klm at > this stage or later. Nearly all parts of the system, that > need a specific module, load it on demand, if its not present > at startup (ipf doesn't unfortunately ;)). And you can load > many via /etc/rc* > > There may be situations in which it is required or at least > of advantage if the module is loaded before booting. > > Although you can set the root-device in loader.conf, it > probably won't work to set it to a vinum device. Well, the obvious way to find out whether Vinum supports a root volume is to read the documentation. The answer is "not yet". When it's ready (maybe soon), we'll obviously need to load Vinum along with the kernel. Then we'll need the parameter. So why is it in there now? Because there's an entry for *every* kld in loader.conf. 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-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 17:53:10 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 17:53:08 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 6AC0437B400 for ; Fri, 5 Jan 2001 17:53:06 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 93A806A90D; Sat, 6 Jan 2001 12:23:04 +1030 (CST) Date: Sat, 6 Jan 2001 12:23:04 +1030 From: Greg Lehey To: Brad Knowles Cc: Andy De Petter , FreeBSD-STABLE Mailing List Subject: Re: Problems with corrupted vinum devices... Message-ID: <20010106122304.I48589@wantadilla.lemis.com> 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 blk@skynet.be on Fri, Jan 05, 2001 at 05:04:47PM +0100 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 5 January 2001 at 17:04:47 +0100, Brad Knowles wrote: > So, instead, I just copied all the data from the two filesystems > that had been mirrored and striped, and then did a "resetconfig". I > then re-created the vinum configuration with exactly the same > parameters as I had used the first time, and was able to get vinum to > init and bring online the "restored" disk devices and rebuild the > mirrors, etc.... > > We then put filesystems on everything, and copied all the files > back to their correct locations. So far as we could tell, this > seemed to have worked perfectly, and we were done. > > However, at some point within the next couple of hours (we're not > quite sure when), the machine crashed, and vinum failed to come up on > the reboot. We had to comment out the /etc/fstab entries that > referred to the vinum volumes, and since then have been trying to > debug the problems as to why vinum can't find or start any devices at > all. > > Following the instructions at > , I > tried pulling the file log information as specified. The exact > command I used was (line-wrapped for readability): > > $ for i in /dev/da2s1e /dev/da2s2e /dev/da3s1e \ > /dev/da3s2e /dev/da4s1e /dev/da4s2e /dev/da5s1e \ > /dev/da5s2e; do (dd if=$i skip=8 count=6|tr -d \ > '\000-\011\200-\377'; echo) >> brad.log; done > > The first two disk devices (da2 & da3) produced gibberish. The > last two disk devices (da4 & da5) produced reasonably intelligible > output, but instead of "IN VINO" as the first seven characters, I got > "NO VINO" instead. Well, I've taken a look at the log file, and in fact all the drives except the first two have "NO VINO", which is the magic number for deleted Vinum drives. This is probably the result of a resetconfig, and it completely explains the following problems. I've just checked the source code, and it looks as if I don't log whether the configuration updates are enabled at all. There's no reason to think that they should not be based on the other information you give, but evidently we never got the configuration to disk. Did you get any error messages? Anyway, the good news is that the data is almost certainly still there. You should be able to recreate the volumes with the same configuration file you used the first time round (don't use resetconfig first). If the second plexes were up when the system crashed, you should use the setupstate keyword for the volumes to indicate that. 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-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 18:12:23 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 18:12:19 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 48DD137B69C for ; Fri, 5 Jan 2001 18:12:13 -0800 (PST) Received: from [172.17.1.121] (warp-core.skynet.be [195.238.2.25]) by trinity.skynet.be (Postfix) with ESMTP id 91DFF18455; Sat, 6 Jan 2001 03:12:02 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20010106122304.I48589@wantadilla.lemis.com> References: <20010106122304.I48589@wantadilla.lemis.com> Date: Sat, 6 Jan 2001 03:11:20 +0100 To: Greg Lehey From: Brad Knowles Subject: Re: Problems with corrupted vinum devices... Cc: Andy De Petter , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:23 PM +1030 2001/1/6, Greg Lehey wrote: > Well, I've taken a look at the log file, and in fact all the drives > except the first two have "NO VINO", which is the magic number for > deleted Vinum drives. This is probably the result of a resetconfig, > and it completely explains the following problems. I counted only four instances of "NO VINO", which I take to mean that the old devices (da4s1, da4s2, da5s1, and da5s2) were all relatively clean, while the new devices were all corrupt. > I've just checked the source code, and it looks as if I don't log > whether the configuration updates are enabled at all. There's no > reason to think that they should not be based on the other information > you give, but evidently we never got the configuration to disk. Did > you get any error messages? No, everything seemed to work just fine -- vinum showed the sub disks, plexes, and volumes as being up, I could create filesystems, etc.... > Anyway, the good news is that the data is almost certainly still > there. You should be able to recreate the volumes with the same > configuration file you used the first time round (don't use > resetconfig first). If the second plexes were up when the system > crashed, you should use the setupstate keyword for the volumes to > indicate that. Well, we've already deleted and re-created the devices once, and now we can't even get vinum to start because it can't read the supposedly existing devices. I am at a loss to understand how we would recreate the devices another time, on top of the old configurations (and hopefully be able to retain all the data, etc...). Is there something I'm missing? Maybe you could explain this process in a little more detail? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 22:25: 6 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 22:25:03 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hobbiton.shire.net (frogmorton.shire.net [204.228.145.136]) by hub.freebsd.org (Postfix) with ESMTP id DA90D37B400 for ; Fri, 5 Jan 2001 22:25:02 -0800 (PST) Received: from [216.64.45.172] (helo=[192.168.99.123]) by hobbiton.shire.net with esmtp (Exim 2.04 #5) id 14Emml-000Kn1-00 for freebsd-stable@FreeBSD.ORG; Fri, 5 Jan 2001 23:25:03 -0700 Date: Sat, 06 Jan 2001 01:17:43 -0500 From: "Chad Leigh, Pengar Enterprises, Inc & Shire.Net LLC" Reply-To: chad@pengar.com To: freebsd-stable@FreeBSD.ORG Subject: cannot ftp into box after 4.2-STABLE upgrade Message-ID: <3786286823.978743863@[192.168.99.123]> In-Reply-To: <200101051822.f05IMMZ65134@cwsys.cwsent.com> X-Mailer: Mulberry/2.0.5 (Win32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========3786292645==========" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==========3786292645========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi All I had a 4.0 box that I upgraded to 4.2-STABLE. It is an internal test = box. Now I cannot ftp into the box. It does not matter if I use inetd to start = ftpd or if I remove it from inetd and start it by hand. I start it with = ftpd -D -d -l and I don't get any log messages anywhere (and I added ftp.* = and *.* to syslog.conf). If I try and ftp into the box I get (immediately) 421 Service not available, remote server has closed connection. If I look at the netstat -t is listening on *.ftp . A ps -ax | grep ftpd = shows it running. The above message also comes when I start ftpd from = inetd without -wW . I have tried everything. It never even asks for a username. /etc/ftpusers = does not get used in that case. ftp was working on this machine before the = upgrade. Any thoughts or comments to help me out? Thanks Chad Pengar Enterprises, Inc. and Shire.Net LLC Web and Macintosh Consulting -- full service web hosting Chad Leigh chad@pengar.com chad@shire.net --==========3786292645========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: Mulberry PGP Plugin v2.0 Comment: processed by Mulberry PGP Plugin iQA/AwUBOla4hzrujlJKZPK5EQKB2ACgreqOjttYAm3qe+ijZhf1FimCNhsAmwX7 SlfGfY+pATiqx/0B6AX9kWsh =GjOy -----END PGP SIGNATURE----- --==========3786292645==========-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 5 23:38: 6 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 23:38:03 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9F7BC37B400 for ; Fri, 5 Jan 2001 23:38:03 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA06897; Fri, 5 Jan 2001 23:37:52 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f067bos20510; Fri, 5 Jan 2001 23:37:50 -0800 (PST) (envelope-from obrien) Date: Fri, 5 Jan 2001 23:37:49 -0800 From: "David O'Brien" To: stable@freebsd.org Subject: Re: C++ and threads Message-ID: <20010105233749.A20484@dragon.nuxi.com> Reply-To: stable@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 fjoe@newst.net on Fri, Jan 05, 2001 at 04:39:37AM +0600 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: obrien@NUXI.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 05, 2001 at 04:39:37AM +0600, Max Khon wrote: > I have cvsupped to latest -stable and rebuilt world with latest patches > posted by David O'Brien to freebsd-stable@ mailing list. I have committed all the fixes I have to -current. It will be MFCed on the fast track. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 6 4:55:51 2001 From owner-freebsd-stable@FreeBSD.ORG Sat Jan 6 04:55:49 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mail.clones.com (unknown [216.70.178.182]) by hub.freebsd.org (Postfix) with ESMTP id C0DDD37B400 for ; Sat, 6 Jan 2001 04:55:48 -0800 (PST) Received: from localhost (gross@localhost) by mail.clones.com (8.9.3/8.9.3) with ESMTP id EAA31077; Sat, 6 Jan 2001 04:56:58 -0800 Date: Sat, 6 Jan 2001 04:56:58 -0800 (PST) From: Glendon Gross To: "Chad Leigh, Pengar Enterprises, Inc & Shire.Net LLC" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: cannot ftp into box after 4.2-STABLE upgrade In-Reply-To: <3786286823.978743863@[192.168.99.123]> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have you tried adding the hostname you are connecting from to /etc/hosts_allow? I recall having a similar problem when I first installed FreeBSD. Also, you may need '"inetd_enable = "YES"' in /etc/rc.conf. On Sat, 6 Jan 2001, Chad Leigh, Pengar Enterprises, Inc & Shire.Net LLC wrote: > Hi All > > I had a 4.0 box that I upgraded to 4.2-STABLE. It is an internal test box. > > Now I cannot ftp into the box. It does not matter if I use inetd to start ftpd or if I remove it from inetd and start it by hand. I start it with ftpd -D -d -l and I don't get any log messages anywhere (and I added ftp.* and *.* to syslog.conf). > > If I try and ftp into the box I get (immediately) > > 421 Service not available, remote server has closed connection. > > If I look at the netstat -t is listening on *.ftp . A ps -ax | grep ftpd shows it running. The above message also comes when I start ftpd from inetd without -wW . > > I have tried everything. It never even asks for a username. /etc/ftpusers > does not get used in that case. ftp was working on this machine before the > upgrade. > > Any thoughts or comments to help me out? > > Thanks > Chad > > > Pengar Enterprises, Inc. and Shire.Net LLC > Web and Macintosh Consulting -- full service web hosting > Chad Leigh > chad@pengar.com chad@shire.net > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 6 6:59:33 2001 From owner-freebsd-stable@FreeBSD.ORG Sat Jan 6 06:59:31 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id F185A37B400 for ; Sat, 6 Jan 2001 06:59:29 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id QAA03461; Sat, 6 Jan 2001 16:43:36 +0200 To: Daniel Lang Subject: Re: Vinum Question Message-ID: <978792215.3a572f1802f5c@webmail.harmonic.co.il> Date: Sat, 06 Jan 2001 16:43:36 +0200 (IST) From: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG References: <20010105141224.E17176@atrbg11.informatik.tu-muenchen.de> In-Reply-To: <20010105141224.E17176@atrbg11.informatik.tu-muenchen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Daniel Lang : [..] > If you need average security agains disk-crashes, you can keep your > data in vinum-volumes and back up the root-partition on a regular > basis e.g. with dd. If you really need more security, go and > buy a SCSI-SCSI raid-controller, which is seen as one or more > single disks, independent of its real disks and configuration. > You save yourself lots of trouble. You're almost right. I used the similar solution when I used vinum raid-5. The only "but" is that dd(1) cannot be used. I got away with newfs,dump,restore. Also, the system disk is "dumb", it can be copied once and saved offline. However, if the "almost-hot" backup is needed, nightly mirror is a feasible solution. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 6 7: 2:49 2001 From owner-freebsd-stable@FreeBSD.ORG Sat Jan 6 07:02:47 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id 5845537B400 for ; Sat, 6 Jan 2001 07:02:46 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id QAA03464; Sat, 6 Jan 2001 16:47:06 +0200 To: Daniel Lang Subject: Re: Vinum Question Message-ID: <978792426.3a572fea1dd0e@webmail.harmonic.co.il> Date: Sat, 06 Jan 2001 16:47:06 +0200 (IST) From: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG References: <20010105141224.E17176@atrbg11.informatik.tu-muenchen.de> <3A55D971.42FB0B16@escape.gr> <20010105154507.F17176@atrbg11.informatik.tu-muenchen.de> In-Reply-To: <20010105154507.F17176@atrbg11.informatik.tu-muenchen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Daniel Lang : [..] > > > Although I guess you could immediately load the vinum.ko, > > > before booting the kernel (i.e. load the kernel, load the > > > module along with other modules like splash, then boot the kernel), > > > but this does not help you to boot from a vinum device. > [..] > > > Although loader is more sophisticated, it does not know about vinum, > > > > I thought the same myself byt, in that case, > > what is the purpose of the vinum_load option ? > As I said, to load the module before booting the kernel. > Just as the other modules. As the module is loaded into > the _kernel_ not into 'loader' or anything you cannot use it > until the kernel booted. Or to put it this way: the kernel or/and modules have to be loaded from filesystem which resides on some *device*. The current booting process, AFAIK, doesn't know about vinum devices. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 6 7:23: 8 2001 From owner-freebsd-stable@FreeBSD.ORG Sat Jan 6 07:23:05 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hobbiton.shire.net (frogmorton.shire.net [204.228.145.136]) by hub.freebsd.org (Postfix) with ESMTP id E84B837B400 for ; Sat, 6 Jan 2001 07:23:04 -0800 (PST) Received: from [216.64.45.172] (helo=[192.168.99.123]) by hobbiton.shire.net with esmtp (Exim 2.04 #5) id 14EvBP-0000uR-00; Sat, 6 Jan 2001 08:23:04 -0700 Date: Sat, 06 Jan 2001 10:15:40 -0500 From: "Chad Leigh, Pengar Enterprises, Inc & Shire.Net LLC" Reply-To: chad@pengar.com To: Glendon Gross Cc: "Chad Leigh, Pengar Enterprises, Inc & Shire.Net LLC" , freebsd-stable@FreeBSD.ORG Subject: Re: cannot ftp into box after 4.2-STABLE upgrade Message-ID: <3818564761.978776140@[192.168.99.123]> In-Reply-To: X-Mailer: Mulberry/2.0.5 (Win32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========3818574922==========" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==========3818574922========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Yes. The system ships with a /etc/hosts.allow (which I copied to = hosts_allow)which it claims is used by the wrapping service in inetd. I = turned off -wW on inetd so that that file would not matter. Telnet then = started to work. But not ftp. So I got rid of ftp altogether in inetd. = You don't need to start ftpd through inetd. I start ftpd with a -D now for = daemon use and it still gives the same problem. Thanks Chad --On Saturday, January 06, 2001 4:56 AM -0800 Glendon Gross = wrote: > > Have you tried adding the hostname you are connecting from to > /etc/hosts_allow? I recall having a similar problem when I first > installed FreeBSD. Also, you may need '"inetd_enable =3D "YES"' in > /etc/rc.conf. > > On Sat, 6 Jan 2001, Chad Leigh, Pengar Enterprises, Inc & Shire.Net LLC > wrote: > >> Hi All >> >> I had a 4.0 box that I upgraded to 4.2-STABLE. It is an internal test >> box. >> >> Now I cannot ftp into the box. It does not matter if I use inetd to >> start ftpd or if I remove it from inetd and start it by hand. I start >> it with ftpd -D -d -l and I don't get any log messages anywhere (and I >> added ftp.* and *.* to syslog.conf). >> >> If I try and ftp into the box I get (immediately) >> >> 421 Service not available, remote server has closed connection. >> >> If I look at the netstat -t is listening on *.ftp . A ps -ax | grep ftpd >> shows it running. The above message also comes when I start ftpd from >> inetd without -wW . >> >> I have tried everything. It never even asks for a username. >> /etc/ftpusers does not get used in that case. ftp was working on this >> machine before the upgrade. >> >> Any thoughts or comments to help me out? >> >> Thanks >> Chad >> >> >> Pengar Enterprises, Inc. and Shire.Net LLC >> Web and Macintosh Consulting -- full service web hosting >> Chad Leigh >> chad@pengar.com chad@shire.net >> > Pengar Enterprises, Inc. and Shire.Net LLC Web and Macintosh Consulting -- full service web hosting Chad Leigh chad@pengar.com chad@shire.net --==========3818574922========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: Mulberry PGP Plugin v2.0 Comment: processed by Mulberry PGP Plugin iQA/AwUBOlc2nDrujlJKZPK5EQJXKgCg5Uv64eYyHNs0ETGisqK5sa8V1uUAoNQO ZDstBVnOpjdkam48rLsfjGVE =ARDF -----END PGP SIGNATURE----- --==========3818574922==========-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 6 11: 8:28 2001 From owner-freebsd-stable@FreeBSD.ORG Sat Jan 6 11:08:25 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 2D5D237B400 for ; Sat, 6 Jan 2001 11:08:25 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f06J8LI13763; Sat, 6 Jan 2001 11:08:21 -0800 (PST) (envelope-from dillon) Date: Sat, 6 Jan 2001 11:08:21 -0800 (PST) From: Matt Dillon Message-Id: <200101061908.f06J8LI13763@earth.backplane.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: NFSv3 O_EXCL file create - protocol spec & solution (was Re: Bug in NFSv3 client) References: <20010103155533.B71238@math.uic.edu> <200101032243.f03Mhar51440@earth.backplane.com> <200101032308.f03N84f51776@earth.backplane.com> <200101032322.f03NMTK51973@earth.backplane.com> <200101040754.f047sUW55674@earth.backplane.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The fix has been MFCd' to -stable. I would like to MFC the fix to 3.x as well since that was what the original PR was filed under, but I have no 3.x machines to test it on. If someone with a 3.x machine and source tree could test the patch included at the end and give me a yah or nay, I'd appreciate it. The patch is the same as for 4.x and 5.x except vfs_timestamp() turns into getnanotime(). To test, run the patch on a 3.x NFS client. The NFS server can be any FreeBSD release. Create a file using this program: #include #include int main(int ac, char **av) { int fd; fd = open("test.dat", O_CREAT|O_TRUNC|O_EXCL|O_RDWR, 0644); printf("fd = %d\n", fd); exit(0); } And then 'ls -lua test.dat'. To repeat the test, remove test.dat and run the program again. Without the patch the file access time shown by ls should be garbage. With the patch it should be reasonable. Thanks, -Matt Index: nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.116.2.8 diff -u -r1.116.2.8 nfs_vnops.c --- nfs_vnops.c 1999/12/12 06:52:34 1.116.2.8 +++ nfs_vnops.c 2001/01/06 19:02:44 @@ -1407,8 +1407,21 @@ } if (newvp) vput(newvp); - } else if (v3 && (fmode & O_EXCL)) + } else if (v3 && (fmode & O_EXCL)) { + /* + * We are normally called with only a partially initialized + * VAP. Since the NFSv3 spec says that server may use the + * file attributes to store the verifier, the spec requires + * us to do a SETATTR RPC. FreeBSD servers store the verifier + * in atime, but we can't really assume that all servers will + * so we ensure that our SETATTR sets both atime and mtime. + */ + if (vap->va_mtime.tv_sec == VNOVAL) + getnanotime(&vap->va_mtime); + if (vap->va_atime.tv_sec == VNOVAL) + vap->va_atime = vap->va_mtime; error = nfs_setattrrpc(newvp, vap, cnp->cn_cred, cnp->cn_proc); + } if (!error) { if (cnp->cn_flags & MAKEENTRY) cache_enter(dvp, newvp, cnp); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 6 11:37:54 2001 From owner-freebsd-stable@FreeBSD.ORG Sat Jan 6 11:37:52 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 053D237B400 for ; Sat, 6 Jan 2001 11:37:52 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1501) id 599F513613; Sat, 6 Jan 2001 14:37:51 -0500 (EST) Date: Sat, 6 Jan 2001 14:37:51 -0500 From: Chris Faulhaber To: Matt Dillon Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFSv3 O_EXCL file create - protocol spec & solution (was Re: Bug in NFSv3 client) Message-ID: <20010106143751.D43120@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , Matt Dillon , freebsd-stable@FreeBSD.ORG References: <20010103155533.B71238@math.uic.edu> <200101032243.f03Mhar51440@earth.backplane.com> <200101032308.f03N84f51776@earth.backplane.com> <200101032322.f03NMTK51973@earth.backplane.com> <200101040754.f047sUW55674@earth.backplane.com> <200101061908.f06J8LI13763@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101061908.f06J8LI13763@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Jan 06, 2001 at 11:08:21AM -0800 Sender: cdf.lists@fxp.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 06, 2001 at 11:08:21AM -0800, Matt Dillon wrote: > The fix has been MFCd' to -stable. > > I would like to MFC the fix to 3.x as well since that was what the > original PR was filed under, but I have no 3.x machines to test it on. > If someone with a 3.x machine and source tree could test > the patch included at the end and give me a yah or nay, I'd appreciate it. > FreeBSD 3.5-STABLE (MUMBLE) #1: Sat Jan 6 14:32:48 EST 2001 before: $ ls -lua -rw-r--r-- 1 jedgar jedgar 0 Feb 1 2005 test.dat after: $ ls -lua -rw-r--r-- 1 jedgar jedgar 0 Jan 6 14:35 test.dat -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 6 11:46:39 2001 From owner-freebsd-stable@FreeBSD.ORG Sat Jan 6 11:46:36 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 0DC0A37B402 for ; Sat, 6 Jan 2001 11:46:36 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f06JkVo13923; Sat, 6 Jan 2001 11:46:31 -0800 (PST) (envelope-from dillon) Date: Sat, 6 Jan 2001 11:46:31 -0800 (PST) From: Matt Dillon Message-Id: <200101061946.f06JkVo13923@earth.backplane.com> To: Chris Faulhaber Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFSv3 O_EXCL file create - protocol spec & solution (was Re: Bug in NFSv3 client) References: <20010103155533.B71238@math.uic.edu> <200101032243.f03Mhar51440@earth.backplane.com> <200101032308.f03N84f51776@earth.backplane.com> <200101032322.f03NMTK51973@earth.backplane.com> <200101040754.f047sUW55674@earth.backplane.com> <200101061908.f06J8LI13763@earth.backplane.com> <20010106143751.D43120@peitho.fxp.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :FreeBSD 3.5-STABLE (MUMBLE) #1: Sat Jan 6 14:32:48 EST 2001 : :before: :$ ls -lua :-rw-r--r-- 1 jedgar jedgar 0 Feb 1 2005 test.dat : :after: :$ ls -lua :-rw-r--r-- 1 jedgar jedgar 0 Jan 6 14:35 test.dat : :-- :Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org Wow, that was fast! Ok, I've MFC'd it. It should show up in the cvsup's in an hour or so. Thanks! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 6 21:19:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7E85737B400 for ; Sat, 6 Jan 2001 21:19:02 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA35885; Sat, 6 Jan 2001 22:18:59 -0700 (MST) (envelope-from ken) Date: Sat, 6 Jan 2001 22:18:59 -0700 From: "Kenneth D. Merry" To: "f.johan.beisser" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SCSI device timeouts. Message-ID: <20010106221859.A35273@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from jan@caustic.org on Fri, Jan 05, 2001 at 09:23:14AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 05, 2001 at 09:23:14 -0800, f.johan.beisser wrote: > > i've been having a problem as of late, that's not really gone away. > > from the console log: > (da0:ahc0:0:0:0): SCB 0x3 - timed out while idle, SEQADDR == 0x4 > STACK == 0x1, 0x174, 0x15e, 0x0 > > i get one of these errors, and after that, the disk does not recover at > all. in this case, it's my main disk. > > any thoughts or advice on this? Timed out while idle generally means that we sent a command to the disk, but it didn't respond before the timeout for that command fired. In the case of reads and writes from the da(4) driver, the timeout is 60 seconds, which is plenty long enough for any disk. So it's likely your disk is going "out to lunch" and not coming back. What sort of disk is it? You might consider replacing it. (Assuming you've checked your cabling, termination, etc.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message