From owner-freebsd-current Sun Jan 9 0:21:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by hub.freebsd.org (Postfix) with ESMTP id E8B0C15189 for ; Sun, 9 Jan 2000 00:20:59 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 127Dar-000LW2-0W for current@freebsd.org; Sun, 9 Jan 2000 08:20:58 +0000 Received: from nenya (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (Postfix) with SMTP id D86C1D913 for ; Sun, 9 Jan 2000 08:22:29 +0000 (GMT) Message-ID: <001001bf5a7a$c4b88440$0304020a@rings> From: "Cameron Grant" To: References: <20000109071636.AFD3B1CA0@overcee.netplex.com.au> Subject: neomagic 256av/256zx audio Date: Sun, 9 Jan 2000 08:23:11 -0000 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.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i have just committed a driver for the neomagic chips. please test and post results. - cameron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 0:35:58 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 7196014CBE; Sun, 9 Jan 2000 00:35:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E1C61CD821; Sun, 9 Jan 2000 00:35:54 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 9 Jan 2000 00:35:54 -0800 (PST) From: Kris Kennaway To: Leif Neland Cc: Yoshinobu Inoue , freebsd-current@FreeBSD.ORG Subject: Re: IPSEC broken, was Re: IPv6 testing...willing to help In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 9 Jan 2000, Leif Neland wrote: > Kernel build stops with "Don't know how to make sha1.c". > sha was removed a few days ago, a "heads up" said. Different instance - that was just SHA1-format passwords. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 1:23: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust252.tnt2.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0A01A14C43; Sun, 9 Jan 2000 01:22:44 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Sun, 9 Jan 2000 04:21:47 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: ATA atapi-all.c problems/fixes/cleanups In-Reply-To: <200001060904.KAA90935@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Jan 2000, Soren Schmidt wrote: > You should respect the blocksize when talking to a device with a > fixed blocklength, dont write ! % blocksize blocks to the device.. > By the way, I think I've redone this enough times that it's all correct. It's 32-bit support _outside_ of the overrun/underrun loops in atapi-all, a bugfix for atapi-cd, and the full support for weird overrun/underrun sizes. The drive is still not working, but I know this has nothing to do with it. Think you might use this at all? I think it's important for stability if the driver handles overruns and underruns well, and this makes everything full-block-size-sized. > -Søren -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' Index: atapi-all.c =================================================================== RCS file: /usr2/ncvs/src/sys/dev/ata/atapi-all.c,v retrieving revision 1.33 diff -u -r1.33 atapi-all.c --- atapi-all.c 2000/01/07 15:51:45 1.33 +++ atapi-all.c 2000/01/08 23:50:08 @@ -558,23 +558,44 @@ *buffer = (int8_t *)&request->sense; if (request->bytecount < length) { - printf("%s: read data overrun %d/%d\n", - request->device->devname, length, request->bytecount); + printf("%s: read data overrun (%d buffer < %d bs), some data ignored\n", + request->device->devname, request->bytecount, length); #ifdef ATA_16BIT_ONLY insw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), request->bytecount/sizeof(int16_t)); + (void *)*buffer, request->bytecount / sizeof(int16_t)); #else insl(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), request->bytecount/sizeof(int32_t)); + (void *)*buffer, request->bytecount / sizeof(int32_t)); + if (request->bytecount & sizeof(int16_t)) + ((int16_t *)*buffer)[(request->bytecount % sizeof(int32_t)) / + sizeof(int16_t)] = + inw(request->device->controller->ioaddr + ATA_DATA); #endif + if (request->bytecount & sizeof(int8_t)) { + int16_t sixteen; + + sixteen = inw(request->device->controller->ioaddr + ATA_DATA); + (*buffer)[request->bytecount - sizeof(int8_t)] = + *(int8_t *)&sixteen; + length -= sizeof(int16_t); + } for (resid=request->bytecount; residdevice->controller->ioaddr + ATA_DATA); + (void)inw(request->device->controller->ioaddr + ATA_DATA); *buffer += request->bytecount; request->bytecount = 0; } else { +#ifdef ATA_16BIT_ONLY insw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); + (void *)*buffer, length / sizeof(int16_t)); +#else + insl(request->device->controller->ioaddr + ATA_DATA, + (void *)*buffer, length / sizeof(int32_t)); + if (length & sizeof(int16_t)) + ((int16_t *)*buffer)[(length - (length % sizeof(int32_t))) / + sizeof(int16_t)] = + inw(request->device->controller->ioaddr + ATA_DATA); +#endif *buffer += length; request->bytecount -= length; } @@ -590,24 +611,46 @@ *buffer = (int8_t *)&request->sense; if (request->bytecount < length) { - printf("%s: write data underrun %d/%d\n", - request->device->devname, length, request->bytecount); + printf("%s: write data underrun (%d buffer < %d bs), padding\n", + request->device->devname, request->bytecount, length); #ifdef ATA_16BIT_ONLY outsw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), request->bytecount/sizeof(int16_t)); + (void *)*buffer, request->bytecount / sizeof(int16_t)); #else outsl(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), request->bytecount/sizeof(int32_t)); + (void *)*buffer, request->bytecount / sizeof(int32_t)); + if (request->bytecount & sizeof(int16_t)) + outw(request->device->controller->ioaddr + ATA_DATA, + ((int16_t *)*buffer)[(request->bytecount % sizeof(int32_t)) / + sizeof(int16_t)]); #endif + if (request->bytecount & sizeof(int8_t)) { + int16_t sixteen; + + sixteen = 0; + *(int8_t *)&sixteen = + (*buffer)[request->bytecount - sizeof(int8_t)]; + outw(request->device->controller->ioaddr + ATA_DATA, sixteen); + length -= sizeof(int16_t); + } for (resid=request->bytecount; residdevice->controller->ioaddr + ATA_DATA, 0); *buffer += request->bytecount; request->bytecount = 0; } else { - outsw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); - *buffer += length; +#ifdef ATA_16BIT_ONLY + outsw(request->device->controller->ioaddr + ATA_DATA, + (void *)*buffer, length / sizeof(int16_t)); +#else + outsl(request->device->controller->ioaddr + ATA_DATA, + (void *)*buffer, length / sizeof(int32_t)); + if (length & sizeof(int16_t)) + outw(request->device->controller->ioaddr + ATA_DATA, + ((int16_t *)*buffer)[(length - (length % sizeof(int32_t))) / + sizeof(int16_t)]); +#endif + *buffer += length; request->bytecount -= length; } } Index: atapi-cd.c =================================================================== RCS file: /usr2/ncvs/src/sys/dev/ata/atapi-cd.c,v retrieving revision 1.33 diff -u -r1.33 atapi-cd.c --- atapi-cd.c 2000/01/07 12:01:00 1.33 +++ atapi-cd.c 2000/01/08 18:50:42 @@ -966,9 +966,12 @@ break; case CDRIOCCLOSEDISK: - if (!(cdp->flags & F_WRITTEN) || !(cdp->flags & F_DISK_OPEN)) { + if (!(cdp->flags & F_DISK_OPEN)) { error = EINVAL; printf("acd%d: sequence error (nothing to close)\n", cdp->lun); + } + else if (!(cdp->flags & F_WRITTEN)) { + cdp->flags &= ~(F_DISK_OPEN | F_TRACK_OPEN); } else { error = acd_close_disk(cdp); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 3: 4:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 4CE1F151D1 for ; Sun, 9 Jan 2000 03:04:39 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id DAA18695; Sun, 9 Jan 2000 03:04:19 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001091104.DAA18695@gndrsh.dnsmgr.net> Subject: Re: 4.0 slower than 3.4? In-Reply-To: <200001090359.TAA63459@vashon.polstra.com> from John Polstra at "Jan 8, 2000 07:59:32 pm" To: jdp@polstra.com (John Polstra) Date: Sun, 9 Jan 2000 03:04:18 -0800 (PST) Cc: death@southcom.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <4.2.2.20000109021927.00dba250@mail.southcom.com.au>, > james wrote: > > > It's interesting though how i had no ipf rules whatsoever, yet it > > introduced so much latency, as Alexander has pointed out in another email. > > Why is ipf so slow? I was planning on switching from ipfw/natd to > > ipf/ipnat, but i don't think i want to now - considering it's so darn slow. > > If you want to do NAT, I can tell you without even trying it that > ipfilter's NAT will be much faster than natd's. With natd, every > packet has to go out from the kernel to userland and back to have its > headers rewritten. That's a lot of overhead. Not so with ipfilter -- > it's all done inside the kernel. Think SMP, think lots of high speed NIC's, think about multiple divert rules to seperate natd's, think about the one big kernel lock and then think about your answer again :-) (Yes, I know latency will always be slightly longer, but overall through put can be signficantly higher when packets are passed over the kernel/user interface due to the big giant kernel lock.) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 3:18:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id DF56215137 for ; Sun, 9 Jan 2000 03:16:51 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 32678 invoked from network); 9 Jan 2000 11:16:50 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 9 Jan 2000 11:16:50 -0000 Message-ID: <38786E0E.D0216628@cvzoom.net> Date: Sun, 09 Jan 2000 06:16:30 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: ESS 1868 and DSP_BUFFSIZE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like the ESS 1868 is working OK now with the DSP_BUFFSIZE set to 8192. Before, it wouldn't work unless I set this value to (65536 - 256), which was the original value, I believe. So, why does the ESS work OK now with a buffer size of 8192? And how is this buffersize an advantage over (65536 - 256)? Everything seems to be working great for the ESS 1868 now, but I was just wondering... - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 4: 9:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 8935A150F8 for ; Sun, 9 Jan 2000 04:09:43 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id VAA21320; Sun, 9 Jan 2000 21:09:29 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id VAA15632; Sun, 9 Jan 2000 21:09:28 +0900 (JST) Received: from localhost ([192.168.245.210]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id VAA18553; Sun, 9 Jan 2000 21:09:27 +0900 (JST) To: leifn@neland.dk Cc: freebsd@cybcon.com, freebsd-current@FreeBSD.ORG Subject: Re: IPSEC broken, was Re: IPv6 testing...willing to help In-Reply-To: References: <20000108133114L.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000109211001N.shin@nd.net.fujitsu.co.jp> Date: Sun, 09 Jan 2000 21:10:01 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 27 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The 1st thing I want to be tested is that, a kernel with > > following additions to the config file > > > > options INET6 #IPv6 communications protocols > > options IPSEC #IP security > > options IPSEC_ESP #IP security (crypto; define w/ IPSEC) > > options IPSEC_IPV6FWD #IP security tunnel for IPv6 > > options IPSEC_DEBUG #debug for IP security > > > Kernel build stops with "Don't know how to make sha1.c". > sha was removed a few days ago, a "heads up" said. > > I've rebuilt world since, but I've had to remove the IPSEC options to make > a kernel. I think you don't have sys/crypto in your environment, is it? (Maybe due to restriction to get it from USA.) If so, please get it from internat.freebsd.org. It is necessary to use IPsec. The CVSROOT is internat.freebsd.org:/home/cvs.crypt Yoshinobu Inoue > Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 4:15:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id 2B7D214E9C for ; Sun, 9 Jan 2000 04:15:27 -0800 (PST) (envelope-from ian@niw.com.au) Received: by rose.niw.com.au (Postfix, from userid 1000) id B94DB62E4E; Sun, 9 Jan 2000 22:45:01 +1030 (CST) Date: Sun, 9 Jan 2000 22:45:01 +1030 From: Ian West To: current@freebsd.org Subject: Re: ESS 1868 and DSP_BUFFSIZE Message-ID: <20000109224500.B94641@rose.niw.com.au> References: <38786E0E.D0216628@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <38786E0E.D0216628@cvzoom.net>; from Donn Miller on Sun, Jan 09, 2000 at 06:16:30AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 09, 2000 at 06:16:30AM -0500, Donn Miller wrote: > It looks like the ESS 1868 is working OK now with the DSP_BUFFSIZE set > to 8192. Before, it wouldn't work unless I set this value to (65536 - > 256), which was the original value, I believe. So, why does the ESS > work OK now with a buffer size of 8192? And how is this buffersize an > advantage over (65536 - 256)? > > Everything seems to be working great for the ESS 1868 now, but I was > just wondering... > While it is much better than it was (sound happens, and the machine doesn't reboot :-), I am still seeing a repeat of the last few seconds of some audio with the ESS 1869 chipset. This seems to occur using waveplay (.wav files) and au files (cat *.au > /dev/dsp). I can't pick any pattern to it, although it is consistent on a per file basis. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 4:24:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id A1FD314D7F for ; Sun, 9 Jan 2000 04:24:45 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.19.152] (dialup1543.brussels.skynet.be [194.78.234.7]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id NAA22752; Sun, 9 Jan 2000 13:24:21 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Sun, 9 Jan 2000 13:01:30 +0100 To: "FreeBSD" , "Poul-Henning Kamp" From: Brad Knowles Subject: RE: load spike strangeness Cc: "freebsd-current@FreeBSD. ORG" Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:29 PM -0800 2000/1/8, FreeBSD wrote: > Again, I ask, if all you want to do is flame, take it to private e-mail and > let's leave the lists out of this. I don't think you get the point. If you continue to use an alias (as opposed to your real name), then it looks like everyone is just going to filter out your e-mail, and therefore it will do no good whatsoever to attempt to continue to post here. And if you go too far in this questionable behaviour, we may have to ask the FreeBSD Postmaster to remove you from the mailing lists and put you into the "spam" filters so that you are no longer capable of sending anything to the lists. Please cease and desist, before you do more damage to yourself and the lists. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 4:49:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 15CBF15137 for ; Sun, 9 Jan 2000 04:49:18 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 75F851DA7; Sun, 9 Jan 2000 13:49:16 +0100 (CET) Date: Sun, 9 Jan 2000 13:49:16 +0100 From: "Dave J. Boers" To: freebsd-current@freebsd.org Subject: Strange SCSI related system hang Message-ID: <20000109134916.A382@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, This morning I had a very strange (at least I've never seen it before) SCSI related system hang. The system simply stopped responding at 9:30:03 am this morning. I found it in this state at 13:20. It had been hanging _hard_. No response to console, serial terminal or network. After a hard reset the system came back online normally and is working normally again. Note that the machine had an uptime of 4 days, 14 hours before the problem occured and it never happened before. Could this be a hardware problem? ====> uname -a: FreeBSD relativity.student.utwente.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Dec 30 21:42:21 CET 1999 root@relativity.student.utwente.nl:/usr/src/sys/compile/RELATIVITY3 i386 ====> Here's the relevant system log messages: Note that all these messages occur at xx:30:00 or xx:30:01. That's probably related to a cron job which runs every half hour and copies some files (about 20 Mb) from my IDE disk to my SCSI disk. When the system is idle, there's usually no other SCSI activity. Jan 9 04:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 04:30:01 relativity /kernel: SEQADDR == 0x151 Jan 9 04:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 04:30:01 relativity /kernel: SEQADDR == 0x151 Jan 9 04:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 04:30:01 relativity /kernel: SEQADDR == 0x151 Jan 9 04:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 04:30:01 relativity /kernel: SEQADDR == 0x151 Jan 9 04:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 04:30:01 relativity /kernel: SEQADDR == 0x151 Jan 9 04:30:01 relativity /kernel: ahc0:A:0: no active SCB for reconnecting target - issuing BUS DEVICE RESET Jan 9 06:30:00 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 06:30:00 relativity /kernel: SEQADDR == 0x151 Jan 9 07:30:00 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 07:30:00 relativity /kernel: SEQADDR == 0x151 Jan 9 07:30:00 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 07:30:00 relativity /kernel: SEQADDR == 0x151 Jan 9 07:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 07:30:01 relativity /kernel: SEQADDR == 0x151 Jan 9 07:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 07:30:01 relativity /kernel: SEQADDR == 0x151 Jan 9 07:30:01 relativity /kernel: ahc0:A:0: no active SCB for reconnecting target - issuing BUS DEVICE RESET Jan 9 07:30:01 relativity /kernel: SAVED_TCL == 0x0, ARG_1 == 0x9, SEQ_FLAGS == 0x0 Jan 9 07:30:01 relativity /kernel: ahc0: Bus Device Reset on A:0. 1 SCBs aborted Jan 9 08:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 08:30:01 relativity /kernel: SEQADDR == 0x151 Jan 9 08:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jan 9 08:30:01 relativity /kernel: SEQADDR == 0x151 Jan 9 09:30:03 relativity /kernel: (da0:ahc0:0:0:0): Invalidating pack ====> Here's my complete dmesg output: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Dec 30 21:42:21 CET 1999 root@relativity.student.utwente.nl:/usr/src/sys/compile/RELATIVITY3 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (450.00-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 134217728 (131072K bytes) avail memory = 127238144 (124256K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02d2000. Preloaded elf module "vesa.ko" at 0xc02d209c. VESA: v3.0, 7936k memory, flags:0x1, mode table:0xc02cf102 (1000022) VESA: NVidia Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 intpm0: at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 ed0: irq 19 at device 9.0 on pci0 ed0: address 00:20:18:2d:d5:2b, type NE2000 (16 bit) ahc0: irq 18 at device 11.0 on pci0 ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs pci0: unknown card (vendor=0x10b7, dev=0x9055) at 13.0 irq 17 ata-pci1: irq 18 at device 19.0 on pci0 ata-pci1: Busmastering DMA supported ata2 at 0xb000 irq 11 on ata-pci1 ata-pci2: irq 18 at device 19.1 on pci0 ata-pci2: Busmastering DMA supported fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: HP ENHANCED PCL5,PJL plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 unknown0: at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown1: at port 0x100 on isa0 unknown2: at port 0x200-0x207 on isa0 unknown: can't assign resources unknown3: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 unknown4: at port 0x40-0x43 irq 0 on isa0 unknown5: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown: can't assign resources unknown6: at port 0xf0-0xff irq 13 on isa0 unknown7: at iomem 0-0x9ffff,0xfffe0000-0xffffffff,0xfec00000-0xfec0ffff,0xfee00000-0xfee0ffff,0x100000-0x7ffffff on isa0 unknown8: at iomem 0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfffff,0xce800-0xcffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown9: at port 0x208-0x20f on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging limited to 100 packets/entry by default SMP: AP CPU #1 Launched! ad0: ATA-4 disk at ata2 as master ad0: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA66 Waiting 5 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers Mounting root from ufs:/dev/ad0s1a cd1 at ahc0 bus 0 target 2 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 8) cd1: cd present [309750 x 2048 byte records] cd0 at ahc0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present WARNING: / was not properly dismounted da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15) da0: 4157MB (8515173 512 byte sectors: 255H 63S/T 530C) da1 at ahc0 bus 0 target 5 lun 0 da1: Removable Direct Access SCSI-2 device da1: 3.300MB/s transfers da1: 96MB (196608 512 byte sectors: 64H 32S/T 96C) pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 17 at device 13.0 on pci0 xl0: Ethernet address: 00:10:5a:65:33:80 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto If you need any more information, please let me know. I can also provide an account on the machine. Regards, Dave Boers. -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 4:53:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 1E468150F8; Sun, 9 Jan 2000 04:53:16 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id FAA09474; Sun, 9 Jan 2000 05:16:16 -0800 (PST) Date: Sun, 9 Jan 2000 05:16:16 -0800 From: Alfred Perlstein To: current@freebsd.org Cc: markm@freebsd.org Subject: make world broken? Message-ID: <20000109051616.C24472@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> libdes rm -f .depend mkdep -f .depend -a -I/vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes -I/usr/obj/vol/vinum0/src/i386/usr/include /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/cbc_cksm.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/pcbc_enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/qud_cksm.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/cbc3_enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/cfb64ede.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/cfb64enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/cfb_enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/ecb3_enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/enc_read.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/enc_writ.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/ofb64ede.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/ofb64enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/! libdes/ofb_enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/rand_key.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/rpc_enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/str2key.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/supp.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/xcbc_enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/cbc_enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/ncbc_enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/ecb_enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/set_key.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/des_enc.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/read_pwd.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/rnd_keys.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/rpw.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/read2pwd.c /vol/vinum0/src/secure/lib/libdes/../../../crypto/libdes/rpw.c:60: openssl/des.h: No such file or directory mkdep: compile failed *** Error code 1 1 error *** Error code 2 1 error -- -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 4:56:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 430F814D86 for ; Sun, 9 Jan 2000 04:56:11 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id EAA23038; Sun, 9 Jan 2000 04:48:22 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001091248.EAA23038@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brad Knowles Cc: "FreeBSD" , "freebsd-current@FreeBSD. ORG" Subject: Re: load spike strangeness In-reply-to: Your message of "Sun, 09 Jan 2000 13:01:30 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Jan 2000 04:48:22 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 8:29 PM -0800 2000/1/8, FreeBSD wrote: > > > Again, I ask, if all you want to do is flame, take it to private e-mail and > > let's leave the lists out of this. > > I don't think you get the point. If you continue to use an alias > (as opposed to your real name), then it looks like everyone is just > going to filter out your e-mail, and therefore it will do no good > whatsoever to attempt to continue to post here. > > And if you go too far in this questionable behaviour, we may have > to ask the FreeBSD Postmaster to remove you from the mailing lists > and put you into the "spam" filters so that you are no longer capable > of sending anything to the lists. > > > Please cease and desist, before you do more damage to yourself > and the lists. And whats the point of refusing him because he is using an obvious alias? For instance, just because someone has an email name which resembles a real name lets say "Brad Knowles" does not necessarily mean that the real "Brad Knowles is sending the mail assuming of course that there is a Brad Knowles. Let me put another way I sure hope we don't assume that any given email truly identifies the individual and that the person is legally responsible for his email handle . -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 5:16:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 9F76414D0C for ; Sun, 9 Jan 2000 05:16:05 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 9533 invoked from network); 9 Jan 2000 13:16:04 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 9 Jan 2000 13:16:04 -0000 Message-ID: <38788A00.123B7E80@cvzoom.net> Date: Sun, 09 Jan 2000 08:15:44 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Ian West Cc: current@freebsd.org Subject: Re: ESS 1868 and DSP_BUFFSIZE References: <38786E0E.D0216628@cvzoom.net> <20000109224500.B94641@rose.niw.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ian West wrote: > > On Sun, Jan 09, 2000 at 06:16:30AM -0500, Donn Miller wrote: > > Everything seems to be working great for the ESS 1868 now, but I was > > just wondering... > > > > While it is much better than it was (sound happens, and the machine > doesn't reboot :-), I am still seeing a repeat of the last few seconds > of some audio with the ESS 1869 chipset. This seems to occur using > waveplay (.wav files) and au files (cat *.au > /dev/dsp). I can't pick > any pattern to it, although it is consistent on a per file basis. Have you tried RealPlayer? Sometimes when RealPlayer does it's rebuffering (which is too much IMO, but that's RealPlayer), the sound repeats twice, and it occurs at the end of clips also. Also, RealPlayer has these useless options like Buffer xxx seconds before playing, and Buffer entire clip up to available memory. All give the same exact result, no matter which value of seconds I choose. Why did Real even put that option in there if it doesn't do anything? This is with RealPlayer 5.0. Actually, my ESS 1868 is working great... I can play a 3 minute clip with RealPlayer 5.0 and compile Wine in an xterm, and it plays smoothly until the end. (At which time it skips 2-3 times, but this is normal behavior.) Overall, the sound driver is working very superbly, at least for the 1868. I'm glad I kept that sound card. (Don't SoundBlaster cards have an ESS chip in them?) - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 5:55: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 07A9C15673; Sun, 9 Jan 2000 05:53:37 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id e09DrLw44383; Sun, 9 Jan 2000 15:53:21 +0200 (SAST) Message-Id: <200001091353.e09DrLw44383@gratis.grondar.za> To: Alfred Perlstein Cc: current@freebsd.org, markm@freebsd.org Subject: Re: make world broken? References: <20000109051616.C24472@fw.wintelcom.net> In-Reply-To: <20000109051616.C24472@fw.wintelcom.net> ; from Alfred Perlstein "Sun, 09 Jan 2000 05:16:16 PST." Date: Sun, 09 Jan 2000 15:53:20 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ===> libdes Fixed - thanks! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 8: 0:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 2D990152BB for ; Sun, 9 Jan 2000 08:00:52 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.19.152] (dialup1489.brussels.skynet.be [194.78.233.209]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id RAA04256; Sun, 9 Jan 2000 17:00:38 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001091248.EAA23038@rah.star-gate.com> References: <200001091248.EAA23038@rah.star-gate.com> Date: Sun, 9 Jan 2000 16:59:03 +0100 To: Amancio Hasty From: Brad Knowles Subject: Re: load spike strangeness Cc: "FreeBSD" , "freebsd-current@FreeBSD. ORG" Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:48 AM -0800 2000/1/9, Amancio Hasty wrote: > For instance, just because someone has an email name which resembles > a real name lets say "Brad Knowles" does not necessarily mean that the > real "Brad Knowles is sending the mail assuming of course that there > is a Brad Knowles. I've built up enough history over the years (all the while using my real name and a real e-mail address, although the address has changed over the years as I've changed employers, etc...) that you can go do some AltaVista or Hotbot searches and find enough stuff that I've written that we can be reasonably sure that this really is me. I may not be proud of some of the stupid things I've done or said over the years, but I'll own up to them regardless. I'd say that the same is probably true of most of the people posting to the various lists. > Let me put another way I sure hope we don't assume that any given email > truly identifies the individual and that the person is legally responsible > for his email handle. No more than you can be sure that a particular PGP key belongs to the person it claims to belong to, or that a person who presents you with a drivers license that claims to tell you their name or address. However, in the case of electronic discussions, there is likely to be enough history available that you can be reasonably sure you're dealing with the same person who claims to go by the same name, even if that isn't their real name. It's hard to make the same kinds of connections with an alias. Yes, Thomas Jefferson and Alexander Hamilton published the Federalist Papers under assumed names, because that was necessary at the time in order to avoid the potential legal consequences of the British finding out who the real authors were. However, I sincerely doubt that any such claim can be made today for posting to one of the FreeBSD mailing lists. Claims of "needing" anonymity in cases like this just aren't likely to be very well received, and the more strident the claimer becomes in their "need" to remain hidden, the more likely people are to either try to unmask the jerk or to decide to simply start ignoring them. If you want to post in a public place like this, and you want other people to be able to help you or carry on an intelligent conversation with you, I would suggest that taking the extremely anti-social approach of using an alias is one of the worst possible things you could as a first step. It won't help stop the spam, and it will just annoy the people you'd want to be talking to. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 8:54: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id 91A5614E6E for ; Sun, 9 Jan 2000 08:54:02 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id IAA73411; Sun, 9 Jan 2000 08:53:59 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: "Brad Knowles" Cc: "freebsd-current@FreeBSD. ORG" Subject: RE: load spike strangeness Date: Sun, 9 Jan 2000 08:54:05 -0800 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) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 8:29 PM -0800 2000/1/8, FreeBSD wrote: > > > Again, I ask, if all you want to do is flame, take it to > private e-mail and > > let's leave the lists out of this. > > I don't think you get the point. If you continue to use an alias > (as opposed to your real name), then it looks like everyone is just > going to filter out your e-mail, and therefore it will do no good > whatsoever to attempt to continue to post here. I don't think YOU get it. I don't care if I'm filtered, that's your right. I'm not about to post my personal info to a public list. If I'm not taken seriously, fine. If I'm filtered, fine. If people don't like it, fine. It's not going to change. > > And if you go too far in this questionable behaviour, we may have > to ask the FreeBSD Postmaster to remove you from the mailing lists > and put you into the "spam" filters so that you are no longer capable > of sending anything to the lists. What's so questionable about protecting personal info in a public list? Why don't you include your SSN, mother maiden name, home phone and home address while you're at it? I'd suggest reading some web pages about internet security (I don't mean the hacking exploit kind) they all say to keep as much personal info off the net as possible. As I've stated before if the charters are changed to demand personal info to be subscribed I'll unsubscribe because my personal info is not, and should not be, public information. > > > Please cease and desist, before you do more damage to yourself > and the lists. I will NOT. > > -- > These are my opinions -- not to be taken as official Skynet policy > ____________________________________________________________________ > |o| Brad Knowles, Belgacom Skynet NV/SA |o| > |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| > |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| > |o| http://www.skynet.be Belgium |o| > \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ > Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. > Unix is very user-friendly. It's just picky who its friends are. > FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 9: 0:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id F1BCE151D1 for ; Sun, 9 Jan 2000 09:00:28 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id JAA73441; Sun, 9 Jan 2000 09:00:27 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: "Amancio Hasty" Cc: "freebsd-current@FreeBSD. ORG" Subject: RE: load spike strangeness Date: Sun, 9 Jan 2000 09:00:33 -0800 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) In-Reply-To: <200001091248.EAA23038@rah.star-gate.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > At 8:29 PM -0800 2000/1/8, FreeBSD wrote: > > > > > Again, I ask, if all you want to do is flame, take it to > private e-mail and > > > let's leave the lists out of this. > > > > I don't think you get the point. If you continue to use an alias > > (as opposed to your real name), then it looks like everyone is just > > going to filter out your e-mail, and therefore it will do no good > > whatsoever to attempt to continue to post here. > > > > And if you go too far in this questionable behaviour, we may have > > to ask the FreeBSD Postmaster to remove you from the mailing lists > > and put you into the "spam" filters so that you are no longer capable > > of sending anything to the lists. > > > > > > Please cease and desist, before you do more damage to yourself > > and the lists. > > And what's the point of refusing him because he is using an obvious alias? > > For instance, just because someone has an email name which resembles > a real name lets say "Brad Knowles" does not necessarily mean that the > real "Brad Knowles is sending the mail assuming of course that there > is a Brad Knowles. > > Let me put another way I sure hope we don't assume that any given email > truly identifies the individual and that the person is legally > responsible > for his email handle . > Indeed, I could adduser bknowels and use/be Brad Knowels (for all you know my name could also be Brad Knowels) if he prefers. I'm not like that though. Some people just aren't happy if they aren't complaining about something. > > Amancio Hasty > hasty@rah.star-gate.com > FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 9:19: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id E98CC1530B for ; Sun, 9 Jan 2000 09:19:06 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id JAA10015; Sun, 9 Jan 2000 09:28:38 -0800 (PST) Received: from wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id JAA19698; Sun, 9 Jan 2000 09:12:35 -0800 (PST) (envelope-from dbutter@wireless.net) Message-ID: <3878C34C.9B453321@wireless.net> Date: Sun, 09 Jan 2000 09:20:12 -0800 From: Devin Butterfield X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Cc: current@freebsd.org Subject: Re: load spike strangeness References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Indeed, I could adduser bknowels and use/be Brad Knowels (for all you know > my name could also be Brad Knowels) if he prefers. I'm not like that though. > Some people just aren't happy if they aren't complaining about something. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I agree. It would be nice if this thread would die. I have seen "FreeBSD" posting to lists for a while now and never saw anyone else complain. If you don't like it, just filter him out of your inbox, but please...there's been too much cat fighting on this list lately. > > > > Amancio Hasty > > hasty@rah.star-gate.com > > > > FreeBSD > freebsd@gtonet.net > > "LinSUX is only free if your time is worthless" > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 9:24: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id 98F14152FD for ; Sun, 9 Jan 2000 09:23:59 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id JAA73509; Sun, 9 Jan 2000 09:23:52 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: "Brad Knowles" Cc: "freebsd-current@FreeBSD. ORG" Subject: RE: load spike strangeness Date: Sun, 9 Jan 2000 09:23:58 -0800 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) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 4:48 AM -0800 2000/1/9, Amancio Hasty wrote: > > > For instance, just because someone has an email name which resembles > > a real name lets say "Brad Knowles" does not necessarily mean that the > > real "Brad Knowles is sending the mail assuming of course that there > > is a Brad Knowles. > > I've built up enough history over the years (all the while using > my real name and a real e-mail address, although the address has > changed over the years as I've changed employers, etc...) that you > can go do some AltaVista or Hotbot searches and find enough stuff > that I've written that we can be reasonably sure that this really is > me. I may not be proud of some of the stupid things I've done or > said over the years, but I'll own up to them regardless. > > I'd say that the same is probably true of most of the people > posting to the various lists. > > > Let me put another way I sure hope we don't assume that any given email > > truly identifies the individual and that the person is legally > responsible > > for his email handle. > > No more than you can be sure that a particular PGP key belongs to > the person it claims to belong to, or that a person who presents you > with a drivers license that claims to tell you their name or address. > > However, in the case of electronic discussions, there is likely > to be enough history available that you can be reasonably sure you're > dealing with the same person who claims to go by the same name, even > if that isn't their real name. > > > It's hard to make the same kinds of connections with an alias. > Yes, Thomas Jefferson and Alexander Hamilton published the Federalist > Papers under assumed names, because that was necessary at the time in > order to avoid the potential legal consequences of the British > finding out who the real authors were. However, I sincerely doubt > that any such claim can be made today for posting to one of the > FreeBSD mailing lists. Look, show me in the mailing list charters where it says I must use my realname or shut-the--up. If you don't like it filter me, I've already said I don't care. The Patriots you use as examples risked death by hanging. We merely risk identity theft and financial ruin. Unfortunately for you, I'm not willing to take that risk. > > Claims of "needing" anonymity in cases like this just aren't > likely to be very well received, and the more strident the claimer > becomes in their "need" to remain hidden, the more likely people are > to either try to unmask the jerk or to decide to simply start > ignoring them. Again, I don't care if it's well received, I'm not here for a popularity contest. Mr. Bushong had a problem and I replied with a tidbit of possible info. If you disagree, fine. If you don't like it, too bad. Other than that, get a life. > > > If you want to post in a public place like this, and you want > other people to be able to help you or carry on an intelligent > conversation with you, I would suggest that taking the extremely > anti-social approach of using an alias is one of the worst possible > things you could as a first step. Anti-social? Are you for real? Please post your Social Security Number, home address, home phone, drivers license #, mothers maiden name and date of birth, Mr. nothing-to-hide-in-a-public-list. Since when does personal info preclude an exchange of information? I might, now, suggest therapy for you Mr. Knowles. > > It won't help stop the spam, and it will just annoy the people > you'd want to be talking to. What makes you think I want to be talking to a self-righteous bore, with no respect for peoples privacy in a day and age of identity theft? You, Brad, have just made my filter list as I hope I've made yours. > > -- > These are my opinions -- not to be taken as official Skynet policy > ____________________________________________________________________ > |o| Brad Knowles, Belgacom Skynet NV/SA |o| > |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| > |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| > |o| http://www.skynet.be Belgium |o| > \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ > Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. > Unix is very user-friendly. It's just picky who its friends are. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 9:26:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id AC444152F6 for ; Sun, 9 Jan 2000 09:26:25 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id JAA73521; Sun, 9 Jan 2000 09:26:19 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: "Devin Butterfield" Cc: Subject: RE: load spike strangeness Date: Sun, 9 Jan 2000 09:26:25 -0800 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) In-Reply-To: <3878C34C.9B453321@wireless.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Indeed, I could adduser bknowels and use/be Brad Knowels (for > all you know > > my name could also be Brad Knowels) if he prefers. I'm not like > that though. > > Some people just aren't happy if they aren't complaining about > something. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > I agree. It would be nice if this thread would die. I have seen > "FreeBSD" posting to lists for a while now and never saw anyone else > complain. If you don't like it, just filter him out of your inbox, but > please...there's been too much cat fighting on this list lately. > > Amen! I thought this was finished last night, but NOOOooOOOOooo. FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 10:11: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 065541521B for ; Sun, 9 Jan 2000 10:10:46 -0800 (PST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id TAA18073; Sun, 9 Jan 2000 19:10:33 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <009b01bf5acc$d943f140$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "FreeBSD" Cc: "freebsd-current@FreeBSD. ORG" References: Subject: Anonymity, was: load spike strangeness Date: Sun, 9 Jan 2000 19:10:27 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While I do not agree with your idea of need of anonymity, I respect your = need for it. Could you not, instead of using the handle "FreeBSD", which sortof = already is taken :-), just assume a human name? The use of an obviously = not human name makes it uncomfortable to communicate with you. If you would call you John Smith, or Thomas Jefferson if you want, you = could much more easily hide your (hideous?) precence in the lists. = Please?=20 Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 10:16:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id CF3AB14D55 for ; Sun, 9 Jan 2000 10:16:37 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA51498; Sun, 9 Jan 2000 10:16:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Brad Knowles Cc: "FreeBSD" , "Poul-Henning Kamp" , "freebsd-current@FreeBSD. ORG" Subject: Re: load spike strangeness In-reply-to: Your message of "Sun, 09 Jan 2000 13:01:30 +0100." Date: Sun, 09 Jan 2000 10:16:11 -0800 Message-ID: <51496.947441771@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can we please end this discussion? End it now. It's of no importance to me or, I venture to say, the postmaster whether or not someone wishes to use an alias in these mailing lists and it's certainly not a topic which follows the charter for the FreeBSD-current mailing list. In fact, the only clear violation of the mailing list charters I've seen here so far is rampant cross-posting (which has resulted in more than a few nasty-grams going out) and the discussion of this topic in all the wrong forums. This should have gone to -chat on the first day since it had ABSOLUTELY NO PLACE in -stable, -current or -security and whomever first cross-posted it to all three lists needs to seriously have their head checked. If I had enough energy to look through the logs and find the first perpetrator, I'd add them to the filter right now just for having a room temperature IQ. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 10:24:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id E66E214E1D for ; Sun, 9 Jan 2000 10:24:53 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id KAA73723; Sun, 9 Jan 2000 10:24:51 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: "Leif Neland" Cc: "freebsd-current@FreeBSD. ORG" Subject: RE: Anonymity, was: load spike strangeness Date: Sun, 9 Jan 2000 10:24:57 -0800 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) In-Reply-To: <009b01bf5acc$d943f140$0e00a8c0@neland.dk> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > While I do not agree with your idea of need of anonymity, I > respect your need for it. You don't have to agree and I appreciate your respect. > > Could you not, instead of using the handle "FreeBSD", which > sortof already is taken :-), just assume a human name? The use of > an obviously not human name makes it uncomfortable to communicate > with you. Certainly, I could, but I wont. I chose this username specifically for FreeBSD mailing lists and it's all I use it for. I have other usernames for other things including one with my real name, on another system, that I use for "personal" communications with friends and family. If people don't like it they can just filter me out. I'm not here to make anyone comfortable, I'm here to get the latest information about FreeBSD, my OS of choice and *IF* I can help someone else with information I may have, I might choose to share it. > > If you would call you John Smith, or Thomas Jefferson if you > want, you could much more easily hide your (hideous?) precence in > the lists. Please? Again, no. > > Leif > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 10:25: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id C133E14C43 for ; Sun, 9 Jan 2000 10:25:03 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id LAA14979; Sun, 9 Jan 2000 11:24:47 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA16478; Sun, 9 Jan 2000 11:24:42 -0700 Date: Sun, 9 Jan 2000 11:24:42 -0700 Message-Id: <200001091824.LAA16478@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Garrett Wollman Cc: "FreeBSD" , Subject: RE: load spike strangeness In-Reply-To: <200001090258.VAA53335@khavrinen.lcs.mit.edu> References: <200001090206.DAA75669@dorifer.heim3.tu-clausthal.de> <200001090258.VAA53335@khavrinen.lcs.mit.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Moved to chat ] > [Multiple irrelevant mailing-lists snipped.] > > < said: > > > Since when does an E-mail address require a "realname"? > > As Sherlock Holmes once said: ``It is always unpleasant dealing with > an alias.'' > > >plonk< Boo... Hisss.... Nate ;) ;) ;) ;) ;) ;) ;) ;) ;) ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 10:29:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7CFFF14D73 for ; Sun, 9 Jan 2000 10:29:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA19954; Sun, 9 Jan 2000 10:29:32 -0800 (PST) (envelope-from dillon) Date: Sun, 9 Jan 2000 10:29:32 -0800 (PST) From: Matthew Dillon Message-Id: <200001091829.KAA19954@apollo.backplane.com> To: "Dave J. Boers" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Strange SCSI related system hang References: <20000109134916.A382@relativity.student.utwente.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi all, : :This morning I had a very strange (at least I've never seen it before) SCSI :related system hang. The system simply stopped responding at 9:30:03 am :this morning. I found it in this state at 13:20. It had been hanging :_hard_. No response to console, serial terminal or network. After a hard :reset the system came back online normally and is working normally again. : :Note that the machine had an uptime of 4 days, 14 hours before the problem :occured and it never happened before. : :Could this be a hardware problem? Yes. The problem is probably termination. You have three devices on your SCSI bus -- your hard drive should be the terminating device and should have termination enabled. Neither of the other two devices should have termination enabled. Alternatively, none of the devices should have termination enabled and you should have an external active terminator (active terminators have LEDs). Never use a CDRom or ZIP drive to terminate a SCSI bus, they're generally too cheap to do it right. I am presuming that these are all internally mounted. If you have any externally mounted SCSI devices or a combination of the two then both ends must be terminated. -Matt :... :Jan 9 04:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 :Jan 9 04:30:01 relativity /kernel: SEQADDR == 0x151 :Jan 9 04:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 :Jan 9 04:30:01 relativity /kernel: SEQADDR == 0x151 :Jan 9 04:30:01 relativity /kernel: Unexpected busfree. LASTPHASE == 0xa0 :... :Jan 9 04:30:01 relativity /kernel: SEQADDR == 0x151 :Jan 9 04:30:01 relativity /kernel: ahc0:A:0: no active SCB for reconnecting target - issuing BUS DEVICE RESET : :... :cd0 at ahc0 bus 0 target 1 lun 0 :cd0: Removable CD-ROM SCSI-2 device :cd0: 10.000MB/s transfers (10.000MHz, offset 8) :cd0: Attempt to query device size failed: NOT READY, Medium not present :WARNING: / was not properly dismounted :da0 at ahc0 bus 0 target 0 lun 0 :da0: Fixed Direct Access SCSI-2 device :da0: 20.000MB/s transfers (20.000MHz, offset 15) :da0: 4157MB (8515173 512 byte sectors: 255H 63S/T 530C) :da1 at ahc0 bus 0 target 5 lun 0 :da1: Removable Direct Access SCSI-2 device :da1: 3.300MB/s transfers :da1: 96MB (196608 512 byte sectors: 64H 32S/T 96C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 11:21:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 7F797152B7 for ; Sun, 9 Jan 2000 11:21:52 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id EAA16151 for ; Mon, 10 Jan 2000 04:21:50 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id EAA15688; Mon, 10 Jan 2000 04:21:49 +0900 (JST) Received: from localhost ([192.168.245.55]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id EAA27611; Mon, 10 Jan 2000 04:21:48 +0900 (JST) To: freebsd-current@FreeBSD.ORG Subject: Re: [solicite review and confirmation of tcp for IPv6 patches] In-Reply-To: <20000107123727P.shin@nd.net.fujitsu.co.jp> References: <20000103012633S.shin@nd.net.fujitsu.co.jp> <20000107123727P.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000110042221K.shin@nd.net.fujitsu.co.jp> Date: Mon, 10 Jan 2000 04:22:21 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 21 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I fixed the bug and using the patched machine from remote. Now > it seems to be working well. > I also simplified the patch to nfs_socket.c. > Updated patches are below. (patches to trpt is same as last version.) > > http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/kernel-tcp.20000107 > http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/trpt.19991228 > > Please try these patches anyone interested. If it seems to be > working well also in other environment, I'll commit them into > the repository. As far as my local check and reports from people who tried it, the patch seems to be safely working. So I just committed it. But if problems will happen, I'll backout the changes, so if you have troubles, please let me know. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 11:22:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from iaehv.iae.nl (iaehv.IAE.nl [194.151.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 3494614C3E for ; Sun, 9 Jan 2000 11:22:42 -0800 (PST) (envelope-from hansot@iae.nl) Received: from iae.nl (pm12d05.iae.nl [212.61.1.198]) by iaehv.iae.nl (Postfix) with ESMTP id CC6827C19; Sun, 9 Jan 2000 20:22:39 +0100 (CET) Message-ID: <3878DFFF.28349A4F@iae.nl> Date: Sun, 09 Jan 2000 20:22:39 +0100 From: Hans Ottevangerne_anchors X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: New kernel no longer boots on one of my machines... ata, other problems References: <200001070405.UAA75303@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > Well guys, I tried upgrading one of my older machines today to the > latest 4.0. It was running an older 4.0 kernel (Nov 29 1999). > [ Detailed description deleted ] > HEEEEELP! Whats happening!!! :-( :-( :-( > > At the moment I am stymied. I switched to a GENERIC kernel and got the > same results, so it isn't anything weird that I have done in my own > kernel config. > > I was hoping that someone would have an idea. > > -Matt Hi folks, As already reported yesterday, I have similar problems, and I have been doing some experiments today with my ancient Pentium 66. With 4.0 CURRENT as of yesterday, it seem to hang while booting, when configured to use the new ATA driver. When using the old WD driver, there is no such problem. The system has 64 MB RAM, two Western Digital harddisks of 1.6 GB and 3.1 GB respectively, 8x Toshiba CDROM, Matrox Millenium II graphics card, and a 3Com 905B NIC. As Matt did, I switched to a GENERIC kernel, and I booted with the options -s and -v. The system seems to hang after the message: Mounting root from ufs:wd0s1a However, if I hit RETURN, followed by CTL-ALT-ESC, I actually end up in the single user mode shell. I even can run commands, I only must type CTL-ALT-ESC to see the output. And indeed, the clock is not running. By mounting /var, I captured the output of dmesg in a file. And it shows at least one strange thing: ata-pci0: at device 1.0 on pci0 ata-pci0: Busmastering DMA not supported ata0: iobase=0x01f0 altiobase=0x03f4 bmaddr=0x0000 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=50 ata0: devices = 0x3 ata0 at 0x01f0 irq 0 on ata-pci0 ^^^^^^^ I.e. ata0 takes the irq that is normally reserved for the timer. And somewhat later in the boot process we see: Device configuration finished. device combination doesn't support shared irq0 intr_connect(irq0) failed, result=-1 So indeed the timer is not able to interrupt, which explains the strange phenomena. The secondary EIDE interface, which is on the ISA bus in this system, is recognized correctly: ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x0000 ata1: mask=01 status0=00 status1=ff ata1: mask=01 status0=00 status1=ffffffff ata1: devices = 0x4 ata1 at port 0x170 irq 15 on isa0 As a quick fix, to get rid of the problem for now, I forced the irq of ata0 to 14 in the source. I added the line irq1 = 14; after line 293 in /sys/dev/ata/ata-all.c (1.39) After compiling the kernel, the system reboots and runs without any problems, using the ATA drivers. Apparently, something is going wrong when reading the PCI configuration on these old systems. It certainly justifies some investigation. Kind regards, Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 11:45:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from iaehv.iae.nl (iaehv.IAE.nl [194.151.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 92A9014E5F for ; Sun, 9 Jan 2000 11:45:33 -0800 (PST) (envelope-from hansot@iae.nl) Received: from iae.nl (pm12d05.iae.nl [212.61.1.198]) by iaehv.iae.nl (Postfix) with ESMTP id 0451C7CBA for ; Sun, 9 Jan 2000 20:45:32 +0100 (CET) Message-ID: <3878E55B.4CAC3A4C@iae.nl> Date: Sun, 09 Jan 2000 20:45:31 +0100 From: Hans Ottevangerne_anchors X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: New kernel no longer boots on one of my machines... ata, other problems References: <200001070405.UAA75303@apollo.backplane.com> <3878DFFF.28349A4F@iae.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Before people start wondering about my name being mangled in the From: field of my previous message: Sorry, it happens regularly when cutting and pasting into the mailer of the Netscape Communicator 4.7. Maybe I have to switch to another mailtool... Cheers, Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 12:17:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.qx.net (darkstar.qx.net [208.235.88.101]) by hub.freebsd.org (Postfix) with ESMTP id EF746152DA for ; Sun, 9 Jan 2000 12:17:34 -0800 (PST) (envelope-from gchil0@pop.uky.edu) Received: from mail.qx.net (mail.qx.net [208.235.88.10]) by darkstar.qx.net (8.8.7/8.8.7) with ESMTP id PAA27292 for ; Sun, 9 Jan 2000 15:17:28 -0500 Received: from k7 ([208.200.111.56]) by mail.qx.net (Netscape Messaging Server 3.6) with ESMTP id AAA4421; Sun, 9 Jan 2000 15:20:18 -0500 Message-Id: <4.2.0.58.20000109151045.00959bf0@pop.uky.edu> X-Sender: gchil0@pop.uky.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sun, 09 Jan 2000 15:18:21 -0500 To: Hans Ottevangerne_anchors , Matthew Dillon From: Greg Childers Subject: Re: New kernel no longer boots on one of my machines... ata, other problems Cc: current@FreeBSD.ORG In-Reply-To: <3878DFFF.28349A4F@iae.nl> References: <200001070405.UAA75303@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes! That is exactly the problem I have been having since the 1999/10/09 12:57:15 PDT ATA commit. Here is the link to the email I sent earlier: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=1326170+1331912+/usr/local/www/db/text/1999/freebsd-current/19991212.freebsd-current Basically, on my Pentium 66 system, I'm seeing the same problems followed by the message microuptime() went backwards (1.4342530 -> 1,047990) Thanks for investigating this! Greg At 08:22 PM 1/9/00 +0100, Hans Ottevangerne_anchors wrote: >As already reported yesterday, I have similar problems, and I have been >doing some experiments today with my ancient Pentium 66. With 4.0 >CURRENT as of yesterday, it seem to hang while booting, when configured >to use the new ATA driver. When using the old WD driver, there is no >such problem. > >The system has 64 MB RAM, two Western Digital harddisks of 1.6 GB and >3.1 GB respectively, 8x Toshiba CDROM, Matrox Millenium II graphics >card, and a 3Com 905B NIC. > >As Matt did, I switched to a GENERIC kernel, and I booted with the >options -s and -v. The system seems to hang after the message: > > Mounting root from ufs:wd0s1a > >However, if I hit RETURN, followed by CTL-ALT-ESC, I actually end up in >the single user mode shell. I even can run commands, I only must type >CTL-ALT-ESC to see the output. And indeed, the clock is not running. By >mounting /var, I captured the output of dmesg in a file. And it shows at >least one strange thing: > > ata-pci0: at device 1.0 on >pci0 > ata-pci0: Busmastering DMA not supported > ata0: iobase=0x01f0 altiobase=0x03f4 bmaddr=0x0000 > ata0: mask=03 status0=50 status1=50 > ata0: mask=03 status0=50 status1=50 > ata0: devices = 0x3 > ata0 at 0x01f0 irq 0 on ata-pci0 > ^^^^^^^ > >I.e. ata0 takes the irq that is normally reserved for the timer. And >somewhat later in the boot process we see: > > Device configuration finished. > device combination doesn't support shared irq0 > intr_connect(irq0) failed, result=-1 > >So indeed the timer is not able to interrupt, which explains the strange >phenomena. >The secondary EIDE interface, which is on the ISA bus in this system, is >recognized correctly: > > ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x0000 > ata1: mask=01 status0=00 status1=ff > ata1: mask=01 status0=00 status1=ffffffff > ata1: devices = 0x4 > ata1 at port 0x170 irq 15 on isa0 > > >As a quick fix, to get rid of the problem for now, I forced the irq of >ata0 to 14 in the source. I added the line > > irq1 = 14; > >after line 293 in /sys/dev/ata/ata-all.c (1.39) > >After compiling the kernel, the system reboots and runs without any >problems, using the ATA drivers. > >Apparently, something is going wrong when reading the PCI configuration >on these old systems. It certainly justifies some investigation. > >Kind regards, > >Hans > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 12:25:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 1D8051528E for ; Sun, 9 Jan 2000 12:25:34 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 9 Jan 2000 20:25:30 +0000 (GMT) Date: Sun, 9 Jan 2000 20:25:29 +0000 From: David Malone To: "Kurt D. Zeilenga" Cc: Garrett Wollman , freebsd-current@freebsd.org Subject: Re: PAM'ized su(1) Message-ID: <20000109202529.A717@walton.maths.tcd.ie> References: <3.0.5.32.20000108141410.00933c40@localhost> <3.0.5.32.20000108124258.0093bb90@localhost> <3.0.5.32.20000108112936.0095f440@localhost> <200001081932.OAA52181@khavrinen.lcs.mit.edu> <3.0.5.32.20000108124258.0093bb90@localhost> <200001082143.QAA52528@khavrinen.lcs.mit.edu> <3.0.5.32.20000108141410.00933c40@localhost> <20000108230835.A88514@walton.maths.tcd.ie> <3.0.5.32.20000108154833.00932930@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3.0.5.32.20000108154833.00932930@localhost>; from Kurt@OpenLDAP.org on Sat, Jan 08, 2000 at 03:48:33PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 08, 2000 at 03:48:33PM -0800, Kurt D. Zeilenga wrote: > Did you try the "use_uid" option? Looks like you're dead right! I can't test it 'till tomorrow, but I'm sure it works. Oh, if only everything came with man pages, then I could RTFM. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 13:24:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D3DF6153D7 for ; Sun, 9 Jan 2000 13:24:19 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA15242; Sun, 9 Jan 2000 13:24:18 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA65356; Sun, 9 Jan 2000 13:24:17 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 9 Jan 2000 13:24:17 -0800 (PST) Message-Id: <200001092124.NAA65356@vashon.polstra.com> To: bde@zeta.org.au Subject: Re: __sigisempty() undefined if "cc -g" used. In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Bruce Evans wrote: > > You apparently > clobbered -O in CFLAGS by setting CFLAGS=-g. -g normally needs to be > added to CC to avoid breaking CFLAGS (CC='cc -g'). Better yet: DEBUG_FLAGS=-g John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 14:19:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 666EE14CC5; Sun, 9 Jan 2000 14:19:42 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@pm3b-13.cybcon.com [205.147.75.78]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id OAA25475; Sun, 9 Jan 2000 14:19:34 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 09 Jan 2000 14:20:51 -0800 (PST) From: William Woods To: freebsd-current@freebsd.org, freebsd-alpha@freebsd.org Subject: PPP connections die in current.... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Running 4.0 -current as of today.....on a DEC Alphaststion 233 when I dial out I connect for about 30 seconds then it dies...here is a copy of the ppp.log Jan 9 22:00:27 alpha ppp[388]: Phase: Using interface: tun0 Jan 9 22:00:27 alpha ppp[388]: Phase: deflink: Created in closed state Jan 9 22:00:27 alpha ppp[388]: tun0: Command: default: set device /dev/cuaa1 Jan 9 22:00:27 alpha ppp[388]: tun0: Command: default: set speed 57600 Jan 9 22:00:27 alpha ppp[388]: tun0: Command: default: set dial ABORT BUSY ABORT NO\sCARRIER TIMEOUT 5 "" AT OK-AT-OK ATE1Q0 OK \dATDT\T TIMEOUT 40 CONNECT Jan 9 22:00:27 alpha ppp[388]: tun0: Phase: PPP Started (interactive mode). Jan 9 22:00:33 alpha ppp[388]: tun0: Command: /dev/tty: dial cybcon Jan 9 22:00:33 alpha ppp[388]: tun0: Command: cybcon: set phone 5039721667:5039721668 Jan 9 22:00:33 alpha ppp[388]: tun0: Command: cybcon: set login ABORT NO\sCARRIER TIMEOUT 5 ogin:--ogin: Pxxxxx word: xxxxxxxxxx Jan 9 22:00:33 alpha ppp[388]: tun0: Command: cybcon: set timeout 300 Jan 9 22:00:33 alpha ppp[388]: tun0: Command: cybcon: set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 Jan 9 22:00:33 alpha ppp[388]: tun0: Command: cybcon: add default HISADDR Jan 9 22:00:33 alpha ppp[388]: tun0: Warning: Add route failed: default already exists Jan 9 22:00:33 alpha ppp[388]: tun0: Command: cybcon: enable dns Jan 9 22:00:33 alpha ppp[388]: tun0: Phase: bundle: Establish Jan 9 22:00:33 alpha ppp[388]: tun0: Phase: deflink: closed -> opening Jan 9 22:00:33 alpha ppp[388]: tun0: Phase: deflink: Connected! Jan 9 22:00:33 alpha ppp[388]: tun0: Phase: deflink: opening -> dial Jan 9 22:00:33 alpha ppp[388]: tun0: Phase: Phone: 5039721667 Jan 9 22:00:33 alpha ppp[388]: tun0: Chat: deflink: Dial attempt 1 of 1 Jan 9 22:00:33 alpha ppp[388]: tun0: Chat: Send: AT^M Jan 9 22:00:33 alpha ppp[388]: tun0: Chat: Expect(5): OK Jan 9 22:00:33 alpha ppp[388]: tun0: Chat: Received: AT^M^M Jan 9 22:00:33 alpha ppp[388]: tun0: Chat: Received: OK^M Jan 9 22:00:33 alpha ppp[388]: tun0: Chat: Send: ATE1Q0^M Jan 9 22:00:33 alpha ppp[388]: tun0: Chat: Expect(5): OK Jan 9 22:00:33 alpha ppp[388]: tun0: Chat: Received: ATE1Q0^M^M Jan 9 22:00:33 alpha ppp[388]: tun0: Chat: Received: OK^M Jan 9 22:00:33 alpha ppp[388]: tun0: Chat: Send: ATDT5039721667^M Jan 9 22:00:35 alpha ppp[388]: tun0: Chat: Expect(40): CONNECT Jan 9 22:01:00 alpha ppp[388]: tun0: Chat: Received: ATDT5039721667^M^M Jan 9 22:01:00 alpha ppp[388]: tun0: Chat: Received: CONNECT Jan 9 22:01:00 alpha ppp[388]: tun0: Phase: deflink: dial -> carrier Jan 9 22:01:01 alpha ppp[388]: tun0: Phase: deflink: /dev/cuaa1: CD detected Jan 9 22:01:01 alpha ppp[388]: tun0: Phase: deflink: carrier -> login Jan 9 22:01:01 alpha ppp[388]: tun0: Chat: Expect(5): ogin: Jan 9 22:01:01 alpha ppp[388]: tun0: Chat: Received: 44000 V42bis^M Jan 9 22:01:02 alpha ppp[388]: tun0: Chat: Received: Welcome to CyberConnectics (Portland Server)^M Jan 9 22:01:02 alpha ppp[388]: tun0: Chat: Received: ^M Jan 9 22:01:02 alpha ppp[388]: tun0: Chat: Received: ^M Jan 9 22:01:02 alpha ppp[388]: tun0: Chat: Received: login: Jan 9 22:01:02 alpha ppp[388]: tun0: Chat: Send: Pwwoods^M Jan 9 22:01:02 alpha ppp[388]: tun0: Chat: Expect(5): word: Jan 9 22:01:02 alpha ppp[388]: tun0: Chat: Received: Pwwoods^M Jan 9 22:01:02 alpha ppp[388]: tun0: Chat: Received: Password: Jan 9 22:01:02 alpha ppp[388]: tun0: Chat: Send: dataf^M Jan 9 22:01:02 alpha ppp[388]: tun0: Phase: deflink: login -> lcp Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: FSM: Using "deflink" as a transport Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: deflink: State change Initial --> Closed Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: deflink: State change Closed --> Stopped Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: deflink: RecvConfigReq(1) state = Stopped Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x3dec7f94 Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: deflink: SendConfigAck(1) state = Stopped Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: deflink: LayerStart Jan 9 22:01:02 alpha ppp[388]: tun0: LCP: deflink: State change Stopped --> Ack-Sent Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: deflink: RecvConfigReq(2) state = Ack-Sent Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: deflink: SendConfigAck(2) state = Ack-Sent Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: deflink: SendConfigReq(1) state = Ack-Sent Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:05 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x3dec7f94 Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: deflink: RecvConfigReq(3) state = Ack-Sent Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: deflink: SendConfigAck(3) state = Ack-Sent Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: deflink: SendConfigReq(1) state = Ack-Sent Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:08 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x3dec7f94 Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: deflink: RecvConfigReq(4) state = Ack-Sent Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: deflink: SendConfigAck(4) state = Ack-Sent Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:11 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:12 alpha ppp[388]: tun0: LCP: deflink: SendConfigReq(1) state = Ack-Sent Jan 9 22:01:12 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:12 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:12 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:12 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:12 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x3dec7f94 Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: deflink: RecvConfigReq(5) state = Ack-Sent Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: deflink: SendConfigAck(5) state = Ack-Sent Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:14 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:15 alpha ppp[388]: tun0: LCP: deflink: SendConfigReq(1) state = Ack-Sent Jan 9 22:01:15 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:15 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:15 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:15 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:15 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x3dec7f94 Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: deflink: RecvConfigReq(6) state = Ack-Sent Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: deflink: SendConfigAck(6) state = Ack-Sent Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: MRU[4] 1500 Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: MAGICNUM[6] 0x4a62ddbf Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: PROTOCOMP[2] Jan 9 22:01:17 alpha ppp[388]: tun0: LCP: ACFCOMP[2] Jan 9 22:01:18 alpha ppp[388]: tun0: LCP: deflink: LayerFinish Jan 9 22:01:18 alpha ppp[388]: tun0: LCP: deflink: State change Ack-Sent --> Stopped Jan 9 22:01:18 alpha ppp[388]: tun0: LCP: deflink: State change Stopped --> Closed Jan 9 22:01:18 alpha ppp[388]: tun0: LCP: deflink: State change Closed --> Initial Jan 9 22:01:18 alpha ppp[388]: tun0: Phase: deflink: Disconnected! Jan 9 22:01:18 alpha ppp[388]: tun0: Phase: deflink: lcp -> logout Jan 9 22:01:18 alpha ppp[388]: tun0: Phase: deflink: logout -> hangup Jan 9 22:01:18 alpha ppp[388]: tun0: Phase: deflink: Disconnected! Jan 9 22:01:18 alpha ppp[388]: tun0: Phase: deflink: Connect time: 45 secs: 378 octets in, 577 octets out Jan 9 22:01:18 alpha ppp[388]: tun0: Phase: total 21 bytes/sec, peak 76 bytes/sec on Sun Jan 9 22:01:18 2000 Jan 9 22:01:18 alpha ppp[388]: tun0: Phase: deflink: hangup -> closed Jan 9 22:01:18 alpha ppp[388]: tun0: Phase: bundle: Dead Jan 9 22:01:39 alpha ppp[388]: tun0: Command: /dev/tty: quit all Jan 9 22:01:39 alpha ppp[388]: tun0: Phase: PPP Terminated (normal). ---------------------------------- E-Mail: William Woods Date: 09-Jan-00 Time: 14:17:46 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 14:48: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from supra.rotterdam.luna.net (supra.rotterdam.luna.net [194.151.24.24]) by hub.freebsd.org (Postfix) with ESMTP id 3AAFE14C27 for ; Sun, 9 Jan 2000 14:47:58 -0800 (PST) (envelope-from stephanb@luna.nl) Received: (from stephanb@localhost) by supra.rotterdam.luna.net (•8.8.8/tcpwrp+ismx/8.8.8/chk+tcpwrpr) id XAA11875 for freebsd-current@FreeBSD.ORG; Sun, 9 Jan 2000 23:47:55 +0100 (CET) Date: Sun, 9 Jan 2000 23:47:55 +0100 From: Stephan van Beerschoten To: freebsd-current@FreeBSD.ORG Subject: Re: PPP connections die in current.... Message-ID: <20000109234755.B11681@supra.rotterdam.luna.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from William Woods on Sun, Jan 09, 2000 at 02:20:51PM -0800 Organization: Luna Internet Services http://www.luna.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 09, 2000 at 02:20:51PM -0800, William Woods wrote: > Running 4.0 -current as of today.....on a DEC Alphaststion 233 when I dial out > I connect for about 30 seconds then it dies...here is a copy of the ppp.log I got the same thing once in a while. I'm using PPPoE. I cannot quote the 4 referring lines out of the logs, they have already scrolled out. But i'm talking about a daily updated cvs-system and almost (bi)-weekly compiled worlds. -Steve -- Stephan van Beerschoten Email: stephanb@luna.nl Network Engineer Luna Internet Services PGP fingerprint 4557 9761 B212 FB4C 778D 3529 C42A 2D27 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 16:12: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from fep01-svc.mail.telepac.pt (fep01-svc.mail.telepac.pt [194.65.5.200]) by hub.freebsd.org (Postfix) with ESMTP id 8F9BB14D65 for ; Sun, 9 Jan 2000 16:11:55 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: from manecao.tafkap.priv ([194.65.203.124]) by fep01-svc.mail.telepac.pt (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000110001416.JIVF19279.fep01-svc.mail.telepac.pt@manecao.tafkap.priv> for ; Mon, 10 Jan 2000 00:14:16 +0000 Content-Length: 752 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 10 Jan 2000 00:11:27 -0000 (GMT) From: Joao Pedras To: freebsd-current@freebsd.org Subject: freezing... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all! Just wanted to ask if anyone else experiences hangs when just compiling something, while using X ? I know this is quite vague but I don't see any other pattern than this. I tested with different window managers, compiling different stuff and sometimes this misteriously happens. This hardware has always been reliable (was?) Joao ^\ /^ O O ----------------------------------------o00-(_)-00o-------------------------- Computers are not intelligent. They only think they are. ----------------------------------------------------------------------------- PGP key available upon request or may be cut at http://pedras.webvolution.net/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 16:19:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (pD4B89036.dip0.t-ipconnect.de [212.184.144.54]) by hub.freebsd.org (Postfix) with ESMTP id 3751714A08; Sun, 9 Jan 2000 16:19:08 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id CAA00334; Mon, 10 Jan 2000 02:21:54 +0100 (CET) (envelope-from cc@devcon.net) Date: Mon, 10 Jan 2000 02:21:54 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: current@freebsd.org Cc: gibbs@freebsd.org Subject: kernel panics when initializing aic7895 controller at startup. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, with the latest changes to src/sys/pci/pci_ahc.c (partity error handling), i'm unable to boot a current kernel, because of panic during system boot. i've attached dmesg from a working kernel version (2000/01/06) to this mail. marked with (***) you'll find the line, where (with the new kernel) the error message "ahc0: brkadrintr, Data-path Parity Error at seqaddr = 0x14e" occurs. any ideas, that could help? -- Christian ... ahc0: irq 16 at device 18.0 on pci0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: irq 16 at device 18.1 on pci0 ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs ... Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8) da1: 1042MB (2134305 512 byte sectors: 64H 32S/T 1042C) Mounting root from ufs:/dev/da0a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 1003MB (2055035 512 byte sectors: 64H 32S/T 1003C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 8.333MB/s transfers (8.333MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed da2 at ahc1 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da2: 4134MB (8467200 512 byte sectors: 64H 32S/T 4134C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 16:28: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (p3E9EBFCB.dip0.t-ipconnect.de [62.158.191.203]) by hub.freebsd.org (Postfix) with ESMTP id 6212414C95 for ; Sun, 9 Jan 2000 16:27:59 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id CAA00518; Mon, 10 Jan 2000 02:30:42 +0100 (CET) (envelope-from cc@devcon.net) Date: Mon, 10 Jan 2000 02:30:42 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: Joao Pedras Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Joao Pedras wrote: > Just wanted to ask if anyone else experiences hangs when just compiling > something, while using X ? > > I know this is quite vague but I don't see any other pattern than this. I > tested with different window managers, compiling different stuff and sometimes > this misteriously happens. > > This hardware has always been reliable (was?) same on my machine. my hardware has not been unstable, but since 3 or 4 days ago, i see my system hanging without _any_ message, keyboard freezed, etc.pp. not only when running x11. seems to be some problem with the current kernel version. sorry, i probably can't do much debugging work in this case, as i don't see any error message. the kernel is not even dropping me to ddb. btw, this is a 2 processor pII and i haven't tried disabling SMP yet. -- Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 16:44:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from fep01-svc.mail.telepac.pt (fep01-svc.mail.telepac.pt [194.65.5.200]) by hub.freebsd.org (Postfix) with ESMTP id 233CC14A11 for ; Sun, 9 Jan 2000 16:44:30 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: from manecao.tafkap.priv ([194.65.203.124]) by fep01-svc.mail.telepac.pt (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000110004654.JKXM19279.fep01-svc.mail.telepac.pt@manecao.tafkap.priv>; Mon, 10 Jan 2000 00:46:54 +0000 Content-Length: 1438 Message-ID: X-Mailer: XFMail 1.3.1 [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: Date: Mon, 10 Jan 2000 00:43:49 -0000 (GMT) From: Joao Pedras To: Christian Carstensen Subject: Re: freezing... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mine's a single processor system PPro200 on Intel VS440FX w/64Mb RAM it just... freezes! my smp system is running -stable, yet! Christian Carstensen wrote: > On Mon, 10 Jan 2000, Joao Pedras wrote: > >> Just wanted to ask if anyone else experiences hangs when just compiling >> something, while using X ? >> >> I know this is quite vague but I don't see any other pattern than this. I >> tested with different window managers, compiling different stuff and >> sometimes >> this misteriously happens. >> >> This hardware has always been reliable (was?) > > same on my machine. my hardware has not been unstable, but since 3 or 4 > days ago, i see my system hanging without _any_ message, keyboard freezed, > etc.pp. not only when running x11. seems to be some problem with the > current kernel version. > sorry, i probably can't do much debugging work in this case, as i don't > see any error message. the kernel is not even dropping me to ddb. > btw, this is a 2 processor pII and i haven't tried disabling SMP yet. > > -- > Christian ^\ /^ O O ----------------------------------------o00-(_)-00o-------------------------- Excellent time to become a missing person. ----------------------------------------------------------------------------- PGP key available upon request or may be cut at http://pedras.webvolution.net/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 17:35:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id B4FB514E72 for ; Sun, 9 Jan 2000 17:35:30 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA05913 for ; Sun, 9 Jan 2000 20:34:15 -0500 (EST) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id UAA01119 for ; Sun, 9 Jan 2000 20:34:12 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA01115 for ; Sun, 9 Jan 2000 20:34:12 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Sun, 9 Jan 2000 20:34:11 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: current crash Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My latest kernel with a cvsup as of around 5 minutes ago seems to have a problem: Whenever I start xmms, it panics. The xmms window doesn't even appear, the computer just locks, and I press enter a few times, and the computer then reboots. I'm not sure why this happens, and I can't switch out of X to the console vty fast enough to catch what happens... ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 17:51:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (p3E9EBEAB.dip0.t-ipconnect.de [62.158.190.171]) by hub.freebsd.org (Postfix) with ESMTP id 1662614E3F for ; Sun, 9 Jan 2000 17:51:04 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id DAA00470; Mon, 10 Jan 2000 03:53:47 +0100 (CET) (envelope-from cc@devcon.net) Date: Mon, 10 Jan 2000 03:53:47 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: Joao Pedras Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok, last mail before going to bed, > it just... freezes! maybe, that's not interesting at all, but every time the error occured on my system, there was much disk usage (buildworld, cron scripts, ... netscape ;)). -- Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 17:58:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 4098A14F8D for ; Sun, 9 Jan 2000 17:58:14 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 4EA2D1DA7; Mon, 10 Jan 2000 02:58:13 +0100 (CET) Date: Mon, 10 Jan 2000 02:58:13 +0100 From: "Dave J. Boers" To: Joao Pedras , cc@devcon.net Cc: freebsd-current@freebsd.org Subject: Re: freezing... Message-ID: <20000110025813.A353@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jpedras@webvolution.net on Mon, Jan 10, 2000 at 12:43:49AM -0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 12:43:49AM -0000, Joao Pedras wrote: > it just... freezes! Can any of you tell me wether you have SCSI in your system (the ahc driver, perhaps)? I too had one of these strange lockups today (see earlier post) and it seems SCSI related. The lockup occured during an I/O operation. Now I cvsupped and I find the ahc driver panic-ing on boot time with a parity error as well. I was actually on the verge of concluding that it had to be a hardware error, but doubts begin to raise again... Regards, Dave Boers. -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 18: 4:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (p3E9D0D9B.dip0.t-ipconnect.de [62.157.13.155]) by hub.freebsd.org (Postfix) with ESMTP id 6DE1F14CFB for ; Sun, 9 Jan 2000 18:04:21 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id EAA00542; Mon, 10 Jan 2000 04:07:04 +0100 (CET) (envelope-from cc@devcon.net) Date: Mon, 10 Jan 2000 04:07:04 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: "Dave J. Boers" Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing... In-Reply-To: <20000110025813.A353@relativity.student.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Dave J. Boers wrote: > Can any of you tell me wether you have SCSI in your system (the ahc > driver, perhaps)? I too had one of these strange lockups today (see earlier > post) and it seems SCSI related. The lockup occured during an I/O > operation. > > Now I cvsupped and I find the ahc driver panic-ing on boot time with a > parity error as well. welcome to the club. world's getting more amazing with every checkout ;) -- Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 18: 7:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (p3E9D0D9B.dip0.t-ipconnect.de [62.157.13.155]) by hub.freebsd.org (Postfix) with ESMTP id B7FDC14C34 for ; Sun, 9 Jan 2000 18:07:51 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id EAA00555; Mon, 10 Jan 2000 04:10:37 +0100 (CET) (envelope-from cc@devcon.net) Date: Mon, 10 Jan 2000 04:10:37 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: "Dave J. Boers" Cc: Joao Pedras , freebsd-current@freebsd.org Subject: Re: freezing... In-Reply-To: <20000110025813.A353@relativity.student.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok, this runs stable for 3 hours now... try a current kernel (checked out 4 hours ago), using a version of the file /usr/src/sys/pci/ahc_pci.c from 2000/01/06. ok, maybe it's not by any means stable, but works better than everything else within the last 24 hours. -- Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 18:21:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 54B8614D55 for ; Sun, 9 Jan 2000 18:21:41 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 8A8F11DA7; Mon, 10 Jan 2000 03:20:17 +0100 (CET) Date: Mon, 10 Jan 2000 03:20:17 +0100 From: "Dave J. Boers" To: Christian Carstensen Cc: Joao Pedras , freebsd-current@freebsd.org Subject: Re: freezing... Message-ID: <20000110032017.A499@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000110025813.A353@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cc@devcon.net on Mon, Jan 10, 2000 at 04:10:37AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 04:10:37AM +0100, Christian Carstensen wrote: > this runs stable for 3 hours now... > try a current kernel (checked out 4 hours ago), using a version of the > file /usr/src/sys/pci/ahc_pci.c from 2000/01/06. ok, maybe it's not by any > means stable, but works better than everything else within the last 24 > hours. Actually, I've booted a kernel from just before newyear (28 december) which works _reasonably_ fine (although it's the same kernel that gave me the lockup earlier) with a userland of today. Problem is that the lockups (I think) are ahc-related and my SCSI hard drive did refuse to come online on one or two occasions while booting the system cold... I therefore concluded that it might be a problem with the hardware. Now (with the new kernel) I find the scsi system unstable and I have doubts again. One piece of information might also be useful in this context. After the system lockup I sort of benchmarked the scsi performance by doing "dd if=/dev/zero of=./testfile bs=1000000 count=128" (actually I varied the blocksize) and got a _very poor_ performance of only 4 Mb/sec (which is usually around 10 to 12 Mb/sec). I isolated my drive to be the only scsi device and I even clocked the SCSI bus down from 20 Mhz to 8 Mhz, but to no avail. In the mean time, I disconnected my scsi hard drive and I am running from my IDE disk. Regards, Dave Boers. -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 18:31:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-89.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.217]) by hub.freebsd.org (Postfix) with ESMTP id 10F9514D1A for ; Sun, 9 Jan 2000 18:31:25 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA24833; Mon, 10 Jan 2000 02:30:51 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA04306; Mon, 10 Jan 2000 01:49:45 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001100149.BAA04306@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: obrien@NUXI.com Cc: Brian Somers , freebsd-current@FreeBSD.org, brian@hak.lan.Awfulhak.org, brian@hak.lan.Awfulhak.org Subject: Re: hak.lan.Awfulhak.org daily run output In-Reply-To: Message from "David O'Brien" of "Sat, 08 Jan 2000 10:23:12 PST." <20000108102312.I1417@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Jan 2000 01:49:45 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Jan 07, 2000 at 08:32:19AM +0000, Brian Somers wrote: > > Anyone know what's changed with `calendar' ? I suspect it's the > > recent cpp changes. > > Please test this patch. [.....] Yep, this works. Of course I expect it'll only really work for gnu's cpp... I'd say go for it though. Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 18:46:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (p3E9D0D20.dip0.t-ipconnect.de [62.157.13.32]) by hub.freebsd.org (Postfix) with ESMTP id 4390414EDB for ; Sun, 9 Jan 2000 18:46:32 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id EAA00383; Mon, 10 Jan 2000 04:48:14 +0100 (CET) (envelope-from cc@devcon.net) Date: Mon, 10 Jan 2000 04:48:08 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: "Dave J. Boers" Cc: freebsd-current@freebsd.org Subject: Re: freezing... In-Reply-To: <20000110032017.A499@relativity.student.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > this runs stable for 3 hours now... > > try a current kernel (checked out 4 hours ago), using a version of the > > file /usr/src/sys/pci/ahc_pci.c from 2000/01/06. ok, maybe it's not by any > > means stable, but works better than everything else within the last 24 > > hours. grrr, after 10 mins fsck... i was wrong. > Problem is that the lockups (I think) are ahc-related and my SCSI hard > drive did refuse to come online on one or two occasions while booting the > system cold... I therefore concluded that it might be a problem with the > hardware. Now (with the new kernel) I find the scsi system unstable and I > have doubts again. i'm using a ahc 7895 onboard on a tyan thunder 100. i've seen my cdrom occasionally not coming up until power cycling. is this a known bug with that controller? > One piece of information might also be useful in this context. After the > system lockup I sort of benchmarked the scsi performance by doing "dd > if=/dev/zero of=./testfile bs=1000000 count=128" (actually I varied the > blocksize) and got a _very poor_ performance of only 4 Mb/sec (which is > usually around 10 to 12 Mb/sec). I isolated my drive to be the only scsi > device and I even clocked the SCSI bus down from 20 Mhz to 8 Mhz, but to no > avail. scsi performance is very bad on my system for a long time now. operating on many small files, for example, my IBM DCAS-34330W is 100% busy with only 1.2 MB/s. i don't know why, but i suspect vinum in combination with some old scsi devices to cause that. -- Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 19:13:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 0EDCD14C01 for ; Sun, 9 Jan 2000 19:13:29 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 209E61DA7; Mon, 10 Jan 2000 04:13:13 +0100 (CET) Date: Mon, 10 Jan 2000 04:13:13 +0100 From: "Dave J. Boers" To: Christian Carstensen Cc: freebsd-current@freebsd.org Subject: Re: freezing... Message-ID: <20000110041313.C655@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000110032017.A499@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cc@devcon.net on Mon, Jan 10, 2000 at 04:48:08AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 04:48:08AM +0100, Christian Carstensen wrote: > i'm using a ahc 7895 onboard on a tyan thunder 100. i've seen my cdrom > occasionally not coming up until power cycling. is this a known bug with > that controller? Mine is an AIC 7860 (i.e. 2940UA). I see my hard disk failing to come up occasionally, but only after I turn my power on after the system had been turned completely off (which is not often). > scsi performance is very bad on my system for a long time now. operating > on many small files, for example, my IBM DCAS-34330W is 100% busy with > only 1.2 MB/s. > i don't know why, but i suspect vinum in combination with some old scsi > devices to cause that. What I'm going to say here may be complete crap, but it has been on my mind for some time now, so I may just as well speak up with my suspicions. I have read on several occasions that people find -current performing very poorly lately. I recall someone comparing -current's network performance to that of 3.4 and finding almost a factor 2 difference. I myself have found the following facts lately: 1) scsi performance is down to 4 Mb/sec MAX, writing simply zero's (this used to be around 12 Mb/sec) 2) network performance (NIC = 3COM 3C905B-TX 100Mbit) is 5 Mb/sec MAX instead of the 8 Mb/sec I'm used to. 3) IDE UDMA66 performance is down to 12 Mb/sec writing zero's (this used to be near 16 Mb/sec). 4) buildworlds are at an all time slow. I haven't been able to compile a current in less than an hour for many weeks now. This used to be more like 40 minutes or so (make buildworld -j 9 on my smp system). Add to this the strange lockups we've been having recently that somehow seem i/o or load dependent. I'm no expert on this at all, but it seems legitimate to conclude that something is seriously wrong somewhere. It seems to me that this should _definitely_ get sorted out to the bottom before release time. Regards, Dave Boers. -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 20:13:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailext04.compaq.com (mailext04.compaq.com [207.18.199.42]) by hub.freebsd.org (Postfix) with ESMTP id CC96E15397 for ; Sun, 9 Jan 2000 20:13:37 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext04.compaq.com (Postfix, from userid 12345) id BED3A104BBE; Sun, 9 Jan 2000 22:13:36 -0600 (CST) Received: from mailint11.im.hou.compaq.com (mailint11.compaq.com [207.18.199.189]) by mailext04.compaq.com (Postfix) with ESMTP id B9586FB101; Sun, 9 Jan 2000 22:13:36 -0600 (CST) Received: by mailint11.im.hou.compaq.com (Postfix, from userid 12345) id 714F255F02; Sun, 9 Jan 2000 22:13:29 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [16.158.59.135]) by mailint11.im.hou.compaq.com (Postfix) with ESMTP id CE15252D01; Sun, 9 Jan 2000 22:13:27 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id QAA00644; Sun, 9 Jan 2000 16:47:36 +0800 (SGT) (envelope-from grog) Date: Sun, 9 Jan 2000 16:47:36 +0800 From: Greg Lehey To: Brad Knowles Cc: Brad Chisholm , freebsd-current@FreeBSD.ORG Subject: RAID benchmarks (was: Adaptec AAC-364 RAID controller support) Message-ID: <20000109164735.B515@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <200001072210.AA10196@newlgn49.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blk@skynet.be on Fri, Jan 07, 2000 at 11:33:20PM +0100 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 7 January 2000 at 23:33:20 +0100, Brad Knowles wrote: > At 5:10 PM -0500 2000/1/7, Brad Chisholm wrote: > >> The Adaptec card looks like it might provide a superior solution. What's >> best way to proceed when trying to get documentation support from vendors? > > Look long and hard at software solutions with vinum before you > wed yourself to a particular hardware RAID controller. At the very > least, I'd encourage you to extensively benchmark all the candidate > solutions in your environment, before you make a choice. > > You can see my own benchmarks that I've done so far at > . I hate to say this, but the results are meaningless for the sequential case; the version of rawio you used started all parallel sequential transfers at the same place, so the results showed primarily how much cache each device had. I've updated rawio and the port, and if you (anybody) are really interested in sequential performance, you should run the tests again. My take on this is that sequential performance is only interesting in a few unusual cases, such as streaming video, and the performance isn't nearly as good as you think as soon as you introduce more than one client process. 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-current" in the body of the message From owner-freebsd-current Sun Jan 9 20:13:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailext12.compaq.com (mailext12.compaq.com [207.18.199.188]) by hub.freebsd.org (Postfix) with ESMTP id 8E580152F9 for ; Sun, 9 Jan 2000 20:13:36 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext12.compaq.com (Postfix, from userid 12345) id B4C5C5782B; Sun, 9 Jan 2000 22:13:33 -0600 (CST) Received: from mailint11.im.hou.compaq.com (mailint11.compaq.com [207.18.199.189]) by mailext12.compaq.com (Postfix) with ESMTP id A3ADC54601; Sun, 9 Jan 2000 22:13:33 -0600 (CST) Received: by mailint11.im.hou.compaq.com (Postfix, from userid 12345) id 5674255F02; Sun, 9 Jan 2000 22:13:26 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [16.158.59.135]) by mailint11.im.hou.compaq.com (Postfix) with ESMTP id BA8D252D01; Sun, 9 Jan 2000 22:13:24 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id RAA00767; Sun, 9 Jan 2000 17:04:33 +0800 (SGT) (envelope-from grog) Date: Sun, 9 Jan 2000 17:04:33 +0800 From: Greg Lehey To: Soren Schmidt Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: ATA lost contact Message-ID: <20000109170433.F515@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <200001050902.KAA41882@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: <200001050902.KAA41882@freebsd.dk>; from sos@freebsd.dk on Wed, Jan 05, 2000 at 10:02:53AM +0100 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 5 January 2000 at 10:02:53 +0100, Søren Schmidt wrote: > It seems Kris Kennaway wrote: >> On Wed, 5 Jan 2000, Soren Schmidt wrote: >> >>> The disk probably has problems with DMA mode (lots of older WD disks >>> has that). You only get WDMA2 mode since you controller is an older >>> Intel PIIX that can't do UDMA... >> >> Hmm..This disk was bought in about March 99..you're sure that's the >> reason? > > No, but I've had my share of bad experiences with WD disks in that > regard, I'll have to look up the modelnumber to be sure... I think the real issue is: did it work under DMA with the wd driver? If so, it should work with the at driver as well. 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-current" in the body of the message From owner-freebsd-current Sun Jan 9 20:15:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailext03.compaq.com (mailext03.compaq.com [207.18.199.41]) by hub.freebsd.org (Postfix) with ESMTP id F2AC714CB8; Sun, 9 Jan 2000 20:15:12 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext03.compaq.com (Postfix, from userid 12345) id 8678315200B; Sun, 9 Jan 2000 22:15:09 -0600 (CST) Received: from mailint11.im.hou.compaq.com (mailint11.compaq.com [207.18.199.189]) by mailext03.compaq.com (Postfix) with ESMTP id 7FBD9148506; Sun, 9 Jan 2000 22:15:09 -0600 (CST) Received: by mailint11.im.hou.compaq.com (Postfix, from userid 12345) id 2CF3255F02; Sun, 9 Jan 2000 22:15:02 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [16.158.59.135]) by mailint11.im.hou.compaq.com (Postfix) with ESMTP id 0AC5252D01; Sun, 9 Jan 2000 22:15:00 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id NAA00358; Sun, 9 Jan 2000 13:18:06 +0800 (SGT) (envelope-from grog) Date: Sun, 9 Jan 2000 13:18:05 +0800 From: Greg Lehey To: "Jordan K. Hubbard" Cc: "Kenneth D. Merry" , current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Message-ID: <20000109131805.A330@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <20000106191051.A40270@panzer.kdm.org> <6956.947217921@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <6956.947217921@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 06, 2000 at 08:05:21PM -0800 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 6 January 2000 at 20:05:21 -0800, Jordan K. Hubbard wrote: > Also, I can now add that cdda2wav does work (hurrah), but it does yelp > that it can't read the CD TOC. > > Of course, the mystery is that tosha no longer works yet was not > changed, nor was the ripit script I call tosha from, so something on > our side of the fence also moved with respect to this drive. > > Any other SCSI CD owners here currently using tosha? I'd be > quite interested to know if this is drive-specific. Not quite the answer you're looking for, but maybe a data point: I get very similar results on my laptop with the ata driver. dd fails with I/O error, and the driver reports: Jan 9 13:08:13 mojave /kernel: acd0: READ_BIG - ILLEGAL REQUEST asc=64 ascq=00 error=04 After that, I was no longer able to access the CD, and I had to reboot the machine. I might have got away with removing the CD-ROM drive, but I didn't think of that until I had rebooted. 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-current" in the body of the message From owner-freebsd-current Sun Jan 9 20:15:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailext03.compaq.com (mailext03.compaq.com [207.18.199.41]) by hub.freebsd.org (Postfix) with ESMTP id A857E15A0F; Sun, 9 Jan 2000 20:15:21 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext03.compaq.com (Postfix, from userid 12345) id 914B815200C; Sun, 9 Jan 2000 22:15:20 -0600 (CST) Received: from mailint11.im.hou.compaq.com (mailint11.compaq.com [207.18.199.189]) by mailext03.compaq.com (Postfix) with ESMTP id 88668148506; Sun, 9 Jan 2000 22:15:20 -0600 (CST) Received: by mailint11.im.hou.compaq.com (Postfix, from userid 12345) id 31D5255F02; Sun, 9 Jan 2000 22:15:13 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [16.158.59.135]) by mailint11.im.hou.compaq.com (Postfix) with ESMTP id 89B9252D01; Sun, 9 Jan 2000 22:15:10 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id QAA00596; Sun, 9 Jan 2000 16:33:14 +0800 (SGT) (envelope-from grog) Date: Sun, 9 Jan 2000 16:33:14 +0800 From: Greg Lehey To: Darren Reed , Mike Smith Cc: Warner Losh , joe@pavilion.net, dillon@apollo.backplane.com, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th) Message-ID: <20000109163314.A515@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <200001071246.XAA05593@avalon.reed.wattle.id.au> <200001072052.MAA01482@mass.cdrom.com> <200001062246.PAA80310@harmony.village.org> <200001071246.XAA05593@avalon.reed.wattle.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001071246.XAA05593@avalon.reed.wattle.id.au>; from darrenr@reed.wattle.id.au on Fri, Jan 07, 2000 at 11:46:49PM +1100 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 7 January 2000 at 23:46:49 +1100, Darren Reed wrote: > In some email I received from Warner Losh, sie wrote: >> >> In message <20000106212050.D95011@florence.pavilion.net> Josef Karthauser writes: >> : My 3c589d works just fine now, along with suspend/resume :) (under 4.0). >> >> The issue with the 3c589d is with its speed. It is falling back to >> the timeout routine to send data rather than getting an interrupt when >> the tx has happened (or something like this, I'm reporting second hand >> stuff). > > Whatever it is, results in ping times being 1000ms then 10ms then 1000ms > then 10ms...when it responds. This doesn't look typical of the problems we've been discussing. First, they appear to occur more with -CURRENT, and secondly they don't affect the ping times. What I've been seeing is that everything is fine until a collision occurs, after which something times out and it takes a 1 second timeout before it continues. It's easiest to see with long ftp transfers. > i.e. it's a mistake to use FreeBSD 3.x with the 3c589d. Mine worked fine under 3.x. The problem seems to have crept in in about October last year (1999). On Friday, 7 January 2000 at 12:52:28 -0800, Mike Smith wrote: >>> The issue with the 3c589d is with its speed. It is falling back to >>> the timeout routine to send data rather than getting an interrupt when >>> the tx has happened (or something like this, I'm reporting second hand >>> stuff). >> >> Whatever it is, results in ping times being 1000ms then 10ms then 1000ms >> then 10ms...when it responds. > > This is typical for interrupt misconfiguration for this driver. When you > get the interrupt configuration right, it works fine. > > (No, getting the interrupt configuration right is not a trivial task.) That may be the answer for Darren's problem. It's definitely not the case for the ones we have been discussing on -mobile. 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-current" in the body of the message From owner-freebsd-current Sun Jan 9 20:29:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 865201515D for ; Sun, 9 Jan 2000 20:29:41 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA29128; Sun, 9 Jan 2000 21:26:44 -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.9.3/8.8.3) with ESMTP id VAA03237; Sun, 9 Jan 2000 21:26:45 -0700 (MST) Message-Id: <200001100426.VAA03237@harmony.village.org> To: Greg Lehey Subject: Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th) Cc: current@FreeBSD.org In-reply-to: Your message of "Sun, 09 Jan 2000 16:33:14 +0800." <20000109163314.A515@mojave.worldwide.lemis.com> References: <20000109163314.A515@mojave.worldwide.lemis.com> <200001071246.XAA05593@avalon.reed.wattle.id.au> <200001072052.MAA01482@mass.cdrom.com> <200001062246.PAA80310@harmony.village.org> <200001071246.XAA05593@avalon.reed.wattle.id.au> Date: Sun, 09 Jan 2000 21:26:45 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [[ Moved to just current ]] In message <20000109163314.A515@mojave.worldwide.lemis.com> Greg Lehey writes: : That may be the answer for Darren's problem. It's definitely not the : case for the ones we have been discussing on -mobile. There are definitely known issues with the ep0 driver. Right now it doesn't interrupt quite right on Rx packets. That's the majority of the problems in current driver, at least with the 3c589D that I have. I see only about 150kBps from the card. I've not had time to deal with looking for this problem. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 21:28:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1484814F40 for ; Sun, 9 Jan 2000 21:28:22 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA27220; Mon, 10 Jan 2000 16:26:35 +1100 Date: Mon, 10 Jan 2000 16:26:32 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: John Polstra Cc: current@freebsd.org Subject: Re: __sigisempty() undefined if "cc -g" used. In-Reply-To: <200001092124.NAA65356@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 9 Jan 2000, John Polstra wrote: > In article , > Bruce Evans wrote: > > > > You apparently > > clobbered -O in CFLAGS by setting CFLAGS=-g. -g normally needs to be > > added to CC to avoid breaking CFLAGS (CC='cc -g'). > > Better yet: DEBUG_FLAGS=-g Except it only supported in bsd.prog.mk and bsd.lib.mk, but not in bsd.kmod.mk, kernel Makefiles, or if no bsd .mk files are included A few verbose module makefiles add it explicitly. You can also use COPTS, but it is only supported in bsd.prog.mk, bsd.kmod.mk and kernel Makefiles. The ordering of these macros is important but very obscure. E.g., if the default options contain -g, then you may want kill -g by adding -g0 after -g. ${DEBUG_FLAGS} seems to be added last, so it works right. Not so for ${COPTS}. It is added before ${CWARNFLAGS}, so it can't be used to kill unwanted warning flags. I think COPTS and DEBUG_FLAGS should be reserved for users, but COPTS is used by 16 Makefiles in the src tree, e.g., ping/Makefile. Its use there is 100% wrong since it is used for warning flags and a non- option. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 21:30:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 949841522F for ; Sun, 9 Jan 2000 21:30:12 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id VAA46855; Sun, 9 Jan 2000 21:30:09 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id VAA78037; Sun, 9 Jan 2000 21:30:09 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001100530.VAA78037@realtime.exit.com> Subject: Re: neomagic 256av/256zx audio In-Reply-To: <001001bf5a7a$c4b88440$0304020a@rings> from Cameron Grant at "Jan 9, 2000 08:23:11 am" To: gandalf@vilnya.demon.co.uk (Cameron Grant) Date: Sun, 9 Jan 2000 21:30:09 -0800 (PST) Cc: current@freebsd.org Reply-To: frank@exit.com 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cameron Grant wrote: > i have just committed a driver for the neomagic chips. please test and post > results. Okay. I have a Dell Inspiron 3500, with a NeoMagic 256AV chipset in it. It hangs on boot, in nm_rd() line 146. Here's the backtrace: (kgdb) bt #0 nm_rd (sc=0xc0d83100, regno=1536, size=2) at ../../dev/sound/pci/neomagic.c:146 #1 0xc0206ac7 in nm_rdcd (devinfo=0xc0d83100, regno=0) at ../../dev/sound/pci/neomagic.c:232 #2 0xc020219e in ac97_init (codec=0xc0d83000) at ../../dev/sound/pcm/ac97.c:251 #3 0xc0202376 in ac97mix_init (m=0xc073d30c) at ../../dev/sound/pcm/ac97.c:304 #4 0xc02050b4 in mixer_init (d=0xc073d200, m=0xc0288120, devinfo=0xc0d83000) at ../../dev/sound/pcm/mixer.c:53 #5 0xc020736b in nm_pci_attach (dev=0xc0d87280) at ../../dev/sound/pci/neomagic.c:594 #6 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87280) at device_if.c:63 #7 0xc0148bdb in device_probe_and_attach (dev=0xc0d87280) at ../../kern/subr_bus.c:1137 #8 0xc01498ca in bus_generic_attach (dev=0xc0d87480) at ../../kern/subr_bus.c:1831 #9 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87480) at device_if.c:63 #10 0xc0148bdb in device_probe_and_attach (dev=0xc0d87480) at ../../kern/subr_bus.c:1137 #11 0xc01498ca in bus_generic_attach (dev=0xc0d87b80) at ../../kern/subr_bus.c:1831 #12 0xc01cced5 in pcib_attach (dev=0xc0d87b80) at ../../pci/pcisupport.c:747 #13 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87b80) at device_if.c:63 #14 0xc0148bdb in device_probe_and_attach (dev=0xc0d87b80) at ../../kern/subr_bus.c:1137 #15 0xc01498ca in bus_generic_attach (dev=0xc0d87d80) at ../../kern/subr_bus.c:1831 #16 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87d80) at device_if.c:63 #17 0xc0148bdb in device_probe_and_attach (dev=0xc0d87d80) at ../../kern/subr_bus.c:1137 #18 0xc01498ca in bus_generic_attach (dev=0xc0d86000) at ../../kern/subr_bus.c:1831 #19 0xc011e27e in DEVICE_ATTACH (dev=0xc0d86000) at device_if.c:63 #20 0xc0148bdb in device_probe_and_attach (dev=0xc0d86000) at ../../kern/subr_bus.c:1137 #21 0xc01498ca in bus_generic_attach (dev=0xc0d86080) at ../../kern/subr_bus.c:1831 #22 0xc0230c89 in nexus_attach (dev=0xc0d86080) at ../../i386/i386/nexus.c:199 #23 0xc011e27e in DEVICE_ATTACH (dev=0xc0d86080) at device_if.c:63 #24 0xc0148bdb in device_probe_and_attach (dev=0xc0d86080) at ../../kern/subr_bus.c:1137 #25 0xc0149e0a in root_bus_configure () at ../../kern/subr_bus.c:2214 #26 0xc0227568 in configure (dummy=0x0) at ../../i386/i386/autoconf.c:146 #27 0xc013319c in mi_startup (framep=0xc0325fb4) at ../../kern/init_main.c:217 Here are the values; looks like sh has problems: (kgdb) print /x sh $2 = 0xc87d3000 (kgdb) print *sh $3 = 17 (kgdb) print st $4 = 1 (kgdb) print /x regno $6 = 0x600 (kgdb) print *sc $8 = {dev = 0x11, type = 0, reg = 0x0, irq = 0x0, buf = 0x0, regid = 0, irqid = 32896, bufid = 0, ih = 0x0, ac97_base = 0, ac97_status = 0, ac97_busy = 0, buftop = 0, pbuf = 0, rbuf = 0, cbuf = 0, acbuf = 0, playint = 0, recint = 0, misc1int = 0, misc2int = 0, irsz = 0, badintr = 0, pch = {spd = 0, dir = 0, fmt = 0, buffer = 0x0, channel = 0x0, parent = 0x0}, rch = {spd = 0, dir = 0, fmt = 0, buffer = 0x0, channel = 0x0, parent = 0x0}} Hmm, looks like sc->reg was never filled in. Hope this helps. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 21:46:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 546F815221 for ; Sun, 9 Jan 2000 21:46:43 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id OAA16568; Mon, 10 Jan 2000 14:46:42 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp390.kt.rim.or.jp [202.247.140.90]) by mail1.rim.or.jp (3.7W/) id OAA06304; Mon, 10 Jan 2000 14:46:39 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id OAA08282; Mon, 10 Jan 2000 14:46:37 +0900 (JST) Date: Mon, 10 Jan 2000 14:46:36 +0900 Message-ID: <14457.29244.643560.68187Y@localhost.sky.rim.or.jp> From: Jun Kuriyama To: bmilekic@dsuper.net Cc: current@FreeBSD.ORG Subject: Re: panic at kern/uipc_socket2.c In-Reply-To: In your message of "Fri, 7 Jan 2000 13:42:37 -0500 (EST)" References: <14450.6126.709759.19547O@localhost.sky.rim.or.jp> User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Bosko Milekic > Can you look at kern/10872 and see if your hardware matches Bob's? > (e.g. The infamous fxp and ncr combo.) and regardless, attempt executing > the script that is provided and note whether or not you can reproduce the > panic in sbdrop()? If so, a backtrace and a `print *sb' would be helpful, > certainly. It looks as though some mbufs are literally being `zapped' off > of sb_mb while sb_cc and sb_mbcnt are still greater than zero. Either > that, or something's not adjusting sb_cc and/or sb_mbcnt under the proper > spl which may lead to an interrupt eventually leading to the sbdrop > with an sb_cc and sb_mb that just don't go together. No. I'm using aue (USB ethernet adaptor) and no SCSI subsystem. And I have another problem that I cannot clean re-mount root filesystem everytime. So I cannot get kernel crash dump... But it seems my panic is same as PR mentioned. I'll try with INVARIANTS and activate KASSERT macro. Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 21:46:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id BCFFE14EDB; Sun, 9 Jan 2000 21:46:36 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id OAA16564; Mon, 10 Jan 2000 14:46:35 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp390.kt.rim.or.jp [202.247.140.90]) by mail1.rim.or.jp (3.7W/) id OAA06281; Mon, 10 Jan 2000 14:46:34 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id OAA08279; Mon, 10 Jan 2000 14:46:33 +0900 (JST) Date: Mon, 10 Jan 2000 14:46:32 +0900 Message-ID: <14457.29240.569082.29321F@localhost.sky.rim.or.jp> From: Jun Kuriyama To: current@FreeBSD.org Cc: cg@FreeBSD.org Subject: NeoMagic 256AV Audio Driver User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG New pcm driver found my NeoMagic 256AV's sound device. Great! But in my configuration, pcm0 complains many "pcm0: 1000 bad intrs" on console. Are there some hints to configure this driver? My machine is SONY VAIO PCG-Z505D (Japanese Version). Probed message is here: vga-pci0: mem 0xfed00000-0xfedfffff,0xfe800000-0xfebfffff,0xfd000000-0xfdffffff irq 9 at device 8.0 on pci0 pcm0: mem 0xfec00000-0xfecfffff,0xfe000000-0xfe3fffff irq 9 at device 8.1 on pci0 pcm0: rec buf 0xc5ac5c00 pcm0: play buf 0xc5ac1c00 Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 22: 3: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from spock.org (cm-24-25-148-191.nycap.rr.com [24.25.148.191]) by hub.freebsd.org (Postfix) with ESMTP id 4A16814D05 for ; Sun, 9 Jan 2000 22:02:55 -0800 (PST) (envelope-from jon@spock.org) Received: (from jon@localhost) by spock.org serial EF600Q3T-B7F; Mon, 10 Jan 2000 01:02:40 -0500 (EST) (envelope-from jon) Date: Mon, 10 Jan 2000 01:02:40 -0500 From: Jonathan Chen To: Warner Losh Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th) Message-ID: References: <20000109163314.A515@mojave.worldwide.lemis.com> <200001071246.XAA05593@avalon.reed.wattle.id.au> <200001072052.MAA01482@mass.cdrom.com> <200001062246.PAA80310@harmony.village.org> <200001071246.XAA05593@avalon.reed.wattle.id.au> <20000109163314.A515@mojave.worldwide.lemis.com> <200001100426.VAA03237@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: telnet In-Reply-To: <200001100426.VAA03237@harmony.village.org>; from imp@village.org on Sun, Jan 09, 2000 at 09:26:45PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 09, 2000 at 09:26:45PM -0700, Warner Losh wrote: > [[ Moved to just current ]] > > In message <20000109163314.A515@mojave.worldwide.lemis.com> Greg Lehey writes: > : That may be the answer for Darren's problem. It's definitely not the > : case for the ones we have been discussing on -mobile. > > There are definitely known issues with the ep0 driver. Right now it > doesn't interrupt quite right on Rx packets. That's the majority of > the problems in current driver, at least with the 3c589D that I have. > I see only about 150kBps from the card. I've not had time to deal > with looking for this problem. With what little pccard/ethernet programming experiences I've had, this problem seems to be caused by the interrupt for the card getting lost somewhere before getting processed by the handler. The reason you still get traffic is because of the watchdog. (Try uncommenting the commented out lines in sys/dev/ep/if_ep.c in the function ep_if_watchdog(), you should start seeing lots of kernel messages saying "ep: watchdog".) After looking briefly at the ep files, I saw something that doesn't seem right. In sys/dev/ep/if_ep_pccard.c around line 176, there's a comment that says "Fake IRQ must be 3". Now maybe the card requires it, or maybe the original author just didn't have anything on IRQ 3, I don't know. So, I'd suggest turning off com2 or whatever you have on irq3, -or- change the "fake irq" to something else you do have free on the next line (ie, 0x3000-> 0xa000 if you have IRQ10 free). If this works, great... if not, I hope Warner gets some more free time. ;) As for the other problem with collisions, I did a search on the word collision on sys/dev/ep/if_ep.c, and found only one mention at around line 620. The comment says "TXS_MAX_COLLISION - we shouldn't get here". I suspect it does get there, so I suggest putting a printf there to find out. I also suspect that the card may require a reset or some other stuff if and when it "gets there". If that's the case, someone else with the specs on the 589 cards can look that up and do it. (I'll have to admit, I looked only briefly, and know virtually nothing about how the pccard stuff works on freebsd, have no ep card, nor ever looked at the documentation for it, so what just said may be completely wrong -- don't be surprised if it doesn't work.) -- (o_ 1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2 _o) \\\_\ Jonathan Chen jon@spock.org /_/// <____) The surest protection against temptation is cowardice. --MT (____> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 22: 3: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id DE19A14C5A; Sun, 9 Jan 2000 22:02:48 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 95C301CC6; Mon, 10 Jan 2000 14:02:42 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Jun Kuriyama Cc: current@FreeBSD.org, cg@FreeBSD.org Subject: Re: NeoMagic 256AV Audio Driver In-Reply-To: Message from Jun Kuriyama of "Mon, 10 Jan 2000 14:46:32 +0900." <14457.29240.569082.29321F@localhost.sky.rim.or.jp> Date: Mon, 10 Jan 2000 14:02:42 +0800 From: Peter Wemm Message-Id: <20000110060242.95C301CC6@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jun Kuriyama wrote: > > New pcm driver found my NeoMagic 256AV's sound device. Great! But in > my configuration, pcm0 complains many "pcm0: 1000 bad intrs" on console. This is a bug in neomagic.c and is probably due to you having a shared interrupt.. Suggested fix: Index: neomagic.c =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/pci/neomagic.c,v retrieving revision 1.2 diff -u -r1.2 neomagic.c --- neomagic.c 2000/01/10 01:59:12 1.2 +++ neomagic.c 2000/01/10 06:01:17 @@ -68,7 +68,7 @@ u_int32_t ac97_base, ac97_status, ac97_busy; u_int32_t buftop, pbuf, rbuf, cbuf, acbuf; u_int32_t playint, recint, misc1int, misc2int; - u_int32_t irsz, badintr; + u_int32_t irsz; struct sc_chinfo pch, rch; }; @@ -431,14 +431,8 @@ int status, x; status = nm_rd(sc, NM_INT_REG, sc->irsz); - if (status == 0) { - if (sc->badintr++ > 1000) { - device_printf(sc->dev, "1000 bad intrs\n"); - sc->badintr = 0; - } + if (status == 0) return; - } - sc->badintr = 0; if (status & sc->playint) { status &= ~sc->playint; @@ -507,7 +501,6 @@ sc->misc1int = NM2_MISC_INT_1; sc->misc2int = NM2_MISC_INT_2; } - sc->badintr = 0; ofs = sc->buftop - 0x0400; sc->buftop -= 0x1400; The reason is simple.. when a shared level-sensitive interrupt is triggered, all of the interrupt handlers are called. They have to check their hardware and ask "was this interrupt my responsibility?" and stop immediately if not. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 22:59: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust104.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4381B14E1A; Sun, 9 Jan 2000 22:58:55 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Mon, 10 Jan 2000 01:58:36 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: current@FreeBSD.org Cc: mckusick@FreeBSD.org Subject: SoftUpdates crash with new code Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I'm having problems with SoftUpdates. I've disabled it for now. Here's the backtrace for the crash; more info from the crashdump is available upon request, but I think this is a general problem, and easily reproduced. 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 3272704 initial pcb at 282620 panicstr: softdep_lock: locking against myself panic messages: --- panic: softdep_lock: locking against myself syncing disks... panic: softdep_lock: locking against myself Uptime: 9m58s dumping to dev #ad/0x20001, offset 262144 dump ata0: resetting devices .. done 128 127 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 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 boot (howto=0x104) at ../../kern/kern_shutdown.c:304 304 dumppcb.pcb_cr3 = rcr3(); (kgdb) #0 boot (howto=0x104) at ../../kern/kern_shutdown.c:304 #1 0xc013f5d5 in panic (fmt=0xc023c6e0 "softdep_lock: locking against myself") at ../../kern/kern_shutdown.c:554 #2 0xc01bacc5 in acquire_lock (lk=0xc026635c) at ../../ufs/ffs/ffs_softdep.c:276 #3 0xc01bfdb0 in softdep_count_dependencies (bp=0xc37131d0, wantcount=0x0) at ../../ufs/ffs/ffs_softdep.c:4473 #4 0xc01c2f98 in ffs_fsync (ap=0xd8189b08) at ../../ufs/ffs/ffs_vnops.c:169 #5 0xc01c1b47 in ffs_sync (mp=0xc0b63000, waitfor=0x2, cred=0xc073d600, p=0xc02988a0) at vnode_if.h:537 #6 0xc016b893 in sync (p=0xc02988a0, uap=0x0) at ../../kern/vfs_syscalls.c:549 #7 0xc013f00b in boot (howto=0x100) at ../../kern/kern_shutdown.c:226 #8 0xc013f5d5 in panic (fmt=0xc023c6e0 "softdep_lock: locking against myself") at ../../kern/kern_shutdown.c:554 #9 0xc01bacc5 in acquire_lock (lk=0xc026635c) at ../../ufs/ffs/ffs_softdep.c:276 #10 0xc01bcc38 in indir_trunc (ip=0xd8189c00, dbn=0x800, level=0x0, lbn=0xc, countp=0xd8189bf0) at ../../ufs/ffs/ffs_softdep.c:2024 #11 0xc01bcb15 in handle_workitem_freeblocks (freeblks=0xc0c43d80) at ../../ufs/ffs/ffs_softdep.c:1959 #12 0xc01bc562 in softdep_setup_freeblocks (ip=0xc0d08c00, length=0x0) at ../../ufs/ffs/ffs_softdep.c:1667 #13 0xc01ba212 in ffs_truncate (vp=0xd81b1be0, length=0x0, flags=0x0, cred=0x0, p=0xd776fa00) at ../../ufs/ffs/ffs_inode.c:195 #14 0xc01c3eaa in ufs_inactive (ap=0xd8189eb8) at ../../ufs/ufs/ufs_inode.c:84 #15 0xc01c8f4d in ufs_vnoperate (ap=0xd8189eb8) at ../../ufs/ufs/ufs_vnops.c:2283 #16 0xc016995a in vput (vp=0xd81b1be0) at vnode_if.h:794 #17 0xc016ccb5 in unlink (p=0xd776fa00, uap=0xd8189f80) at ../../kern/vfs_syscalls.c:1421 #18 0xc02101da in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x0, tf_esi = 0x80601b0, tf_ebp = 0xbfbff984, tf_isp = 0xd8189fd4, tf_ebx = 0x8060230, tf_edx = 0x0, tf_ecx = 0x0, tf_eax = 0xa, tf_trapno = 0x0, tf_err = 0x2, tf_eip = 0x280aac70, tf_cs = 0x1f, tf_eflags = 0x297, tf_esp = 0xbfbff8f8, tf_ss = 0x2f}) at ../../i386/i386/trap.c:1057 #19 0xc0203f86 in Xint0x80_syscall () #20 0x804a30a in ?? () #21 0x80501b1 in ?? () #22 0x8048fa9 in ?? () (kgdb) -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 9 23:36:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 2DDD115044 for ; Sun, 9 Jan 2000 23:36:33 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id RAA09825; Mon, 10 Jan 2000 17:36:05 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd009813; Mon Jan 10 17:36:00 2000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id RAA29556 for ; Mon, 10 Jan 2000 17:35:35 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id RAA26615 for ; Mon, 10 Jan 2000 17:35:35 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id RAA51943; Mon, 10 Jan 2000 17:35:34 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <200001100735.RAA51943@nymph.detir.qld.gov.au> To: freebsd-current@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Crash from ^T during heavy paging Date: Mon, 10 Jan 2000 17:35:34 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently giving 4.0 a thrashing in the best way I know. I run way too much stuff and let it page madly all day. Here's how I killed it: 1) pick a 32MB box 2) make -j20 buildworld 3) lean on ^T and let autorepeat go for it Soon it dies in calcru() called from ttyinfo(). The stack trace showed that I caught it part way through a fork(). In calcru(), p->p_stats has a bad value because it is initialised in vm_fork() sometime *after* the P_INMEM flag is set, and there are some M_WAITOK mallocs between them. The problem is that calcru() thinks that P_INMEM means that the proc structure is fully and accurately populated. But P_INMEM is one of the first flags set. A few places test for p->p_stats == NULL but that doesn't look applicable since p->p_stats is uninitialised in this case. Hmm. I can't see any use for that test at first glance. So, calcru() and possibly some other places, are looking at a struct proc before it's all there. What's the "proper" way to do it? Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 0:10:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id F172A15772; Mon, 10 Jan 2000 00:10:27 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id BAA63658; Mon, 10 Jan 2000 01:10:27 -0700 (MST) (envelope-from ken) Date: Mon, 10 Jan 2000 01:10:27 -0700 From: "Kenneth D. Merry" To: Brian Fundakowski Feldman Cc: current@FreeBSD.ORG, mckusick@FreeBSD.ORG Subject: Re: SoftUpdates crash with new code Message-ID: <20000110011027.A63628@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from green@FreeBSD.ORG on Mon, Jan 10, 2000 at 01:58:36AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 01:58:36 -0500, Brian Fundakowski Feldman wrote: > Well, I'm having problems with SoftUpdates. I've disabled it for now. > Here's the backtrace for the crash; more info from the crashdump is > available upon request, but I think this is a general problem, and > easily reproduced. I had a similar panic (mine got to indir_trunc() through a different code path). I already sent mail to Kirk with the stack trace, etc. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 0:12:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from exchange.prism.co.za (exchange.prism.co.za [196.34.63.66]) by hub.freebsd.org (Postfix) with ESMTP id 60EE114D1C; Mon, 10 Jan 2000 00:12:39 -0800 (PST) (envelope-from alwyns@littlecruncher.prizm.dhs.org) Received: from littlecruncher.prizm.dhs.org (196.34.63.201 [196.34.63.201]) by exchange.prism.co.za with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id CKVJLPYD; Mon, 10 Jan 2000 10:14:59 +0200 Received: by littlecruncher.prizm.dhs.org (Postfix, from userid 1001) id 55725B9; Mon, 10 Jan 2000 10:14:20 +0200 (SAST) Date: Mon, 10 Jan 2000 10:14:19 +0200 From: Alwyn Schoeman To: FreeBSD Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, "freebsd-security@FreeBSD. ORG" Subject: Re: load spike strangeness Message-ID: <20000110101419.D7053@littlecruncher.prizm.dhs.org> References: <200001090206.DAA75669@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from freebsd@gtonet.net on Sat, Jan 08, 2000 at 06:31:19PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Since when does an E-mail address require a "realname"? Only a imbecile > (IMHO) would use their real name on an e-mail that goes out to a public > list. I don't want people to know my real name or SSN or any other personal > info for that matter, NOR is it required, as far as I know. If it were to > become required, I'd prefer to "unsubscribe" than to give that info out, as > would any other intelligent person. I suggest you check your e-mail security > information again before babbling nonsense. My e-mail addy is a REAL addy > not one that goes through an anonymous re-mailer and I use it so IF I start > getting Spam I can easily rmuser it and create another to resubscribe. Do > you also use you real full name on IRC? To quote "Mr. T": "I pity da f00!" I think he was talking about the text that accompanies your e-mail address. E.g. Bill Gates and Bill Gates is the same user for human processing, but 2 completely different people when it comes to spam. Sometimes I long for the days when people on The Internet were just a few and netiquette ruled the day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 1:40:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id E53CA1524E for ; Mon, 10 Jan 2000 01:40:26 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 127bJI-000LoX-0X for freebsd-current@freebsd.org; Mon, 10 Jan 2000 09:40:25 +0000 Received: from nenya (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (Postfix) with SMTP id A9841D913 for ; Mon, 10 Jan 2000 09:42:15 +0000 (GMT) Message-ID: <000901bf5b4f$0e1ba520$0304020a@rings> From: "Cameron Grant" To: Subject: newpcm Date: Mon, 10 Jan 2000 09:42:48 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG would everyone who currently has an issue outstanding with newpcm please report it to me in the next few days directly, please, so i can get an idea of what needs work before release. i need as much detail as possible. - cameron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 3:51:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from godfather.webvolution.net (unknown.cust-X.hecenter.com [208.231.0.74]) by hub.freebsd.org (Postfix) with ESMTP id 508FB1510D for ; Mon, 10 Jan 2000 03:50:14 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: (from nobody@localhost) by godfather.webvolution.net (13.5.3/13.5.3) id LAA35188; Mon, 10 Jan 2000 11:50:01 GMT (envelope-from jpedras@webvolution.net) Date: Mon, 10 Jan 2000 11:50:01 GMT Message-Id: <200001101150.LAA35188@godfather.webvolution.net> X-Authentication-Warning: godfather.webvolution.net: nobody set sender to jpedras@webvolution.net using -f From: Joao Pedras To: djb@Wit389306.student.utwente.nl Reply-To: Joao Pedras Cc: freebsd-current@freebsd.org References: <20000110025813.A353@relativity.student.utwente.nl> <20000110032017.A499@relativity.student.utwente.nl> In-Reply-To: <20000110032017.A499@relativity.student.utwente.nl> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP3 Imap webMail Program 2.0.11 X-Originating-IP: 193.137.208.1 Subject: Re: freezing... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello again No, my problem is not ahc related. This single processor system doesn't have any scsi It's a : PPro200/64MbRAM/8.4QuantumIDE/IntelVS440FX/Pioneer12x(which is not detected after upgraded to -CURRENT)/Digital 21240 (de0)/S3 Virge What I have in common with Christian is that it hangs during high usage, as I mentioned in my first post (e.g. compiling something, buildworld). I performed a buildworld this night with yesterday's code (in a common console) and it worked ok. I ONLY noticed this when having high CPU usage (e.g. compiling mysql port) when in using X. I am not saying this is X related. Common point here seems to be a busy system Joao Quoting "Dave J. Boers" : > On Mon, Jan 10, 2000 at 04:10:37AM +0100, Christian Carstensen wrote: > > this runs stable for 3 hours now... > > try a current kernel (checked out 4 hours ago), using a version of the > > file /usr/src/sys/pci/ahc_pci.c from 2000/01/06. ok, maybe it's not by > any > > means stable, but works better than everything else within the last 24 > > hours. > > Actually, I've booted a kernel from just before newyear (28 december) which > works _reasonably_ fine (although it's the same kernel that gave me the > lockup earlier) with a userland of today. > > Problem is that the lockups (I think) are ahc-related and my SCSI hard > drive did refuse to come online on one or two occasions while booting the > system cold... I therefore concluded that it might be a problem with the > hardware. Now (with the new kernel) I find the scsi system unstable and I > have doubts again. > > One piece of information might also be useful in this context. After the > system lockup I sort of benchmarked the scsi performance by doing "dd > if=/dev/zero of=./testfile bs=1000000 count=128" (actually I varied the > blocksize) and got a _very poor_ performance of only 4 Mb/sec (which is > usually around 10 to 12 Mb/sec). I isolated my drive to be the only scsi > device and I even clocked the SCSI bus down from 20 Mhz to 8 Mhz, but to no > avail. > > In the mean time, I disconnected my scsi hard drive and I am running from > my IDE disk. ------------------------------- Powered by Webvolution Networks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 4:45:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id CE80014D3D for ; Mon, 10 Jan 2000 04:45:15 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id GAA92594; Mon, 10 Jan 2000 06:45:14 -0600 (CST) From: Joe Greco Message-Id: <200001101245.GAA92594@aurora.sol.net> Subject: Re: load spike strangeness To: current@freebsd.org Date: Mon, 10 Jan 2000 06:45:14 -0600 (CST) Cc: blk@skynet.be X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 4:48 AM -0800 2000/1/9, Amancio Hasty wrote: > > For instance, just because someone has an email name which resembles > > a real name lets say "Brad Knowles" does not necessarily mean that the > > real "Brad Knowles is sending the mail assuming of course that there > > is a Brad Knowles. > > I've built up enough history over the years (all the while using > my real name and a real e-mail address, although the address has > changed over the years as I've changed employers, etc...) that you > can go do some AltaVista or Hotbot searches and find enough stuff > that I've written that we can be reasonably sure that this really is > me. I may not be proud of some of the stupid things I've done or > said over the years, but I'll own up to them regardless. > > I'd say that the same is probably true of most of the people > posting to the various lists. We have a new existential proof, "I'm archived, therefore I am"! :-) Seriously, Brad, I'm not convinced that you're anything more than a complex PERL program until I meet you in person. Particularly since you seem to have more time and energy to spend posting to Usenet and mailing lists than anyone else I know. ;-) ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 5:33:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (p3E9EBF51.dip0.t-ipconnect.de [62.158.191.81]) by hub.freebsd.org (Postfix) with ESMTP id 1210A151E6 for ; Mon, 10 Jan 2000 05:33:01 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id PAA00630; Mon, 10 Jan 2000 15:35:47 +0100 (CET) (envelope-from cc@devcon.net) Date: Mon, 10 Jan 2000 15:35:47 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: Joao Pedras Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: freezing... In-Reply-To: <200001101150.LAA35188@godfather.webvolution.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Joao Pedras wrote: > What I have in common with Christian is that it hangs > during high usage, as I mentioned in my first post (e.g. > compiling something, buildworld). this is funny: the system operates well, even when on heavy load (especially disk load), until i want a little more 8). to become more precisely, a cvs checkout or make world is no problem, if - and that's really interesting - nothing else requests the system's attention. i've had some successfully reproducable crashes when generating much i/o usage (cvs, buildworld), which in fact caused no problem, and then simply starting pine. at the moment, pine opened the mail folder, all my noisy hard disks stopped and it was perfectly quiet apart from cpu fans. -- Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 5:42:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id D7EB315270 for ; Mon, 10 Jan 2000 05:38:15 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 364A61DA7; Mon, 10 Jan 2000 14:38:11 +0100 (CET) Date: Mon, 10 Jan 2000 14:38:11 +0100 From: "Dave J. Boers" To: Christian Carstensen Cc: Joao Pedras , freebsd-current@FreeBSD.ORG Subject: Re: freezing... Message-ID: <20000110143811.B796@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <200001101150.LAA35188@godfather.webvolution.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cc@devcon.net on Mon, Jan 10, 2000 at 03:35:47PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 03:35:47PM +0100, Christian Carstensen wrote: > this is funny: > the system operates well, even when on heavy load (especially disk load), > until i want a little more 8). to become more precisely, a cvs checkout or > make world is no problem, if - and that's really interesting - nothing > else requests the system's attention. i've had some successfully reproducable > crashes when generating much i/o usage (cvs, buildworld), which in fact > caused no problem, and then simply starting pine. at the moment, pine > opened the mail folder, all my noisy hard disks stopped and it was > perfectly quiet apart from cpu fans. That sounds exactly like the very dead state I found my system in when it hang (I only have one occurence, so far, but my system isn't under very heavy load lately). Make -j 9 buildworld completes fine. The hang seems to have occured during a simple 20 Mb transfer of email data from my ide to my scsi disk (which is a very short but i/o intensive operation). There might have been an incoming email at the same time. I will try an idiotic buildworld -j 30 this evening just to see wether I can hang the system reproducibly. Have to go now, however. Regards, Dave Boers. -- Fatal error: replace user and try again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 6: 4: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.01019freenet.de (mout0.01019freenet.de [62.104.201.5]) by hub.freebsd.org (Postfix) with ESMTP id A069A14BDA for ; Mon, 10 Jan 2000 06:04:01 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.2] (helo=mx1.01019freenet.de) by mout0.01019freenet.de with esmtp (Exim 3.12 #2) id 127fQM-0000Mo-00; Mon, 10 Jan 2000 15:03:58 +0100 Received: from [213.6.45.198] (helo=Magelan.Leidinger.net) by mx1.01019freenet.de with esmtp (Exim 3.12 #2) id 127fQM-0000t8-00; Mon, 10 Jan 2000 15:03:58 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id OAA02110; Mon, 10 Jan 2000 14:05:55 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200001101305.OAA02110@Magelan.Leidinger.net> Date: Mon, 10 Jan 2000 14:05:54 +0100 (CET) From: Alexander Leidinger Subject: Re: __sigisempty() undefined if "cc -g" used. To: bde@zeta.org.au Cc: John Polstra , current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by Magelan.Leidinger.net id OAA02110 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 Jan, Bruce Evans wrote: >> Better yet: DEBUG_FLAGS=3D-g >=20 > Except it only supported in bsd.prog.mk and bsd.lib.mk, but not in > bsd.kmod.mk, kernel Makefiles, or if no bsd .mk files are included > A few verbose module makefiles add it explicitly. You can also use > COPTS, but it is only supported in bsd.prog.mk, bsd.kmod.mk and kernel > Makefiles. Didn=B4t we have "makeoptions DEBUG=3D-g" as a kernel option to compile t= he kernel with debug information? What about "config -g MYKERNEL"? Do we really need a global debug option which covers everything? If I read it correcly we have DEBUG_FLAGS for the userland (if it uses a bsd.{prog,lib}.mk) and DEBUG for the kernel (and COPTS for KLD's), right? So we only have to make the KLD's consistent to the kernel (or am I missing something): bsd.kmod.mk: ---snip--- 92c92 < CFLAGS+=3D ${COPTS} -D_KERNEL ${CWARNFLAGS} --- > CFLAGS+=3D ${DEBUG} -D_KERNEL ${CWARNFLAGS} ---snip--- Bye, Alexander. --=20 Happy new year and no Y2K-crash to everyone. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint =3D 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 6: 4:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 898EF15162 for ; Mon, 10 Jan 2000 06:04:20 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id PAA55928; Mon, 10 Jan 2000 15:03:47 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Christian Carstensen Cc: Joao Pedras , djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: freezing... In-reply-to: Your message of "Mon, 10 Jan 2000 15:35:47 +0100." Date: Mon, 10 Jan 2000 15:03:47 +0100 Message-ID: <55926.947513027@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Christian Carstensen writes: >On Mon, 10 Jan 2000, Joao Pedras wrote: > >> What I have in common with Christian is that it hangs >> during high usage, as I mentioned in my first post (e.g. >> compiling something, buildworld). > >this is funny: >the system operates well, even when on heavy load (especially disk load), >until i want a little more 8). I have a make world hanging here: 0 19914 19902 169 -2 0 1276 932 getblk D+ p1 0:00.09 yacc -d -o c-parse.c c-parse.y -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 6:37:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from gandalf.hk.linkage.net (gandalf.hk.linkage.net [202.76.4.1]) by hub.freebsd.org (Postfix) with ESMTP id 459DC14BD8 for ; Mon, 10 Jan 2000 06:37:06 -0800 (PST) (envelope-from satyajit@spnetctg.com) Received: from mail.spnetctg.com (qmailr@mail.spnetctg.com [210.184.28.8]) by gandalf.hk.linkage.net (8.9.1/8.8.8) with SMTP id WAA05560 for ; Mon, 10 Jan 2000 22:37:01 +0800 (HKT) Received: (qmail 1640 invoked from network); 10 Jan 2000 15:03:11 -0000 Received: from unknown (HELO spnetctg.com) (210.184.28.217) by mail.spnetctg.com with SMTP; 10 Jan 2000 15:03:11 -0000 Message-ID: <3879EFB3.53CAE35C@spnetctg.com> Date: Mon, 10 Jan 2000 14:41:56 +0000 From: Satyajit Das X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.13-7mdk i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: mouse problem(please help) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I install FreeBSD3.3 but i face a problem to config mouse in Xwindows. I'm not able to subscribe in freebsd-question so i send it here please solve this problem. I have a GENIUS mouse , port : com 2 (/dev/cuaa1). when i install FreeBSD that time i test my mouse and it's work that time but when i start "startx" mouse not working . Again i run XF86Setup program ,I also choose "mouse system , sysmouse" and port /dev/cuaa1 or /dev/sysmouse but no work. please help me how can i work mouse in Xwindows. please give me suggestion. satyajit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 7: 1:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id AD25A15162 for ; Mon, 10 Jan 2000 07:01:10 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 33A0F1F3C; Mon, 10 Jan 2000 16:01:09 +0100 (CET) Date: Mon, 10 Jan 2000 16:01:09 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: Buildworld fails Message-ID: <20000110160109.A10972@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With CURRENT-sources updates within an hour ago ... buildworld fails: cd /usr/src/gnu/lib/libdialog; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/gnu/lib/libdial og/dialog.h /usr/obj/usr/src/i386/usr/include sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 /usr/src/gnu/lib/libdia log/TESTS/Makefile /usr/obj/usr/src/i386/usr/share/examples/libdialog install: mkstemp: /usr/obj/usr/src/i386/usr/share/examples/INS@0244 for /usr/obj /usr/src/i386/usr/share/examples/libdialog: No such file or directory *** Error code 71 Stop in /usr/src/gnu/lib/libdialog. *** Error code 1 -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 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+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 7: 9:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id E611114D3D; Mon, 10 Jan 2000 07:09:30 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-7.iptelecom.net.ua [212.9.227.7]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id RAA12603; Mon, 10 Jan 2000 17:13:13 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id RAA27957; Mon, 10 Jan 2000 17:08:46 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <3879F5FB.EE08DEBF@altavista.net> Date: Mon, 10 Jan 2000 17:08:43 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org, brian@freebsd.org Subject: pppctl/ppp bug Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've noticed that pppctl hangs 100% repeatable when I'm doing "set log local +chat" followed by the "dial" command over diagnostic socket. In the case when the "dial" command being sent over other socket this behaviour doesn't observed. Following I'm attaching transcript of my sessions -Maxim Bad: Script started on Mon Jan 10 16:55:21 2000 bash-2.03$ pppctl 3000 ppp ON vega> set log local +chat +phase ppp ON vega> dia [doesn't respond to any keystroke other than ^C] ^C bash-2.03$ exit Script done on Mon Jan 10 16:55:53 2000 Good: Script started on Mon Jan 10 17:01:15 2000 bash-2.03$ pppctl 3000 ppp ON vega> set log local +phase +chat ppp ON vega> Phase: Connected to client from 127.0.0.1:53000 Phase: bundle: Establish Phase: deflink: closed -> opening Phase: deflink: Connected! Phase: deflink: opening -> dial Phase: Phone: 9-2388888 Chat: deflink: Dial attempt 1 of 20 Chat: Send: ATZ Chat: Expect(4): OK Chat: Received: ATDT9238-8888 ATZ Chat: Received: OK Chat: Send: ATDT9238-8888 Chat: Expect(45): CONNECT Chat: Received: ATDT9238-8888 Chat: Received: BUSY Warning: Chat script failed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 7:25:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A2EDA151D2 for ; Mon, 10 Jan 2000 07:25:07 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id QAA57328 for ; Mon, 10 Jan 2000 16:24:57 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: current hangs in make world (softupdates on ccd on ata) From: Poul-Henning Kamp Date: Mon, 10 Jan 2000 16:24:57 +0100 Message-ID: <57326.947517897@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make world hangs reliably for me right now: +-------- |... |/* starting time is 16:18:8 */ |/* ending time is 16:18:8 */ |ln -sf gxx-hash.h hash.h |echo '#include "cp/cp-tree.def"' > gencheck.h |echo '#include "objc/objc-tree.def"' >> gencheck.h |sed -e "/^ifobjc$/,/^end ifobjc$/d" -e "/^ifc$/d" -e "/^end ifc$/d" /syv/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.in > c-parse.y |yacc -d -o c-parse.c c-parse.y +-------- 0 19921 1 83 -2 0 1276 932 getblk D p0 0:00.09 yacc -d -o c-parse.c c-parse.y This is a softupdates filesystem on a ccd on ata... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 7:55:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 29C1514FA6 for ; Mon, 10 Jan 2000 07:55:48 -0800 (PST) (envelope-from michaelc@tmbbwmc.bbn.hp.com) Received: from tmbbmcc3.bbn.hp.com (tmbbmcc3.bbn.hp.com [15.136.126.78]) by palrel3.hp.com (Postfix) with ESMTP id 689C41496 for ; Mon, 10 Jan 2000 07:55:46 -0800 (PST) Received: from tmbbwmc.bbn.hp.com (michaelc@tmbbwmc.bbn.hp.com [15.136.124.25]) by tmbbmcc3.bbn.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id QAA27360 for ; Mon, 10 Jan 2000 16:52:11 +0100 (MET) Received: from localhost (michaelc@localhost) by tmbbwmc.bbn.hp.com (8.8.6/8.8.6) with ESMTP id QAA08617 for ; Mon, 10 Jan 2000 16:55:44 +0100 (MET) Date: Mon, 10 Jan 2000 16:55:43 +0100 (MET) From: #Michael Class To: freebsd-current@freebsd.org Subject: Neomagic Sounddriver hangs HP OB4150 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, as someone already has mentioned for another Laptop, the new Neomagic Audio-Driver (btw. thank you for creating one) hangs my HP Omnibook 4150 during boot. The Laptop is equipped with the following Neomagic-Chip: chip1: irq 10 at device 0.1 on pci1 The Stack-Backtrace looks exactly the same as the other mail mentioned. A little bit further digging into this shows me that on this Laptop every read access to the second memory-area of the chip in the range of 0x600-0x8ff brings the machine to a halt. I can read successfully from the areas with offset 0x0-0x5ff and 0x900-0xFFF. The Header-File states that the mixer-I/O Area starts at offset 0x600. This access brings the machine to a halt during boot. Any suggestions of what I could try? Michael ___________________________________________________________________________ Michael Class E-Mail: michael_class@hp.com E-Business Solution Division Phone: +49 7031 14-3707 Fax: +49 7031 14-4505 ___________________________________________________________________________ Hewlett-Packard GmbH, PO Box 1430, Mailstop ESD2, 71004 Boeblingen Sitz der Gesellschaft: Böblingen, Amtsgericht Böblingen HRB 4081 Geschäftsführer: Jörg Menno Harms (Vorsitzender),Rainer Erlat, Hans-Joachim Lueckefett,Heribert Schmitz,Fritz Schuller ___________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 8:19:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E4DDD15133 for ; Mon, 10 Jan 2000 08:19:41 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id DAA25162; Tue, 11 Jan 2000 03:19:00 +1100 Date: Tue, 11 Jan 2000 03:18:57 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Alexander Leidinger Cc: John Polstra , current@FreeBSD.ORG Subject: Re: __sigisempty() undefined if "cc -g" used. In-Reply-To: <200001101305.OAA02110@Magelan.Leidinger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Alexander Leidinger wrote: > On 10 Jan, Bruce Evans wrote: >=20 > >> Better yet: DEBUG_FLAGS=3D-g > >=20 > > Except it only supported in bsd.prog.mk and bsd.lib.mk, but not in > > bsd.kmod.mk, kernel Makefiles, or if no bsd .mk files are included > > A few verbose module makefiles add it explicitly. You can also use > > COPTS, but it is only supported in bsd.prog.mk, bsd.kmod.mk and kernel > > Makefiles. >=20 > Didn=B4t we have "makeoptions DEBUG=3D-g" as a kernel option to compile t= he > kernel with debug information? What about "config -g MYKERNEL"? DEBUG is a private variable in kernel Makefiles. "config -g MYKERNEL" is the only correct way to set it. "makeoptions DEBUG=3D-g" is a hackish way to set it. It depends on knowing the the Makefiles' internals. > Do we really need a global debug option which covers everything? It's simpler to have the same global debug option for everything. > If I read it correcly we have DEBUG_FLAGS for the userland (if it uses a > bsd.{prog,lib}.mk) and DEBUG for the kernel (and COPTS for KLD's), > right? No. DEBUG is quite different. > So we only have to make the KLD's consistent to the kernel (or am > I missing something): > > bsd.kmod.mk: > ---snip--- > 92c92 > < CFLAGS+=3D ${COPTS} -D_KERNEL ${CWARNFLAGS} > --- > > CFLAGS+=3D ${DEBUG} -D_KERNEL ${CWARNFLAGS} > ---snip--- This would break COPTS :-). All places should use something more like: CFLAGS+=3D=09[-D_KERNEL] ${CWARNFLAGS} ${COPTS} ${DEBUG_FLAGS} Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 8:43:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 995B114CE8 for ; Mon, 10 Jan 2000 08:43:05 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id LAA08720; Mon, 10 Jan 2000 11:42:29 -0500 (EST) Date: Mon, 10 Jan 2000 11:42:29 -0500 (EST) From: "Mr. K." To: Leif Neland Cc: FreeBSD , "freebsd-current@FreeBSD. ORG" Subject: Re: Anonymity, was: load spike strangeness In-Reply-To: <009b01bf5acc$d943f140$0e00a8c0@neland.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 9 Jan 2000, Leif Neland wrote: > While I do not agree with your idea of need of anonymity, I respect your need for it. > > Could you not, instead of using the handle "FreeBSD", which sortof already is taken :-), just assume a human name? The use of an obviously not human name makes it uncomfortable to communicate with you. > > If you would call you John Smith, or Thomas Jefferson if you want, you could much more easily hide your (hideous?) precence in the lists. Please? > Yeah, like Mr. K. :) > Leif K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 9: 6:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.01019freenet.de (mout1.01019freenet.de [62.104.201.3]) by hub.freebsd.org (Postfix) with ESMTP id 0CE2314FE9 for ; Mon, 10 Jan 2000 09:06:44 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.2] (helo=mx1.01019freenet.de) by mout1.01019freenet.de with esmtp (Exim 3.12 #2) id 127iHB-0008PK-00; Mon, 10 Jan 2000 18:06:41 +0100 Received: from [213.6.53.222] (helo=Magelan.Leidinger.net) by mx1.01019freenet.de with esmtp (Exim 3.12 #2) id 127iHA-0006V6-00; Mon, 10 Jan 2000 18:06:40 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id SAA04920; Mon, 10 Jan 2000 18:00:53 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200001101700.SAA04920@Magelan.Leidinger.net> Date: Mon, 10 Jan 2000 18:00:52 +0100 (CET) From: Alexander Leidinger Subject: Re: __sigisempty() undefined if "cc -g" used. To: bde@zeta.org.au Cc: jdp@polstra.com, current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by Magelan.Leidinger.net id SAA04920 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11 Jan, Bruce Evans wrote: >> Didn=B4t we have "makeoptions DEBUG=3D-g" as a kernel option to compil= e the >> kernel with debug information? What about "config -g MYKERNEL"? >=20 > DEBUG is a private variable in kernel Makefiles. "config -g MYKERNEL" If I set DEBUG in make.conf it should work, right? So what's private about it? > is the only correct way to set it. "makeoptions DEBUG=3D-g" is a hacki= sh > way to set it. It depends on knowing the the Makefiles' internals. > >> Do we really need a global debug option which covers everything? >=20 > It's simpler to have the same global debug option for everything. We have CFLAGS (userland) and COPTFLAGS (kernel) in make.conf, shouldn=B4= t we also have e.g. DEBUG_FLAGS and DEBUG_KERNEL (renamed DEBUG from above)? Together with CFLAGS and COPTFLAGS it would make more sense, IMO. And what about those people who want to compile only the kernel and the KLD's with debug information, but not the userland? >> If I read it correcly we have DEBUG_FLAGS for the userland (if it uses= a >> bsd.{prog,lib}.mk) and DEBUG for the kernel (and COPTS for KLD's), >> right? >=20 > No. DEBUG is quite different. Sorry, but I didn=B4t get the point. Is it a semantic difference or a technical one? >> So we only have to make the KLD's consistent to the kernel (or am >> I missing something): >> >> bsd.kmod.mk: >> ---snip--- >> 92c92 >> < CFLAGS+=3D ${COPTS} -D_KERNEL ${CWARNFLAGS} >> --- >> > CFLAGS+=3D ${DEBUG} -D_KERNEL ${CWARNFLAGS} >> ---snip--- >=20 > This would break COPTS :-). All places should use something more like: > > CFLAGS+=3D [-D_KERNEL] ${CWARNFLAGS} ${COPTS} ${DEBUG_FLAGS} What about renaming "DEBUG" in the kernel makefile to DEBUG_KERNEL and use DEBUG_KERNEL instead of DEBUG_FLAGS in bsd.kmod.mk? Bye, Alexander. --=20 Happy new year and no Y2K-crash to everyone. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint =3D 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 10: 1:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B58D0152E7 for ; Mon, 10 Jan 2000 10:01:23 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id FAA28184; Tue, 11 Jan 2000 05:00:52 +1100 Date: Tue, 11 Jan 2000 05:00:48 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Alexander Leidinger Cc: jdp@polstra.com, current@FreeBSD.ORG Subject: Re: __sigisempty() undefined if "cc -g" used. In-Reply-To: <200001101700.SAA04920@Magelan.Leidinger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Alexander Leidinger wrote: > On 11 Jan, Bruce Evans wrote: >=20 > >> Didn=B4t we have "makeoptions DEBUG=3D-g" as a kernel option to compil= e the > >> kernel with debug information? What about "config -g MYKERNEL"? > >=20 > > DEBUG is a private variable in kernel Makefiles. "config -g MYKERNEL" >=20 > If I set DEBUG in make.conf it should work, right? It shouldn't work, but may. > So what's private > about it? It's set unconditionally in some cases. > We have CFLAGS (userland) and COPTFLAGS (kernel) in make.conf, shouldn=B4= t > we also have e.g. DEBUG_FLAGS and DEBUG_KERNEL (renamed DEBUG from > above)? No. Who knows what all those undocumented variables do. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 10: 5:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id C2E87152F8 for ; Mon, 10 Jan 2000 10:05:28 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id SAA24574 for current@FreeBSD.org; Mon, 10 Jan 2000 18:51:44 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Mon, 10 Jan 2000 18:51:39 +0100 From: Marcel Moolenaar Message-ID: <387A1C2B.75AFE94A@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <57326.947517897@critter.freebsd.dk> Subject: Re: current hangs in make world (softupdates on ccd on ata) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > Make world hangs reliably for me right now: [snip] > |yacc -d -o c-parse.c c-parse.y > +-------- > > 0 19921 1 83 -2 0 1276 932 getblk D p0 0:00.09 yacc -d -o c-parse.c c-parse.y > > This is a softupdates filesystem on a ccd on ata... The format used for mkstemp has been changed (4 chars. longer). Does the following patch work? Index: main.c =================================================================== RCS file: /home/ncvs/src/usr.bin/yacc/main.c,v retrieving revision 1.11 diff -u -r1.11 main.c --- main.c 2000/01/10 08:54:09 1.11 +++ main.c 2000/01/10 17:47:33 @@ -304,7 +304,7 @@ if (tmpdir == 0) tmpdir = "/tmp"; len = strlen(tmpdir); - i = len + 13; + i = len + 17; if (len && tmpdir[len-1] != '/') ++i; -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 10: 7:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 6B9AC1530E for ; Mon, 10 Jan 2000 10:07:15 -0800 (PST) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.5.62]) by matrix.eurocontrol.fr (Postfix) with ESMTP id 1B233593B for ; Mon, 10 Jan 2000 19:07:12 +0100 (CET) (envelope-from roberto@caerdonn.eurocontrol.fr) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id 0545F4E48; Mon, 10 Jan 2000 19:07:08 +0100 (CET) Date: Mon, 10 Jan 2000 19:07:08 +0100 From: Ollivier Robert To: FreeBSD Current Users' list Subject: Re: Buildworld fails Message-ID: <20000110190708.A34876@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Pascal Hofstee wrote: > With CURRENT-sources updates within an hour ago ... buildworld fails: Revert to version 1.26 of gnu/lib/libdialog/Makefile. someone broke it when he decided to install all the files in TESTS/... Don't forget to revert to 1.34 of lib/libncurses/Makefile for the same reason. Grrr. -- Ollivier ROBERT -=- Eurocontrol EEC/TEC -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 10:56:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id 22F8A14E82 for ; Mon, 10 Jan 2000 10:56:42 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 5754 invoked by uid 1010); 10 Jan 2000 16:55:43 -0000 Date: Mon, 10 Jan 2000 16:55:43 +0000 From: George Cox To: freebsd-current@freebsd.org Subject: -pipe switch in kernel compilation Message-ID: <20000110165543.A5720@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG G'day, While compiling a kernel today, I noticed that the '-pipe' option to gcc was not being used. Is there any reason for this? best; gjvc -- [gjvc] 4.4BSD 4.ever! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 10:57:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id CCF011534D for ; Mon, 10 Jan 2000 10:57:40 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id LAA19222 for current@freebsd.org; Mon, 10 Jan 2000 11:20:54 -0800 (PST) Date: Mon, 10 Jan 2000 11:20:54 -0800 From: Alfred Perlstein To: current@freebsd.org Subject: fix for hangs with recent -current + vinum Message-ID: <20000110112054.C9397@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you're getting hangs while running vinum please update sys/dev/vinum/vinumrequest.c to version 1.41. Only people running -current compilied with version 1.40 or 1.38-1.36 of vinumrequest.c should need this fix. thanks, -- -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 11:39:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5899514C86; Mon, 10 Jan 2000 11:39:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA29268; Mon, 10 Jan 2000 11:39:13 -0800 (PST) (envelope-from dillon) Date: Mon, 10 Jan 2000 11:39:13 -0800 (PST) From: Matthew Dillon Message-Id: <200001101939.LAA29268@apollo.backplane.com> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: current hangs in make world (softupdates on ccd on ata) References: <57326.947517897@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Make world hangs reliably for me right now: :+-------- :|... :|/* starting time is 16:18:8 */ :|/* ending time is 16:18:8 */ :|ln -sf gxx-hash.h hash.h :|echo '#include "cp/cp-tree.def"' > gencheck.h :|echo '#include "objc/objc-tree.def"' >> gencheck.h :|sed -e "/^ifobjc$/,/^end ifobjc$/d" -e "/^ifc$/d" -e "/^end ifc$/d" /syv/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.in > c-parse.y :|yacc -d -o c-parse.c c-parse.y :+-------- : : 0 19921 1 83 -2 0 1276 932 getblk D p0 0:00.09 yacc -d -o c-parse.c c-parse.y : :This is a softupdates filesystem on a ccd on ata... : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." :FreeBSD -- It will take a long time before progress goes too far! No vinum? Please ps axl and pick out any other processes stuck in odd places. Then gdb -k kernel.debug /dev/mem (assuming you have kernel.debug sitting around somewhere). proc 19921 back proc ...other processes... back ... note: if you have a custom .gdbinit that sets the base to hex you may have to type the process number in hex. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 11:45:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9D1ED1534F for ; Mon, 10 Jan 2000 11:45:46 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA29394; Mon, 10 Jan 2000 11:45:46 -0800 (PST) (envelope-from dillon) Date: Mon, 10 Jan 2000 11:45:46 -0800 (PST) From: Matthew Dillon Message-Id: <200001101945.LAA29394@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: Re: freezing... References: <55926.947513027@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've reproduced the softupdates ftruncate panic and have a core dump to play with. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 11:46:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 347171501F for ; Mon, 10 Jan 2000 11:46:35 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA32105; Mon, 10 Jan 2000 12:46:29 -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.9.3/8.8.3) with ESMTP id MAA11790; Mon, 10 Jan 2000 12:46:36 -0700 (MST) Message-Id: <200001101946.MAA11790@harmony.village.org> To: Jonathan Chen Subject: Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th) Cc: Greg Lehey , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 10 Jan 2000 01:02:40 EST." References: <20000109163314.A515@mojave.worldwide.lemis.com> <200001071246.XAA05593@avalon.reed.wattle.id.au> <200001072052.MAA01482@mass.cdrom.com> <200001062246.PAA80310@harmony.village.org> <200001071246.XAA05593@avalon.reed.wattle.id.au> <20000109163314.A515@mojave.worldwide.lemis.com> <200001100426.VAA03237@harmony.village.org> Date: Mon, 10 Jan 2000 12:46:36 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jonathan Chen writes: : "Fake IRQ must be 3". Now maybe the card requires it, or maybe the : original author just didn't have anything on IRQ 3, I don't know. So, I'd : suggest turning off com2 or whatever you have on irq3, -or- change the : "fake irq" to something else you do have free on the next line (ie, : 0x3000-> 0xa000 if you have IRQ10 free). If this works, great... if not, I : hope Warner gets some more free time. ;) I don't think this is the problem. The pccard interface has one interrupt pin that is mapped by the pcic bridge (or some other pccard/cardbus bridge) to the main bus of the system. I didn't change that from the 3.x driver... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 12:24:15 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 9B369150CD; Mon, 10 Jan 2000 12:24:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 8905D1CD819; Mon, 10 Jan 2000 12:24:13 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 10 Jan 2000 12:24:13 -0800 (PST) From: Kris Kennaway To: Marcel Moolenaar Cc: current@FreeBSD.org Subject: Re: current hangs in make world (softupdates on ccd on ata) In-Reply-To: <387A1C2B.75AFE94A@scc.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Marcel Moolenaar wrote: > The format used for mkstemp has been changed (4 chars. longer). Does the > following patch work? Sorry, but FWIW I did test the change by recompiling cvs (which uses yacc) before I committed it :( I guess it was just the gods of stack which allowed that one to build. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 12:26:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id C723B15403 for ; Mon, 10 Jan 2000 12:26:44 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id PAA30087; Mon, 10 Jan 2000 15:26:08 -0500 (EST) Date: Mon, 10 Jan 2000 15:26:08 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: Jonathan Chen , Greg Lehey , current@FreeBSD.ORG Subject: Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th) In-Reply-To: <200001101946.MAA11790@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Warner Losh wrote: > I don't think this is the problem. The pccard interface has one > interrupt pin that is mapped by the pcic bridge (or some other > pccard/cardbus bridge) to the main bus of the system. I didn't change > that from the 3.x driver... Indeed. The watchdog timout problem with if_ep happens on all cards, all busses. I seem to have most of the important bits working on my dev cluster and should be able to test some fixes tonite. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 12:27: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 70D5F15460 for ; Mon, 10 Jan 2000 12:26:51 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from yoda.sftw.com (a-177.sftw.com [209.157.37.177]) by guardian.sftw.com (8.9.3/8.9.3) with ESMTP id MAA77056; Mon, 10 Jan 2000 12:26:50 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.9.3/8.9.3) with ESMTP id MAA06414; Mon, 10 Jan 2000 12:26:47 -0800 (PST) (envelope-from nsayer@sftw.com) Message-ID: <387A4083.369827BE@sftw.com> Date: Mon, 10 Jan 2000 20:26:44 +0000 From: Nick Sayer Reply-To: nsayer@FreeBSD.ORG X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: frank@exit.com Cc: Cameron Grant , current@FreeBSD.ORG Subject: Re: neomagic 256av/256zx audio References: <200001100530.VAA78037@realtime.exit.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For what it's worth, I believe the Insperion 3500 is an oddity. When I was dealing with OSS, the correct configuration turned out to be a "Generic 256AV" located at 0x530, I5, DMA 0&1 -- that is, you treat it just like an ordinary Windows Sound System chip (CS4231). The PCI interface, I believe, has something to do with the funky control panel gizmo you get in Windows that sets tone and chorus effects or some such. I haven't looked at the driver in question, but I believe it probably expects to use an exclusively PCI interface to the chip. Somehow, I believe the Insperion doesn't do this. Frank Mayhar wrote: > Cameron Grant wrote: > > i have just committed a driver for the neomagic chips. please test and post > > results. > > Okay. I have a Dell Inspiron 3500, with a NeoMagic 256AV chipset in it. > It hangs on boot, in nm_rd() line 146. Here's the backtrace: > > (kgdb) bt > #0 nm_rd (sc=0xc0d83100, regno=1536, size=2) > at ../../dev/sound/pci/neomagic.c:146 > #1 0xc0206ac7 in nm_rdcd (devinfo=0xc0d83100, regno=0) > at ../../dev/sound/pci/neomagic.c:232 > #2 0xc020219e in ac97_init (codec=0xc0d83000) > at ../../dev/sound/pcm/ac97.c:251 > #3 0xc0202376 in ac97mix_init (m=0xc073d30c) at ../../dev/sound/pcm/ac97.c:304 > #4 0xc02050b4 in mixer_init (d=0xc073d200, m=0xc0288120, devinfo=0xc0d83000) > at ../../dev/sound/pcm/mixer.c:53 > #5 0xc020736b in nm_pci_attach (dev=0xc0d87280) > at ../../dev/sound/pci/neomagic.c:594 > #6 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87280) at device_if.c:63 > #7 0xc0148bdb in device_probe_and_attach (dev=0xc0d87280) > at ../../kern/subr_bus.c:1137 > #8 0xc01498ca in bus_generic_attach (dev=0xc0d87480) > at ../../kern/subr_bus.c:1831 > #9 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87480) at device_if.c:63 > #10 0xc0148bdb in device_probe_and_attach (dev=0xc0d87480) > at ../../kern/subr_bus.c:1137 > #11 0xc01498ca in bus_generic_attach (dev=0xc0d87b80) > at ../../kern/subr_bus.c:1831 > #12 0xc01cced5 in pcib_attach (dev=0xc0d87b80) at ../../pci/pcisupport.c:747 > #13 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87b80) at device_if.c:63 > #14 0xc0148bdb in device_probe_and_attach (dev=0xc0d87b80) > at ../../kern/subr_bus.c:1137 > #15 0xc01498ca in bus_generic_attach (dev=0xc0d87d80) > at ../../kern/subr_bus.c:1831 > #16 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87d80) at device_if.c:63 > #17 0xc0148bdb in device_probe_and_attach (dev=0xc0d87d80) > at ../../kern/subr_bus.c:1137 > #18 0xc01498ca in bus_generic_attach (dev=0xc0d86000) > at ../../kern/subr_bus.c:1831 > #19 0xc011e27e in DEVICE_ATTACH (dev=0xc0d86000) at device_if.c:63 > #20 0xc0148bdb in device_probe_and_attach (dev=0xc0d86000) > at ../../kern/subr_bus.c:1137 > #21 0xc01498ca in bus_generic_attach (dev=0xc0d86080) > at ../../kern/subr_bus.c:1831 > #22 0xc0230c89 in nexus_attach (dev=0xc0d86080) at ../../i386/i386/nexus.c:199 > #23 0xc011e27e in DEVICE_ATTACH (dev=0xc0d86080) at device_if.c:63 > #24 0xc0148bdb in device_probe_and_attach (dev=0xc0d86080) > at ../../kern/subr_bus.c:1137 > #25 0xc0149e0a in root_bus_configure () at ../../kern/subr_bus.c:2214 > #26 0xc0227568 in configure (dummy=0x0) at ../../i386/i386/autoconf.c:146 > #27 0xc013319c in mi_startup (framep=0xc0325fb4) at ../../kern/init_main.c:217 > > Here are the values; looks like sh has problems: > > (kgdb) print /x sh > $2 = 0xc87d3000 > (kgdb) print *sh > $3 = 17 > (kgdb) print st > $4 = 1 > (kgdb) print /x regno > $6 = 0x600 > (kgdb) print *sc > $8 = {dev = 0x11, type = 0, reg = 0x0, irq = 0x0, buf = 0x0, regid = 0, > irqid = 32896, bufid = 0, ih = 0x0, ac97_base = 0, ac97_status = 0, > ac97_busy = 0, buftop = 0, pbuf = 0, rbuf = 0, cbuf = 0, acbuf = 0, > playint = 0, recint = 0, misc1int = 0, misc2int = 0, irsz = 0, badintr = 0, > pch = {spd = 0, dir = 0, fmt = 0, buffer = 0x0, channel = 0x0, > parent = 0x0}, rch = {spd = 0, dir = 0, fmt = 0, buffer = 0x0, > channel = 0x0, parent = 0x0}} > > Hmm, looks like sc->reg was never filled in. > > Hope this helps. > -- > Frank Mayhar frank@exit.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 13: 1:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 6C14415323 for ; Mon, 10 Jan 2000 13:01:51 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 7BBD71C2B; Mon, 10 Jan 2000 15:07:35 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 787EF3843; Mon, 10 Jan 2000 15:07:35 -0500 (EST) Date: Mon, 10 Jan 2000 15:07:35 -0500 (EST) From: Bill Fumerola To: #Michael Class Cc: freebsd-current@freebsd.org Subject: Re: Neomagic Sounddriver hangs HP OB4150 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, #Michael Class wrote: > The Laptop is equipped with the following Neomagic-Chip: > chip1: irq 10 at device 0.1 on pci1 > > The Stack-Backtrace looks exactly the same as the other mail mentioned. A > little bit further digging into this shows me that on this Laptop every > read access to the second memory-area of the chip in the range of 0x600-0x8ff > brings the machine to a halt. I can read successfully from the areas with > offset 0x0-0x5ff and 0x900-0xFFF. The Header-File states that the mixer-I/O > Area starts at offset 0x600. This access brings the machine to a halt during > boot. > > Any suggestions of what I could try? Try providing us with real data. The boot message you gave us is when pcisupport.c matches it, not when neomagic. matches it. It is impossible to recieve the above message and then have the neomagic code fall on its face. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 13:22:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 7216415AB3 for ; Mon, 10 Jan 2000 13:22:07 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id C8D5A1C5F; Sun, 9 Jan 2000 15:27:53 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id C56C03819; Sun, 9 Jan 2000 15:27:53 -0500 (EST) Date: Sun, 9 Jan 2000 15:27:53 -0500 (EST) From: Bill Fumerola To: FreeBSD Cc: Poul-Henning Kamp , "freebsd-current@FreeBSD. ORG" Subject: RE: load spike strangeness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 Jan 2000, FreeBSD wrote: > list if you insist on attacking me there. Maybe Karl was right, some people > in the FreeBSD organization really do think they are above the rest of us. I > however do not share that belief. So, are you done? If you had half of the etiquette and knowledge on e-mail you previously have stated you have, you'd realize that phk doesn't (nor does anyone with a @FreeBSD.org) speak for the FreeBSD organization. Please crawl back into the hole you came out of. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 13:45: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id F3FDC152F0 for ; Mon, 10 Jan 2000 13:44:57 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA30180; Mon, 10 Jan 2000 13:44:57 -0800 (PST) (envelope-from dillon) Date: Mon, 10 Jan 2000 13:44:57 -0800 (PST) From: Matthew Dillon Message-Id: <200001102144.NAA30180@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: Re: freezing... update to 1.45 of ffs_softdep.c References: <55926.947513027@critter.freebsd.dk> <200001101945.LAA29394@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : I've reproduced the softupdates ftruncate panic and have a core dump : to play with. : : -Matt Ok, Kirk fixed the softupdates ftruncate panic last night. Make sure you have version 1.45 of sys/contrib/softupdates/ffs_softdep.c I would like to know if the person reporting the getblk lockup (I think it was Poul) sees that problem solved with the vinum fix that Alfred posted in regards to or whether we still have an open issue. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 13:58:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 72138152F0; Mon, 10 Jan 2000 13:58:43 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id OAA23384; Mon, 10 Jan 2000 14:21:56 -0800 (PST) Date: Mon, 10 Jan 2000 14:21:56 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, mckusick@FreeBSD.ORG Subject: Re: freezing... Message-ID: <20000110142156.F9397@fw.wintelcom.net> References: <55926.947513027@critter.freebsd.dk> <200001101945.LAA29394@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001101945.LAA29394@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Jan 10, 2000 at 11:45:46AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000110 12:11] wrote: > I've reproduced the softupdates ftruncate panic and have a core dump > to play with. I don't have a panic, but rather many processes start to get stuck in "getblk", unfortunatly they all don't stem from a common codepath, although the first process that wedged appears to have come through indir_trunc: 1442 d8ed2700 d93a0000 1001 1422 1422 004006 3 ranlib getblk cc50a85(kgdb) proc 0xd8ed2700 (kgdb) bt #0 mi_switch () at machine/globals.h:117 #1 0xc015d869 in tsleep (ident=0xcc50a850, priority=0x14, wmesg=0xc0292de1 "getblk", timo=0x0) at ../../kern/kern_synch.c:437 #2 0xc0155b06 in acquire (lkp=0xcc50a850, extflags=0x20, wanted=0x600) at ../../kern/kern_lock.c:147 #3 0xc0155dbc in lockmgr (lkp=0xcc50a850, flags=0x10022, interlkp=0xc030ba74, p=0xd8ed2700) at ../../kern/kern_lock.c:362 #4 0xc017e73e in getblk (vp=0xd66dab20, blkno=0xe565a0, size=0x2000, slpflag=0x0, slptimeo=0x0) at ../../sys/buf.h:294 #5 0xc017c72a in bread (vp=0xd66dab20, blkno=0xe565a0, size=0x2000, cred=0x0, bpp=0xd93a1bb8) at ../../kern/vfs_bio.c:498 #6 0xc02015af in indir_trunc (ip=0xd93a1bfc, dbn=0xe565a0, level=0x0, lbn=0xc, countp=0xd93a1bec) at ../../ufs/ffs/ffs_softdep.c:2040 #7 0xc02013f5 in handle_workitem_freeblocks (freeblks=0xc2315300) at ../../ufs/ffs/ffs_softdep.c:1961 #8 0xc0200e40 in softdep_setup_freeblocks (ip=0xc23ca200, length=0x0) at ../../ufs/ffs/ffs_softdep.c:1668 #9 0xc01fead6 in ffs_truncate (vp=0xd9072860, length=0x0, flags=0x0, cred=0x0, p=0xd8ed2700) at ../../ufs/ffs/ffs_inode.c:195 #10 0xc0209276 in ufs_inactive (ap=0xd93a1eb8) at ../../ufs/ufs/ufs_inode.c:84 #11 0xc020e3bd in ufs_vnoperate (ap=0xd93a1eb8) at ../../ufs/ufs/ufs_vnops.c:2283 #12 0xc0185145 in vput (vp=0xd9072860) at vnode_if.h:794 #13 0xc0188739 in unlink (p=0xd8ed2700, uap=0xd93a1f80) at ../../kern/vfs_syscalls.c:1421 #14 0xc026f7ba in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x808b300, tf_esi = 0x8076170, tf_ebp = 0xbfbffa04, tf_isp = 0xd93a1fd4, tf_ebx = 0x8076160, tf_edx = 0x8074060, tf_ecx = 0x0, tf_eax = 0xa, tf_trapno = 0x7, tf_err = 0x2, tf_eip = 0x180c41cc, tf_cs = 0x1f, tf_eflags = 0x293, tf_esp = 0xbfbff9c8, tf_ss = 0x2f}) at ../../i386/i386/trap.c:1057 after that it starts spreading: 1478 d8ed3480 d8f32000 1001 1477 1478 004006 3 zsh getblk cc50b148 1477 d8ed3a80 d8f24000 1001 369 1477 004106 3 rxvt getblk cc50b148 1473 d8ed2a00 d8fbf000 1001 1466 1473 004006 3 cvs getblk cc4a39e8 with varied tracebacks: (kgdb) proc 0xd8ed3480 (kgdb) bt #0 mi_switch () at machine/globals.h:117 #1 0xc015d869 in tsleep (ident=0xcc50b148, priority=0x14, wmesg=0xc0292de1 "getblk", timo=0x0) at ../../kern/kern_synch.c:437 #2 0xc0155b06 in acquire (lkp=0xcc50b148, extflags=0x20, wanted=0x600) at ../../kern/kern_lock.c:147 #3 0xc0155dbc in lockmgr (lkp=0xcc50b148, flags=0x10022, interlkp=0xc030ba74, p=0xd8ed3480) at ../../kern/kern_lock.c:362 #4 0xc017e73e in getblk (vp=0xd66dcf60, blkno=0x20090, size=0x2000, slpflag=0x0, slptimeo=0x0) at ../../sys/buf.h:294 #5 0xc017c72a in bread (vp=0xd66dcf60, blkno=0x20090, size=0x2000, cred=0x0, bpp=0xd8f33dec) at ../../kern/vfs_bio.c:498 #6 0xc01fe869 in ffs_update (vp=0xd8e880e0, waitfor=0x0) at ../../ufs/ffs/ffs_inode.c:98 #7 0xc02092ca in ufs_inactive (ap=0xd8f33e40) at ../../ufs/ufs/ufs_inode.c:92 #8 0xc020e3bd in ufs_vnoperate (ap=0xd8f33e40) at ../../ufs/ufs/ufs_vnops.c:2283 #9 0xc018507d in vrele (vp=0xd8e880e0) at vnode_if.h:794 #10 0xc018bbb3 in vn_close (vp=0xd8e880e0, flags=0x1, cred=0xc2243c80, p=0xd8ed3480) at ../../kern/vfs_vnops.c:232 #11 0xc018c414 in vn_closefile (fp=0xc1fb6000, p=0xd8ed3480) at ../../kern/vfs_vnops.c:630 #12 0xc01526fd in fdrop (fp=0xc1fb6000, p=0xd8ed3480) at ../../sys/file.h:211 #13 0xc015263b in closef (fp=0xc1fb6000, p=0xd8ed3480) at ../../kern/kern_descrip.c:1003 #14 0xc0151d98 in close (p=0xd8ed3480, uap=0xd8f33f80) at ../../kern/kern_descrip.c:507 #15 0xc026f7ba in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x80a9000, tf_esi = 0x1, tf_ebp = 0xbfbff9c8, tf_isp = 0xd8f33fd4, tf_ebx = 0x1816d3c4, tf_edx = 0x80a9138, tf_ecx = 0x2, tf_eax = 0x6, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0x1812a22c, tf_cs = 0x1f, tf_eflags = 0x283, tf_esp = 0xbfbff98c, tf_ss = 0x2f}) at ../../i386/i386/trap.c:1057 (kgdb) proc 0xd8ed3a80 (kgdb) bt #0 mi_switch () at machine/globals.h:117 #1 0xc015d869 in tsleep (ident=0xcc50b148, priority=0x14, wmesg=0xc0292de1 "getblk", timo=0x0) at ../../kern/kern_synch.c:437 #2 0xc0155b06 in acquire (lkp=0xcc50b148, extflags=0x20, wanted=0x600) at ../../kern/kern_lock.c:147 #3 0xc0155dbc in lockmgr (lkp=0xcc50b148, flags=0x10022, interlkp=0xc030ba74, p=0xd8ed3a80) at ../../kern/kern_lock.c:362 #4 0xc017e73e in getblk (vp=0xd66dcf60, blkno=0x20090, size=0x2000, slpflag=0x0, slptimeo=0x0) at ../../sys/buf.h:294 #5 0xc017c72a in bread (vp=0xd66dcf60, blkno=0x20090, size=0x2000, cred=0x0, bpp=0xd8f25dec) at ../../kern/vfs_bio.c:498 #6 0xc01fe869 in ffs_update (vp=0xd66d90e0, waitfor=0x0) at ../../ufs/ffs/ffs_inode.c:98 #7 0xc02092ca in ufs_inactive (ap=0xd8f25e40) at ../../ufs/ufs/ufs_inode.c:92 #8 0xc020e3bd in ufs_vnoperate (ap=0xd8f25e40) at ../../ufs/ufs/ufs_vnops.c:2283 #9 0xc018507d in vrele (vp=0xd66d90e0) at vnode_if.h:794 #10 0xc018bbb3 in vn_close (vp=0xd66d90e0, flags=0x1, cred=0xc2312f00, p=0xd8ed3a80) at ../../kern/vfs_vnops.c:232 #11 0xc018c414 in vn_closefile (fp=0xc200ab40, p=0xd8ed3a80) at ../../kern/vfs_vnops.c:630 #12 0xc01526fd in fdrop (fp=0xc200ab40, p=0xd8ed3a80) at ../../sys/file.h:211 #13 0xc015263b in closef (fp=0xc200ab40, p=0xd8ed3a80) at ../../kern/kern_descrip.c:1003 #14 0xc0151d98 in close (p=0xd8ed3a80, uap=0xd8f25f80) at ../../kern/kern_descrip.c:507 #15 0xc026f7ba in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x8064800, tf_esi = 0x1, tf_ebp = 0xbfbff770, tf_isp = 0xd8f25fd4, tf_ebx = 0x181a03c4, tf_edx = 0x8064938, tf_ecx = 0x806c000, tf_eax = 0x6, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0x1815d22c, tf_cs = 0x1f, tf_eflags = 0x287, tf_esp = 0xbfbff734, tf_ss = 0x2f}) at ../../i386/i386/trap.c:1057 (kgdb) proc 0xd8ed2a00 (kgdb) bt #0 mi_switch () at machine/globals.h:117 #1 0xc015d869 in tsleep (ident=0xcc4a39e8, priority=0x14, wmesg=0xc0292de1 "getblk", timo=0x0) at ../../kern/kern_synch.c:437 #2 0xc0155b06 in acquire (lkp=0xcc4a39e8, extflags=0x20, wanted=0x600) at ../../kern/kern_lock.c:147 #3 0xc0155dbc in lockmgr (lkp=0xcc4a39e8, flags=0x10022, interlkp=0xc030ba74, p=0xd8ed2a00) at ../../kern/kern_lock.c:362 #4 0xc017e73e in getblk (vp=0xd66dcf60, blkno=0x20950, size=0x2000, slpflag=0x0, slptimeo=0x0) at ../../sys/buf.h:294 #5 0xc017c72a in bread (vp=0xd66dcf60, blkno=0x20950, size=0x2000, cred=0x0, bpp=0xd8fc0bb8) at ../../kern/vfs_bio.c:498 #6 0xc02015af in indir_trunc (ip=0xd8fc0bfc, dbn=0x20950, level=0x0, lbn=0xc, countp=0xd8fc0bec) at ../../ufs/ffs/ffs_softdep.c:2040 #7 0xc02013f5 in handle_workitem_freeblocks (freeblks=0xc230c000) at ../../ufs/ffs/ffs_softdep.c:1961 #8 0xc0200e40 in softdep_setup_freeblocks (ip=0xc2366800, length=0x0) at ../../ufs/ffs/ffs_softdep.c:1668 #9 0xc01fead6 in ffs_truncate (vp=0xd907aa00, length=0x0, flags=0x0, cred=0x0, p=0xd8ed2a00) at ../../ufs/ffs/ffs_inode.c:195 #10 0xc0209276 in ufs_inactive (ap=0xd8fc0eb8) at ../../ufs/ufs/ufs_inode.c:84 #11 0xc020e3bd in ufs_vnoperate (ap=0xd8fc0eb8) at ../../ufs/ufs/ufs_vnops.c:2283 #12 0xc0185145 in vput (vp=0xd907aa00) at vnode_if.h:794 #13 0xc0188739 in unlink (p=0xd8ed2a00, uap=0xd8fc0f80) at ../../kern/vfs_syscalls.c:1421 #14 0xc026f7ba in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x0, tf_esi = 0x80bf180, tf_ebp = 0xbfbff71c, tf_isp = 0xd8fc0fd4, tf_ebx = 0x80bf180, tf_edx = 0x5, tf_ecx = 0x1b, tf_eax = 0xa, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0x1813f1cc, tf_cs = 0x1f, tf_eflags = 0x283, tf_esp = 0xbfbff6f0, tf_ss = 0x2f}) at ../../i386/i386/trap.c:1057 have fun, I know I am. :) it seems that ranlib is caught on someone else's buffer lock in getblk on the BUF_TIMELOCK() call, the lock looks like this: #2 0xc0155b06 in acquire (lkp=0xcc50a850, extflags=0x20, wanted=0x600) at ../../kern/kern_lock.c:147 147 error = tsleep(lkp, lkp->lk_prio, lkp->lk_wmesg, lkp->lk_timo); (kgdb) print *lkp $5 = { lk_interlock = { lock_data = 0x0 }, lk_flags = 0x200400, lk_sharecount = 0x0, lk_waitcount = 0x1, lk_exclusivecount = 0x1, lk_prio = 0x14, lk_wmesg = 0xc0292de1 "getblk", lk_timo = 0x0, lk_lockholder = 0xfffffffe } thanks, -- -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 14: 0:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9D633153FB for ; Mon, 10 Jan 2000 14:00:25 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id OAA23419; Mon, 10 Jan 2000 14:23:38 -0800 (PST) Date: Mon, 10 Jan 2000 14:23:38 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing... update to 1.45 of ffs_softdep.c Message-ID: <20000110142338.G9397@fw.wintelcom.net> References: <55926.947513027@critter.freebsd.dk> <200001101945.LAA29394@apollo.backplane.com> <200001102144.NAA30180@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001102144.NAA30180@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Jan 10, 2000 at 01:44:57PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000110 14:09] wrote: > > : I've reproduced the softupdates ftruncate panic and have a core dump > : to play with. > : > : -Matt > > Ok, Kirk fixed the softupdates ftruncate panic last night. Make sure > you have version 1.45 of sys/contrib/softupdates/ffs_softdep.c > > I would like to know if the person reporting the getblk lockup (I think > it was Poul) sees that problem solved with the vinum fix that Alfred > posted in regards to or whether we still have an open issue. still a problem, just got snagged a few moments ago, there's a traceback already on the way. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 14: 8:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 9CCAA14CFD for ; Mon, 10 Jan 2000 14:07:49 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA62743; Mon, 10 Jan 2000 23:07:29 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing... update to 1.45 of ffs_softdep.c In-reply-to: Your message of "Mon, 10 Jan 2000 13:44:57 PST." <200001102144.NAA30180@apollo.backplane.com> Date: Mon, 10 Jan 2000 23:07:29 +0100 Message-ID: <62741.947542049@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001102144.NAA30180@apollo.backplane.com>, Matthew Dillon writes: > I would like to know if the person reporting the getblk lockup (I think > it was Poul) sees that problem solved with the vinum fix that Alfred > posted in regards to or whether we still have an open issue. I don't use vinum and -current as cvsup'ed right now has the problem. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 14:17:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6C09215256 for ; Mon, 10 Jan 2000 14:17:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA30472; Mon, 10 Jan 2000 14:17:34 -0800 (PST) (envelope-from dillon) Date: Mon, 10 Jan 2000 14:17:34 -0800 (PST) From: Matthew Dillon Message-Id: <200001102217.OAA30472@apollo.backplane.com> To: Alfred Perlstein Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing... update to 1.45 of ffs_softdep.c References: <55926.947513027@critter.freebsd.dk> <200001101945.LAA29394@apollo.backplane.com> <200001102144.NAA30180@apollo.backplane.com> <20000110142338.G9397@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> I would like to know if the person reporting the getblk lockup (I think :> it was Poul) sees that problem solved with the vinum fix that Alfred :> posted in regards to or whether we still have an open issue. : :still a problem, just got snagged a few moments ago, there's a traceback :already on the way. :) : :-Alfred Is this backed by the ata driver too? If so, if either you or Poul could backoff to the wd driver and see if the problem continues, I would appreciate it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 14:49:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0539515393 for ; Mon, 10 Jan 2000 14:49:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA30876; Mon, 10 Jan 2000 14:49:10 -0800 (PST) (envelope-from dillon) Date: Mon, 10 Jan 2000 14:49:10 -0800 (PST) From: Matthew Dillon Message-Id: <200001102249.OAA30876@apollo.backplane.com> To: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: freezing... update to 1.45 of ffs_softdep.c References: <55926.947513027@critter.freebsd.dk> <200001101945.LAA29394@apollo.backplane.com> <200001102144.NAA30180@apollo.backplane.com> <20000110142338.G9397@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ::still a problem, just got snagged a few moments ago, there's a traceback ::already on the way. :) :: ::-Alfred : : Is this backed by the ata driver too? : : If so, if either you or Poul could backoff to the wd driver and see : if the problem continues, I would appreciate it. I was able to reproduce it. Never mind re: trying to use the 'wd' driver. It occurs for me w/ SCSI. It looks like a softupdates problem for sure. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 14:57:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id A63AA14F77; Mon, 10 Jan 2000 14:57:33 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id OAA56983; Mon, 10 Jan 2000 14:57:31 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id OAA07609; Mon, 10 Jan 2000 14:57:31 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001102257.OAA07609@realtime.exit.com> Subject: Re: neomagic 256av/256zx audio In-Reply-To: <387A4083.369827BE@sftw.com> from Nick Sayer at "Jan 10, 2000 08:26:44 pm" To: nsayer@FreeBSD.ORG Date: Mon, 10 Jan 2000 14:57:30 -0800 (PST) Cc: frank@exit.com, gandalf@vilnya.demon.co.uk (Cameron Grant), current@FreeBSD.ORG Reply-To: frank@exit.com 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Sayer wrote: > For what it's worth, I believe the Insperion 3500 is an oddity. > > When I was dealing with OSS, the correct configuration turned out to be > a "Generic 256AV" located at 0x530, I5, DMA 0&1 -- that is, you treat > it just like an ordinary Windows Sound System chip (CS4231). The PCI > interface, I believe, has something to do with the funky control panel gizmo > you get in Windows that sets tone and chorus effects or some such. > I haven't looked at the driver in question, but I believe it probably expects > to use an exclusively PCI interface to the chip. Somehow, I believe the > Insperion doesn't do this. Well, this doesn't help me a whole lot with pcm. I wasn't able to do it last night, but I'll get a new kernel on the laptop tonight and try to reproduce it with all-new bits. I suspect, though, that I'll get what that other guy got, a hang on the outw instruction. (I suspect that the zeroed-out *sc I saw was a remote-debugging glitch.) -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 15: 0:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 6225E15371 for ; Mon, 10 Jan 2000 15:00:14 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id PAA57019; Mon, 10 Jan 2000 15:00:09 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id PAA07661; Mon, 10 Jan 2000 15:00:09 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001102300.PAA07661@realtime.exit.com> Subject: Re: Neomagic Sounddriver hangs HP OB4150 In-Reply-To: from Bill Fumerola at "Jan 10, 2000 03:07:35 pm" To: billf@chc-chimes.com (Bill Fumerola) Date: Mon, 10 Jan 2000 15:00:09 -0800 (PST) Cc: michaelc@tmbbwmc.bbn.hp.com (#Michael Class), freebsd-current@FreeBSD.ORG Reply-To: frank@exit.com 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > On Mon, 10 Jan 2000, #Michael Class wrote: > > > The Laptop is equipped with the following Neomagic-Chip: > > chip1: irq 10 at device 0.1 on pci1 > > > > The Stack-Backtrace looks exactly the same as the other mail mentioned. A > > little bit further digging into this shows me that on this Laptop every > > read access to the second memory-area of the chip in the range of 0x600-0x8ff > > brings the machine to a halt. I can read successfully from the areas with > > offset 0x0-0x5ff and 0x900-0xFFF. The Header-File states that the mixer-I/O > > Area starts at offset 0x600. This access brings the machine to a halt during > > boot. > > > > Any suggestions of what I could try? > > Try providing us with real data. The boot message you gave us is when > pcisupport.c matches it, not when neomagic. matches it. It is impossible > to recieve the above message and then have the neomagic code fall on > its face. Um, no it's not. The very next thing that happens after that message comes out is that the nm_* routines are called to initialize the hardware and the driver. (In my case, though, it was the outw in ac97_init() that hung my machine.) -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 15: 3: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 9F17A14E7F for ; Mon, 10 Jan 2000 15:02:57 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id AAA63087; Tue, 11 Jan 2000 00:02:30 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: freezing... update to 1.45 of ffs_softdep.c In-reply-to: Your message of "Mon, 10 Jan 2000 14:17:34 PST." <200001102217.OAA30472@apollo.backplane.com> Date: Tue, 11 Jan 2000 00:02:30 +0100 Message-ID: <63085.947545350@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001102217.OAA30472@apollo.backplane.com>, Matthew Dillon writes: > If so, if either you or Poul could backoff to the wd driver and see > if the problem continues, I would appreciate it. I disabled softupdates and the problem went away. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 15:12:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [170.1.70.2]) by hub.freebsd.org (Postfix) with ESMTP id BDEB614F77 for ; Mon, 10 Jan 2000 15:12:34 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from morpheus.kfu.com (morpheus.kfu.com [170.1.70.19]) by quack.kfu.com (8.9.2/8.9.3) with ESMTP id PAA69263; Mon, 10 Jan 2000 15:10:33 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by morpheus.kfu.com with ESMTP (8.9.3//ident-1.0) id PAA00592; Mon, 10 Jan 2000 15:10:31 -0800 (PST) Message-ID: <387A66E7.812D8FA1@quack.kfu.com> Date: Mon, 10 Jan 2000 23:10:31 +0000 From: Nick Sayer Reply-To: nsayer@FreeBSD.ORG X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en-GB, en-US, en MIME-Version: 1.0 To: frank@exit.com Cc: Cameron Grant , current@FreeBSD.ORG Subject: Re: neomagic 256av/256zx audio References: <200001102257.OAA07609@realtime.exit.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frank Mayhar wrote: > Well, this doesn't help me a whole lot with pcm. I think it does. Try configuring pcm0 at 0x534 (4, not 0), irq 5, dma 0, flags 0x11 (presuming the BIOS says 0x530, irq 5, dma 0 & 1). This did work for me once upon a time, modulo bugs in the old pcm code. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 15:14:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from acutiator.nacamar.de (mail.nacamar.de [194.162.162.200]) by hub.freebsd.org (Postfix) with ESMTP id EA61615366 for ; Mon, 10 Jan 2000 15:14:06 -0800 (PST) (envelope-from rohrbach@mail.nacamar.de) Received: by acutiator.nacamar.de (Postfix, from userid 499) id D29345E8D; Tue, 11 Jan 2000 00:11:57 +0100 (CET) Date: Tue, 11 Jan 2000 00:11:57 +0100 From: "Karsten W. Rohrbach" To: Cameron Grant Cc: freebsd-current@freebsd.org Subject: Re: newpcm Message-ID: <20000111001156.A60039@nacamar.net> Reply-To: rohrbach@nacamar.net Mail-Followup-To: Cameron Grant , freebsd-current@freebsd.org References: <000901bf5b4f$0e1ba520$0304020a@rings> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <000901bf5b4f$0e1ba520$0304020a@rings>; from Cameron Grant on Mon, Jan 10, 2000 at 09:42:48AM -0000 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: rohrbach@nacamar.net X-Organisation: Nacamar Data Communications GmbH X-Address: Robert-Bosch-Str. 32, 63303 Dreieich, Germany X-Phone: vox: +49 6103 993 870 fax: +49 6103 993 199 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ahem, after some poking around and having a look at http://www.yourvote.com/pci/default.asp (excellent source for pci device numbers) i found out that the sony vaio n505x doe not use the neomagic 256av chipset for sound output but vendor 0x1073 (yamaha) dev 0x0010 (YMF744 DS-1S PCI audio). is that supported with newpcm in any way? (i mean other comparable soundboards with yamaha chipset) /k Cameron Grant (gandalf@vilnya.demon.co.uk) @ Mon, Jan 10, 2000 at 09:42:48AM -0000: > would everyone who currently has an issue outstanding with newpcm please > report it to me in the next few days directly, please, so i can get an idea > of what needs work before release. i need as much detail as possible. > > - cameron > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- > Hoover sucks. http://www.nacamar.de - http://www.nacamar.net - http://www.webmonster.de http://www.apache.de - http://www.quakeforum.de - finger rohrbach@nacamar.net KR433/KR11-RIPE - PGP-KFP = F9 A0 DF 91 74 07 6A 1C 5F 0B E0 6B 4D CD 8C 44 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 15:28:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 51AC514CE8 for ; Mon, 10 Jan 2000 15:28:21 -0800 (PST) (envelope-from doconnor@gsoft.com.au) 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 JAA14724; Tue, 11 Jan 2000 09:56:48 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [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: <3879EFB3.53CAE35C@spnetctg.com> Date: Tue, 11 Jan 2000 09:56:48 +1030 (CST) From: "Daniel O'Connor" To: Satyajit Das Subject: RE: mouse problem(please help) Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Jan-00 Satyajit Das wrote: > mouse not working . Again i run XF86Setup program ,I also choose > system , sysmouse" and port /dev/cuaa1 or /dev/sysmouse > but no work. please help me how can i work mouse in Xwindows. Well, if the mouse works on the console, then moused is working OK. You should double check your X configuration.. The port should be /dev/sysmouse, and the protocol MouseSystems. --- 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-current" in the body of the message From owner-freebsd-current Mon Jan 10 15:34: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 59FC0152B7 for ; Mon, 10 Jan 2000 15:34:04 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id PAA25436; Mon, 10 Jan 2000 15:54:39 -0800 (PST) Date: Mon, 10 Jan 2000 15:54:38 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing... update to 1.45 of ffs_softdep.c Message-ID: <20000110155438.H9397@fw.wintelcom.net> References: <55926.947513027@critter.freebsd.dk> <200001101945.LAA29394@apollo.backplane.com> <200001102144.NAA30180@apollo.backplane.com> <20000110142338.G9397@fw.wintelcom.net> <200001102249.OAA30876@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001102249.OAA30876@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Jan 10, 2000 at 02:49:10PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000110 15:13] wrote: > ::still a problem, just got snagged a few moments ago, there's a traceback > ::already on the way. :) > :: > ::-Alfred > : > : Is this backed by the ata driver too? > : > : If so, if either you or Poul could backoff to the wd driver and see > : if the problem continues, I would appreciate it. > > I was able to reproduce it. Never mind re: trying to use > the 'wd' driver. It occurs for me w/ SCSI. It looks like > a softupdates problem for sure. ugh, what fun this is, yes, i'm using vinum, softupdates, nfs and ata, but da for the vinum backing. I think i'm one of the bio bug posterboys. Anyhow, it seems that the problem happens because somewhere softupdates (or something else perhaps) LK_KERNPROCs the buffer and never lets go. I've been trying to compile with DEBUG_LOCKS for nearly half an hour but i'm having difficulty with vinum because i think it's intent on giving me a hard time w/ matching itself and the kernel and the userland. argh.. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 16:17:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id BDFA5153DC for ; Mon, 10 Jan 2000 16:17:49 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id RAA01471; Mon, 10 Jan 2000 17:04:09 -0700 (MST) Date: Mon, 10 Jan 2000 17:04:09 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <200001110004.RAA01471@narnia.plutotech.com> To: djb@Wit389306.student.utwente.nl Cc: current@FreeBSD.org Subject: Re: Strange SCSI related system hang X-Newsgroups: pluto.freebsd.current In-Reply-To: <20000109134916.A382@relativity.student.utwente.nl> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000109134916.A382@relativity.student.utwente.nl> you wrote: > Hi all, > > This morning I had a very strange (at least I've never seen it before) SCSI > related system hang. The system simply stopped responding at 9:30:03 am > this morning. I found it in this state at 13:20. It had been hanging > _hard_. No response to console, serial terminal or network. After a hard > reset the system came back online normally and is working normally again. > > Note that the machine had an uptime of 4 days, 14 hours before the problem > occured and it never happened before. > > Could this be a hardware problem? Perhaps. Is your WD drive getting hot? The ahc driver believes that, during a message out phase, the target simply dropped off the bus. It may be that the ahc driver did something to provoke that, but without a bus analyzer on the drive, it is hard to know. According to the progrom counter, we are waiting for the target to request the next byte at the time this occurs, but that request never comes. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 16:28: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-9.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.137]) by hub.freebsd.org (Postfix) with ESMTP id ECFA215375; Mon, 10 Jan 2000 16:27:52 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA27464; Mon, 10 Jan 2000 21:29:26 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA03429; Mon, 10 Jan 2000 21:33:28 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001102133.VAA03429@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: sobomax@altavista.net Cc: current@freebsd.org, brian@freebsd.org, brian@hak.lan.Awfulhak.org Subject: Re: pppctl/ppp bug In-Reply-To: Message from Maxim Sobolev of "Mon, 10 Jan 2000 17:08:43 +0200." <3879F5FB.EE08DEBF@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Jan 2000 21:33:27 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I've noticed that pppctl hangs 100% repeatable when I'm doing "set log local > +chat" followed by the "dial" command over diagnostic socket. In the case when > the "dial" command being sent over other socket this behaviour doesn't > observed. Following I'm attaching transcript of my sessions > > -Maxim Hi, Does it still hang if you also enable debug logging ? And if so, what sort of output to you see ? It's possible (perhaps) that the socket is blocking. If you open a connection that hangs then open a second connection, do you get the second one ok ? If so, what does ``show who'' and ``show route'' come up with - on both diagnostic connections ? Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 16:33:20 2000 Delivered-To: freebsd-current@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 8DDBF14EA5 for ; Mon, 10 Jan 2000 16:33:14 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id QAA27379; Mon, 10 Jan 2000 16:32:05 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda27377; Mon Jan 10 16:31:45 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id QAA08562; Mon, 10 Jan 2000 16:31:45 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdoL8546; Mon Jan 10 16:31:18 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id QAA02009; Mon, 10 Jan 2000 16:31:18 -0800 (PST) Message-Id: <200001110031.QAA02009@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdYk1999; Mon Jan 10 16:30:55 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Brad Knowles Cc: Jonathan Michaels , freebsd-current@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? In-reply-to: Your message of "Mon, 10 Jan 2000 14:19:10 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Jan 2000 16:30:55 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Brad Knowles writes: > At 11:46 PM +1100 2000/1/10, Jonathan Michaels wrote: > > > what sort of hardware problems, please ? > > Issues with some older Pentium motherboards apparently losing > their minds (and their timing interrupts) with the new ATA driver > (replaces the old wd driver). There are also some issues with > laptops and PC Cards, especially CardBus cards. I currently have a couple of older machines, a P120 and a 486DX/33 happily running 3.4. Would you recommend installing 4.0-current on a spare slice to verify whether it will run on these older machines or should I wait until -current settles down, e.g. is more or less in a bug-fix state? Any other pitfalls one would need to consider prior to running this kind of test? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 16:34: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id ED9AB14D80 for ; Mon, 10 Jan 2000 16:33:59 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.20.79] (dialup335.brussels.skynet.be [195.238.20.79]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id BAA28994; Tue, 11 Jan 2000 01:33:40 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <20000109164735.B515@mojave.worldwide.lemis.com> References: <200001072210.AA10196@newlgn49.unx.sas.com> <20000109164735.B515@mojave.worldwide.lemis.com> Date: Tue, 11 Jan 2000 01:33:06 +0100 To: Greg Lehey From: Brad Knowles Subject: Re: RAID benchmarks (was: Adaptec AAC-364 RAID controller support) Cc: Brad Chisholm , freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:47 PM +0800 2000/1/9, Greg Lehey wrote: > I've updated rawio and the port, and if you > (anybody) are really interested in sequential performance, you should > run the tests again. Unfortunately, that machine is no longer available for benchmarking. However, I might have another benchmarking opportunity in the near future with our replacement news spool server, so we'll have to see what I can do in the short amount of time I will have available to me. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 16:37:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7386A153D5 for ; Mon, 10 Jan 2000 16:37:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA32229; Mon, 10 Jan 2000 16:37:17 -0800 (PST) (envelope-from dillon) Date: Mon, 10 Jan 2000 16:37:17 -0800 (PST) From: Matthew Dillon Message-Id: <200001110037.QAA32229@apollo.backplane.com> To: Alfred Perlstein Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing... update to 1.45 of ffs_softdep.c References: <55926.947513027@critter.freebsd.dk> <200001101945.LAA29394@apollo.backplane.com> <200001102144.NAA30180@apollo.backplane.com> <20000110142338.G9397@fw.wintelcom.net> <200001102249.OAA30876@apollo.backplane.com> <20000110155438.H9397@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following patch should fix the problem temporarily until Kirk can dig into it and figure out what went wrong. -Matt Index: sys/contrib//softupdates/ffs_softdep.c =================================================================== RCS file: /FreeBSD/FreeBSD-CVS/src/sys/contrib/softupdates/ffs_softdep.c,v retrieving revision 1.45 diff -u -r1.45 ffs_softdep.c --- sys/contrib//softupdates/ffs_softdep.c 2000/01/10 08:39:03 1.45 +++ sys/contrib//softupdates/ffs_softdep.c 2000/01/11 00:20:55 @@ -1663,10 +1663,13 @@ * still have a bitmap dependency, then the inode has never been * written to disk, so we can process the freeblks immediately. */ +#if 0 if ((inodedep->id_state & DEPCOMPLETE) == 0) { FREE_LOCK(&lk); handle_workitem_freeblocks(freeblks); - } else { + } else +#endif + { WORKLIST_INSERT(&inodedep->id_bufwait, &freeblks->fb_list); FREE_LOCK(&lk); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 18:58:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from tiger1.nownuri.net (tiger1.nownuri.net [203.238.128.52]) by hub.freebsd.org (Postfix) with ESMTP id 7244515327 for ; Mon, 10 Jan 2000 18:58:19 -0800 (PST) (envelope-from plite@nownuri.net) Received: (from k3@localhost) by tiger1.nownuri.net (8.9.0/H/8.9.0) id LAA27025; Tue, 11 Jan 2000 11:58:02 +0900 (KST) Date: Tue, 11 Jan 2000 11:58:02 +0900 (KST) From: °í¹üŒ® Message-Id: <200001110258.LAA27025@tiger1.nownuri.net> To: freebsd-current@freebsd.org Subject: i want to join the mailing list.! MIME-Version: 1.0 Content-Type: text/plain; charset=EUC-KR Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG how do i.? :) --MIME Multi-part separator-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 19: 9:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by hub.freebsd.org (Postfix) with ESMTP id 5A1991528F for ; Mon, 10 Jan 2000 19:09:44 -0800 (PST) (envelope-from archer@lucky.net) Received: from 207-172-201-64.s1.as2.xnb.nj.dialup.rcn.com ([207.172.201.64] helo=unknown.nowhere.org) by smtp03.mrf.mail.rcn.net with esmtp (Exim 2.12 #3) id 127rgb-0003Ft-00 for current@freebsd.org; Mon, 10 Jan 2000 22:09:33 -0500 Received: (from archer@localhost) by unknown.nowhere.org (8.9.3/8.9.3) id WAA00636; Mon, 10 Jan 2000 22:06:59 -0500 (EST) (envelope-from archer) Date: Mon, 10 Jan 2000 22:06:59 -0500 (EST) Message-Id: <200001110306.WAA00636@unknown.nowhere.org> From: Alexander Litvin To: current@freebsd.org Subject: Re: freezing... update to 1.45 of ffs_softdep.c X-Newsgroups: unknown.freebsd.current In-Reply-To: <62741.947542049@critter.freebsd.dk> User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <62741.947542049@critter.freebsd.dk> you wrote: > In message <200001102144.NAA30180@apollo.backplane.com>, Matthew Dillon writes: >> I would like to know if the person reporting the getblk lockup (I think >> it was Poul) sees that problem solved with the vinum fix that Alfred >> posted in regards to or whether we still have an open issue. > I don't use vinum and -current as cvsup'ed right now has the problem. I just saw the same: two processes got frozen in getblk (tin and mutt). No makeworld, no activity on the system at all -- just reading news and mail. After a minute or so the whole system froze. It's with version 1.46 of ffs_softdep.c > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! --- "Nuclear war can ruin your whole compile." -- Karl Lehenbauer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 19:26: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 16F0F15359 for ; Mon, 10 Jan 2000 19:25:51 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA62762; Mon, 10 Jan 2000 22:24:59 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Mon, 10 Jan 2000 22:24:59 -0500 (EST) From: Chuck Robey To: =?ISO-8859-1?B?sO25/Lyu?= Cc: freebsd-current@FreeBSD.ORG Subject: Re: i want to join the mailing list.! In-Reply-To: <200001110258.LAA27025@tiger1.nownuri.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, °í¹üŒ® wrote: > how do i.? :) http://www.freebsd.org/support.html#mailing-list ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 19:36:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust186.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 20A3314CD4 for ; Mon, 10 Jan 2000 19:36:12 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Mon, 10 Jan 2000 22:34:25 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: current@FreeBSD.org Subject: ATAPI broken, but why? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sure everyone's seen my e-mail and others' e-mail about ATAPI in the ATA driver, at least, being broken (WRT CD-Rs). The question is, does anyone have any idea at all why? I tried reverting to just before the CDRIOC* changes, and that didn't help (using wormcontrol to test that). If any of you have any hints at all, please let me know. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 20:16:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 8281314E55 for ; Mon, 10 Jan 2000 20:16:00 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id XAA46411; Mon, 10 Jan 2000 23:14:43 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001110414.XAA46411@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Ollivier Robert Cc: "FreeBSD Current Users' list" From: "Louis A. Mamakos" Subject: Re: Buildworld fails References: <20000110190708.A34876@caerdonn.eurocontrol.fr> In-reply-to: Your message of "Mon, 10 Jan 2000 19:07:08 +0100." <20000110190708.A34876@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Jan 2000 23:14:43 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As Pascal Hofstee wrote: > > With CURRENT-sources updates within an hour ago ... buildworld fails: > > Revert to version 1.26 of gnu/lib/libdialog/Makefile. someone broke it when > he decided to install all the files in TESTS/... > > Don't forget to revert to 1.34 of lib/libncurses/Makefile for the same > reason. Grrr. Yeah, this happened to me too. It seems that mtree doesn't get run to populate the bootstrap build environment. Of course, installing documentation and examples into the build environment probably is a waste of time and disk space anyway.. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 20:37:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id E1AEE153E3; Mon, 10 Jan 2000 20:37:29 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from dyn-18.blackbox-2.netaxs.com (dyn-18.blackbox-2.netaxs.com [207.106.60.18]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id XAA09054; Mon, 10 Jan 2000 23:20:17 -0500 (EST) Date: Mon, 10 Jan 2000 23:20:17 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: Brian Fundakowski Feldman Cc: current@FreeBSD.ORG Subject: Re: ATAPI broken, but why? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Brian Fundakowski Feldman wrote: >I'm sure everyone's seen my e-mail and others' e-mail about ATAPI in the >ATA driver, at least, being broken (WRT CD-Rs). The question is, does >anyone have any idea at all why? I tried reverting to just before the >CDRIOC* changes, and that didn't help (using wormcontrol to test that). >If any of you have any hints at all, please let me know. I just wanted to add for all to see that prior to the CDRIOC* changes, all was OK with my HP 8250i CD-RW unit, reading and writing both worked fine. After the changes, writing no longer works. All I get is WRITE_BIG errors from burncd (the write light never turns on) then the driver endlessly tries to reset the CD-R drive and I have to hit the reset button to reboot. My HP Colorado 8G ATAPI tape never probed/worked at all with the new ATA driver. Anyone out there have one that's working? The wd* drivers, although obselete now, handled all of my ATA-ATAPI stuff without any problems. I find it hard to believe that 4.0 will get released with less hardware support than 3.x. -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 21:53:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 3505A1540A for ; Mon, 10 Jan 2000 21:53:20 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id VAA60568 for ; Mon, 10 Jan 2000 21:53:00 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id VAA18103 for current@freebsd.org; Mon, 10 Jan 2000 21:52:59 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001110552.VAA18103@realtime.exit.com> Subject: Re: neomagic 256av/256zx audio In-Reply-To: <000d01bf5b39$f31275c0$0304020a@rings> from Cameron Grant at "Jan 10, 2000 07:11:43 am" To: gandalf@vilnya.demon.co.uk (Cameron Grant) Date: Mon, 10 Jan 2000 20:11:01 -0800 (PST) Cc: frank@exit.com Reply-To: frank@exit.com 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cameron Grant wrote: [Charset iso-8859-1 unsupported, filtering to ASCII...] > > I did that and it still hangs. Let me see if it's for the same reason. > > Maybe *sc is getting stepped on somehow? > very odd. i have no idea what is going on. > i have committed bits, so try again in a few hours. Okay, I've rebuilt the kernel and rerun the test, again doing remote debugging. As I thought, the zeroed *sc was a quirk of that debugging session. The same hang is happening to me as is happening to the other guy with a hang at 0x600 (sorry, I forgot his name and didn't retain the email). Here's the backtrace: #0 nm_rd (sc=0xc0d83100, regno=1536, size=2) at ../../dev/sound/pci/neomagic.c:142 #1 0xc0207267 in nm_rdcd (devinfo=0xc0d83100, regno=0) at ../../dev/sound/pci/neomagic.c:232 #2 0xc020293e in ac97_init (codec=0xc0d83000) at ../../dev/sound/pcm/ac97.c:251 #3 0xc0202b16 in ac97mix_init (m=0xc073d30c) at ../../dev/sound/pcm/ac97.c:304 #4 0xc0205854 in mixer_init (d=0xc073d200, m=0xc0288c40, devinfo=0xc0d83000) at ../../dev/sound/pcm/mixer.c:53 #5 0xc0207b4b in nm_pci_attach (dev=0xc0d87280) at ../../dev/sound/pci/neomagic.c:595 #6 0xc011e1be in DEVICE_ATTACH (dev=0xc0d87280) at device_if.c:63 #7 0xc0148b87 in device_probe_and_attach (dev=0xc0d87280) at ../../kern/subr_bus.c:1137 #8 0xc0149876 in bus_generic_attach (dev=0xc0d87480) at ../../kern/subr_bus.c:1831 #9 0xc011e1be in DEVICE_ATTACH (dev=0xc0d87480) at device_if.c:63 #10 0xc0148b87 in device_probe_and_attach (dev=0xc0d87480) at ../../kern/subr_bus.c:1137 #11 0xc0149876 in bus_generic_attach (dev=0xc0d87b80) at ../../kern/subr_bus.c:1831 #12 0xc01cd235 in pcib_attach (dev=0xc0d87b80) at ../../pci/pcisupport.c:747 #13 0xc011e1be in DEVICE_ATTACH (dev=0xc0d87b80) at device_if.c:63 #14 0xc0148b87 in device_probe_and_attach (dev=0xc0d87b80) at ../../kern/subr_bus.c:1137 #15 0xc0149876 in bus_generic_attach (dev=0xc0d87d80) at ../../kern/subr_bus.c:1831 #16 0xc011e1be in DEVICE_ATTACH (dev=0xc0d87d80) at device_if.c:63 #17 0xc0148b87 in device_probe_and_attach (dev=0xc0d87d80) at ../../kern/subr_bus.c:1137 #18 0xc0149876 in bus_generic_attach (dev=0xc0d86000) at ../../kern/subr_bus.c:1831 #19 0xc011e1be in DEVICE_ATTACH (dev=0xc0d86000) at device_if.c:63 #20 0xc0148b87 in device_probe_and_attach (dev=0xc0d86000) at ../../kern/subr_bus.c:1137 #21 0xc0149876 in bus_generic_attach (dev=0xc0d86080) at ../../kern/subr_bus.c:1831 #22 0xc0231579 in nexus_attach (dev=0xc0d86080) at ../../i386/i386/nexus.c:199 #23 0xc011e1be in DEVICE_ATTACH (dev=0xc0d86080) at device_if.c:63 #24 0xc0148b87 in device_probe_and_attach (dev=0xc0d86080) at ../../kern/subr_bus.c:1137 #25 0xc0149db6 in root_bus_configure () at ../../kern/subr_bus.c:2214 #26 0xc0227e58 in configure (dummy=0x0) at ../../i386/i386/autoconf.c:146 #27 0xc0133118 in mi_startup (framep=0xc0326fb4) at ../../kern/init_main.c:217 (kgdb) print /x regno $1 = 0x600 The hang is happening on the "movzwl (%ebx,%eax,1),%eax" at nm_rd+80: (kgdb) s 146 return bus_space_read_2(st, sh, regno); (kgdb) print $eip $2 = (void *) 0xc0207054 (kgdb) stepi 0xc0207056 146 return bus_space_read_2(st, sh, regno); (kgdb) stepi 198 #if defined(_I386_BUS_MEMIO_H_) (kgdb) print $eip $3 = (void *) 0xc0207060 That's this instruction: 0xc0207060 : movzwl (%ebx,%eax,1),%eax (kgdb) print /x $ebx $5 = 0x600 (kgdb) print /x $eax $6 = 0xc87d2000 $eax being 0xc87d2000 seems a little odd, but I don't remember my 80x86 assembly well enough to say whether it's right or wrong. In the meantime, I'll try Nick Sayer's trick. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 21:55:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 21E7314C82; Mon, 10 Jan 2000 21:55:49 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id VAA60628; Mon, 10 Jan 2000 21:55:47 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id VAA18163; Mon, 10 Jan 2000 21:55:47 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001110555.VAA18163@realtime.exit.com> Subject: Re: neomagic 256av/256zx audio In-Reply-To: <387A66E7.812D8FA1@quack.kfu.com> from Nick Sayer at "Jan 10, 2000 11:10:31 pm" To: nsayer@FreeBSD.ORG Date: Mon, 10 Jan 2000 21:55:47 -0800 (PST) Cc: frank@exit.com, gandalf@vilnya.demon.co.uk (Cameron Grant), current@FreeBSD.ORG Reply-To: frank@exit.com 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Sayer wrote: > Frank Mayhar wrote: > > Well, this doesn't help me a whole lot with pcm. > I think it does. Try configuring pcm0 at 0x534 (4, not 0), irq 5, > dma 0, flags 0x11 (presuming the BIOS says 0x530, irq 5, dma 0 & 1). > This did work for me once upon a time, modulo bugs in the old pcm code. Sigh. I tried this. I get the *exact* same hang as before. It looks like newpcm is trying to get the device on the pci bus without respect to the configuration in the config file. The line I used was device pcm0 at isa? port 0x534 irq 5 drq 0 flags 0x11 with no "device pcm0" line. Argh. Next suggestion? -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 22:40:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 0880815092 for ; Mon, 10 Jan 2000 22:40:17 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.9.3/8.9.3) with ESMTP id HAA16233; Tue, 11 Jan 2000 07:40:13 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id HAA31316; Tue, 11 Jan 2000 07:39:40 +0100 (CET) (envelope-from andreas) Date: Tue, 11 Jan 2000 07:39:40 +0100 From: Andreas Klemm To: George Cox Cc: freebsd-current@FreeBSD.ORG Subject: Re: -pipe switch in kernel compilation Message-ID: <20000111073939.A31293@titan.klemm.gtn.com> References: <20000110165543.A5720@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000110165543.A5720@extremis.demon.co.uk>; from gjvc@extremis.demon.co.uk on Mon, Jan 10, 2000 at 04:55:43PM +0000 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 04:55:43PM +0000, George Cox wrote: > G'day, > > While compiling a kernel today, I noticed that the '-pipe' option to gcc > was not being used. Is there any reason for this? I think this is the (historical) default, so that people with only 4-8 MB of RAM don't get into trouble ;-) Where 4 MB isn't sufficient anymore with a GENERIC kernel. You need at least 6 MB or so to boot, then compile a custom kernel and then, if you are lucky, can perhaps run with 4 MB. But that information is about 1-2 years old, don't know, if we perhaps already need 6-8 MB nowadays... Though it's zillions better than M$ crap. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 22:47:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 58F5914E7F for ; Mon, 10 Jan 2000 22:47:49 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 127v5l-00012h-00 for current@freebsd.org; Tue, 11 Jan 2000 06:47:46 +0000 Date: Tue, 11 Jan 2000 07:47:45 +0100 (CET) From: Marc Schneiders To: current@freebsd.org Subject: ssh2: piperd = hanging? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trying to use cvs to get a working copy of /usr/src from the /home/ncvs of one machine to another, cvs just hangs. Top displays as state for cvs `piperd'. I have not been able to find this documented in the top man page. A guess: pipe reading data? In my case it indicates cvs or ssh hanging :-( There are no data read anymore in any case (for which top seems to print `getblk' or `RUN' during the short time cvs works). Things remain like this until I kill cvs through ^C. This happens a few seconds after entering the cvs command. When I retry: the same result, but not always at the same file. Maybe I should mention that after entering the password (for ssh) I get: `stdin isn't a terminal'. The solution for this problem seems to be to set CVS_RSH to ssh1. Both `ssh' and `ssh2' produce the abortive cvs. Both machines run ssh2 2.0.13 from the ports. uname -a: ... 4.0 CURRENT Dec 26 ... 1999 -- Marc Schneiders marc@venster.nl marc@oldserver.demon.nl propro 7:00am up 11 days, 8:49, load average: 2.03 2.04 2.00 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 10 23:15:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id C515814E6B for ; Mon, 10 Jan 2000 23:15:26 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 15528 invoked from network); 11 Jan 2000 07:15:25 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 11 Jan 2000 07:15:25 -0000 Message-ID: <387AD873.1814A5F9@cvzoom.net> Date: Tue, 11 Jan 2000 02:14:59 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Marc Schneiders Cc: current@freebsd.org Subject: Re: ssh2: piperd = hanging? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Schneiders wrote: > > Trying to use cvs to get a working copy of /usr/src from the > /home/ncvs of one machine to another, cvs just hangs. Top displays as > state for cvs `piperd'. I have not been able to find this documented > in the top man page. A guess: pipe reading data? In my case it > indicates cvs or ssh hanging :-( There are no data read anymore in any > case (for which top seems to print `getblk' or `RUN' during the short > time cvs works). Things remain like this until I kill cvs through ^C. `piperd' means a process is reading from a pipe. In your case, maybe reading from a pipe is causing a hang. Of course, the inverse of piperd is pipewt, I believe, which means the process is writing to a pipe. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 0:12:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 8D43914BCD for ; Tue, 11 Jan 2000 00:12:04 -0800 (PST) (envelope-from michaelc@tmbbwmc.bbn.hp.com) Received: from tmbbmcc3.bbn.hp.com (tmbbmcc3.bbn.hp.com [15.136.126.78]) by palrel3.hp.com (Postfix) with ESMTP id 734A286B; Tue, 11 Jan 2000 00:12:02 -0800 (PST) Received: from tmbbwmc.bbn.hp.com (michaelc@tmbbwmc.bbn.hp.com [15.136.124.25]) by tmbbmcc3.bbn.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id JAA27939; Tue, 11 Jan 2000 09:08:27 +0100 (MET) Received: from localhost (michaelc@localhost) by tmbbwmc.bbn.hp.com (8.8.6/8.8.6) with ESMTP id JAA11101; Tue, 11 Jan 2000 09:12:00 +0100 (MET) Date: Tue, 11 Jan 2000 09:11:59 +0100 (MET) From: #Michael Class To: Bill Fumerola Cc: freebsd-current@freebsd.org Subject: Re: Neomagic Sounddriver hangs HP OB4150 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Bill Fumerola wrote: > On Mon, 10 Jan 2000, #Michael Class wrote: > > > The Laptop is equipped with the following Neomagic-Chip: > > chip1: irq 10 at device 0.1 on pci1 > > > > The Stack-Backtrace looks exactly the same as the other mail mentioned. A > > little bit further digging into this shows me that on this Laptop every > > read access to the second memory-area of the chip in the range of 0x600-0x8ff > > brings the machine to a halt. I can read successfully from the areas with > > offset 0x0-0x5ff and 0x900-0xFFF. The Header-File states that the mixer-I/O > > Area starts at offset 0x600. This access brings the machine to a halt during > > boot. > > > > Any suggestions of what I could try? > > Try providing us with real data. The boot message you gave us is when > pcisupport.c matches it, not when neomagic. matches it. It is impossible > to recieve the above message and then have the neomagic code fall on > its face. I am sorry, but the obove message was just copied from a kernel without the neomagic driver to show which chip (256AX instead of 256 Zsomething) the Laptop has. It was not intended to be the message during boot with the new driver. Given the fact that someone else already gave an exact stack-backtrace which is identical of what I am getting (ac97_init calls nm_rd with an argument of 0x600 and size 2 which then does a bus_space_read2 where it hangs. (Names unfortunately not exact, I do have the code not at my hands)) I have not yet setup a serial console on this machine, so I am not able to provide you with the boot-messages of the kernel that hangs. Here is the bootmessage of the kernel without the neomagic-sound-driver (Jan 7th.) Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Jan 7 14:04:10 MET 2000 michaelc@pc-micha.mc.hp.com:/usr/src/sys/compile/MCOB4150 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (397.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 201326592 (196608K bytes) avail memory = 191954944 (187456K bytes) Preloaded elf kernel "kernel" at 0xc02eb000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 9 at device 0.0 on pci1 chip1: irq 10 at device 0.1 on pci1 pcic-pci0: at device 4.0 on pci0 pcic-pci1: at device 4.1 on pci0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 10 chip2: at device 7.3 on pci0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic0: at irq 3 on isa0 pccard0: on pcic0 pccard1: on pcic0 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 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, unlimited logging ad0: ATA-4 disk at ata0 as master ad0: 9590MB (19640880 sectors), 19485 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: DVD-ROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, ??? acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked pccard: card inserted, slot 0 pccard: card inserted, slot 1 ata_command: timeout waiting for interrupt Mounting root from ufs:/dev/ad0s3a /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-364 $ /dev/vmmon: Module vmmon: initialized sio2 at port 0x3e8-0x3ef irq 7 slot 0 on pccard0 sio2: type 16550A ed0 at port 0x340-0x35f irq 11 slot 1 on pccard1 ed0: address 00:e0:98:03:a4:ad, type Linksys (16 bit) And here the kernel-configuration: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. machine i386 cpu I686_CPU ident MCOB4150 maxusers 64 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols # This allows you to actually store this configuration file into # the kernel binary itself, where it may be later read by saying: # strings /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL # options INCLUDE_CONFIG_FILE # Include this file in kernel options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options CD9660_ROOT #CD-ROM usable as root device options FFS_ROOT #FFS usable as root device [keep this!] options NFS_ROOT #NFS usable as root device options SOFTUPDATES options MSGBUF_SIZE=65536 # # Allow user-mode programs to manipulate their local descriptor tables. # This option is required for the WINE Windows(tm) emulator, and is # not used by anything else (that we know of). # options USER_LDT #allow user-level control of i386 ldt # # These three options provide support for System V Interface # Definition-style interprocess communication, in the form of shared # memory, semaphores, and message queues, respectively. # options SYSVSHM options SYSVSEM options SYSVMSG # # This option includes a MD5 routine in the kernel, this is used for # various authentication and privacy uses. # options MD5 options COMPAT_LINUX ##################################################################### # POSIX P1003.1B # Real time extensions added int the 1993 Posix # P1003_1B: Infrastructure # _KPOSIX_PRIORITY_SCHEDULING: Build in _POSIX_PRIORITY_SCHEDULING # _KPOSIX_VERSION: Version kernel is built for options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L ##################################################################### # # Enable the following (IPFIREWALL_VERBOSE optional) to enable the IP firewall # code. This is used in conjunction with the ipfw(1) command. See the # man page for more details. options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable xparent proxy support options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets ##################################################################### # ICMP_BANDLIM enables icmp error response bandwidth limiting. You # typically want this option as it will help protect the machine from # D.O.S. packet attacks. # options ICMP_BANDLIM ##################################################################### # DEBUGGING OPTIONS # # Enable the kernel debugger. # options DDB controller isa0 at nexus? controller pci0 at nexus? controller fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # # ATA and ATAPI devices # This is work in progress, use at your own risk. # It currently reuses the majors of wd.c and freinds. # It cannot co-exist with the old system in one kernel. # You only need one "controller ata0" for it to find all # PCI devices on modern machines. controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x01 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? # splash screen/screen saver pseudo-device splash device npx0 at nexus? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at nexus? # Advanced Power Management #SOUND: device pcm0 # PCCARD (PCMCIA) support controller card0 device pcic0 at isa? irq 3 device pcic1 at isa? irq 3 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 #device sio2 at isa? disable port "IO_COM3" irq 11 #device sio3 at isa? disable port "IO_COM4" irq 9 #device ppc0 at isa? port ? irq 7 #controller ppbus0 #device lpt0 at ppbus? # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device ed0 device ep0 pseudo-device loop pseudo-device ether pseudo-device tun pseudo-device bpf #Berkeley packet filter pseudo-device pty pseudo-device vn #Vnode driver (turns a file into a device) Michael ___________________________________________________________________________ Michael Class E-Mail: michael_class@hp.com E-Business Solution Division Phone: +49 7031 14-3707 Fax: +49 7031 14-4505 ___________________________________________________________________________ Hewlett-Packard GmbH, PO Box 1430, Mailstop ESD2, 71004 Boeblingen Sitz der Gesellschaft: Böblingen, Amtsgericht Böblingen HRB 4081 Geschäftsführer: Jörg Menno Harms (Vorsitzender),Rainer Erlat, Hans-Joachim Lueckefett,Heribert Schmitz,Fritz Schuller ___________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 0:34:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust15.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 290AF151F4; Tue, 11 Jan 2000 00:34:46 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Tue, 11 Jan 2000 03:34:43 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Stephen McKay Cc: freebsd-current@freebsd.org Subject: Re: Crash from ^T during heavy paging In-Reply-To: <200001100735.RAA51943@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Stephen McKay wrote: > The problem is that calcru() thinks that P_INMEM means that the proc > structure is fully and accurately populated. But P_INMEM is one of the > first flags set. > > So, calcru() and possibly some other places, are looking at a struct proc > before it's all there. What's the "proper" way to do it? It should really be one of the _last_ flags set, if it's to mean anything. I don't know how to explain the prevalance of race conditions in the old code, except to say it probably has to do with not planning ahead. Certainly it's not acceptable to create new race conditions now (even if it can happen by accident). So, here's something to defer P_INMEM til the end, when the process is really "ready": --- sys/kern/kern_fork.c Tue Dec 7 22:11:35 1999 +++ /tmp/kern_fork.c Tue Jan 11 03:32:44 2000 @@ -351,7 +351,7 @@ * Increase reference counts on shared objects. * The p_stats and p_sigacts substructs are set in vm_fork. */ - p2->p_flag = P_INMEM; + p2->p_flag = 0; if (p1->p_flag & P_PROFIL) startprofclock(p2); MALLOC(p2->p_cred, struct pcred *, sizeof(struct pcred), @@ -499,6 +499,7 @@ microtime(&(p2->p_stats->p_start)); p2->p_acflag = AFORK; (void) splhigh(); + p2->p_flag |= P_INMEM; p2->p_stat = SRUN; setrunqueue(p2); (void) spl0(); -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 0:54:51 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 3FE5A14CEB; Tue, 11 Jan 2000 00:54:46 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 2CE171CD819 for ; Tue, 11 Jan 2000 00:54:46 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 11 Jan 2000 00:54:46 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: ATA CDROM problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In addition to my lost contact problems with the ATA driver and one of my WDC drives, my CDROM no longer works properly under the new drivers. Accessing the drive causes excessive pauses and seems to chew lots of CPU in the kernel: the system becomes very sluggish with about 4 or 5 seconds to respond to a keystroke or change of virtual console. I can still mount and read CDs, but it takes about 90 seconds to mount, and about 30 to do a ls /cdrom. Reading audio CDs (e.g. with cdcontrol) does not work at all: it spins the CPU with HD and CDROM activity light solid for about 40 seconds before returning: acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04 I also get an error message at boot time, shown in the dmesg output below. This CD is a crappy old Goldstone (?), but it always worked perfectly under the old drivers. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Mon Jan 10 23:47:56 PST 2000 kkenn@morden.rebel.net.au:/usr5/src2/src/sys/compile/MORDEN Calibrating clock(s) ... TSC clock: 120041588 Hz, i8254 clock: 1193596 Hz Timecounter "i8254" frequency 1193596 Hz Timecounter "TSC" frequency 120041588 Hz CPU: Pentium/P54C (120.04-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x1bf real memory = 50331648 (49152K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x00342000 - 0x02feffff, 46850048 bytes (11438 pages) avail memory = 45527040 (44460K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fac90 bios32: Entry = 0xfb150 (c00fb150) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb180 pnpbios: Found PnP BIOS data at 0xc00fb9f0 pnpbios: Entry = f0000:ba18 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Intel Pentium detected, installing workaround for F00F bug VESA: information block 56 45 53 41 02 01 48 56 00 c0 00 00 00 00 8f 56 00 c0 20 00 de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de VESA: 29 mode(s) found VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c568f (c000568f) VESA: Tseng Labs ET4000 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=122d8086) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 155836060 bytes/sec bzero() bandwidth = 78094494 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=122d8086) pcib0: on motherboard found-> vendor=0x8086, dev=0x122d, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x122e, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x1230, revid=0x02 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 00003000, size 4 found-> vendor=0x100c, dev=0x3206, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base f0000000, size 24 found-> vendor=0x9004, dev=0x5078, revid=0x01 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 00006000, size 8 map[14]: type 1, range 32, base f1000000, size 12 pci0: on pcib0 CPU Inactivity timer: clocks Peer Concurrency: enabled CPU-to-PCI Write Bursting: enabled PCI Streaming: enabled Bus Concurrency: enabled Cache: 256K pipelined-burst secondary; L1 enabled DRAM: no memory hole, 60 MHz refresh Read burst timing: x-2-2-2/x-3-3-3 Write burst timing: x-3-3-3 RAS-CAS delay: 3 clocks isab0: at device 7.0 on pci0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: enabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: disabled, B: IRQ10, C: IRQ11, D: disabled MB0: disabled, MB1: disabled isa0: on isab0 ata-pci0: port 0x3000-0x300f at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x3000 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=50 ata0: devices = 0x3 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x3008 ata1: mask=03 status0=50 status1=00 ata1: mask=03 status0=50 status1=00 ata1: devices = 0x9 ata1 at 0x0170 irq 15 on ata-pci0 vga-pci0: mem 0xf0000000-0xf0ffffff irq 11 at device 18.0 on pci0 ahc0: port 0x6000-0x60ff mem 0xf1000000-0xf1000fff irq 10 at device 19.0 on pci0 ahc0: No SEEPROM available. ahc0: Using left over BIOS settings ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs ahc0: Downloading Sequencer Program... 408 instructions downloaded Trying Read_Port at 203 Trying Read_Port at 243 CTL0031: start dependant CTL0031: adding irq mask 0x20 CTL0031: adding dma mask 0x2 CTL0031: adding dma mask 0x20 CTL0031: adding io range 0x220-0x22f, size=0x10, align=0x1 CTL0031: adding io range 0x330-0x331, size=0x2, align=0x1 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: start dependant CTL0031: adding irq mask 0xca0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: end dependant CTL2011: start dependant CTL2011: adding irq mask 0x400 CTL2011: adding io range 0x168-0x16f, size=0x8, align=0x1 CTL2011: adding io range 0x36e-0x36f, size=0x2, align=0x1 CTL2011: start dependant CTL2011: adding irq mask 0x800 CTL2011: adding io range 0x1e8-0x1ef, size=0x8, align=0x1 CTL2011: adding io range 0x3ee-0x3ef, size=0x2, align=0x1 CTL2011: start dependant CTL2011: adding irq mask 0x9c00 CTL2011: adding io range 0x100-0x1ff, size=0x8, align=0x8 CTL2011: adding io range 0x300-0x3ff, size=0x2, align=0x2 CTL2011: start dependant CTL2011: adding irq mask 0x8000 CTL2011: adding io range 0x170-0x177, size=0x8, align=0x1 CTL2011: adding io range 0x376-0x376, size=0x1, align=0x1 CTL2011: end dependant PNPffff: adding io range 0x100-0x3f8, size=0x1, align=0x8 CTL7001: adding io range 0x200-0x207, size=0x8, align=0x1 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices 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 sio0: irq maps: 0x61 0x71 0x61 0x61 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x61 0x69 0x61 0x61 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00ff kbdc: RESET_AUX return code:00ff kbdc: RESET_AUX return code:00ff kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <12 virtual consoles, flags=0x200> sc0: fb0 kbd0 isa_probe_children: probing PnP devices sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 pcm: setmap c000, 2000; 0xc4e88000 -> c000 pcm: setmap e000, 2000; 0xc4e8a000 -> e000 ata2: iobase=0x01e8 altiobase=0x03ee bmaddr=0x0000 ata2: mask=00 status0=ff status1=ff unknown0: at port 0x1e8-0x1ef,0x3ee-0x3ef irq 11 on isa0 unknown1: at port 0x100 on isa0 unknown2: at port 0x200-0x207 on isa0 BIOS Geometries: 0:03113f3f 0..785=786 cylinders, 0..63=64 heads, 1..63=63 sectors 1:026a7f3f 0..618=619 cylinders, 0..127=128 heads, 1..63=63 sectors 2:030efe3f 0..782=783 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert disabled, rule-based forwarding disabled, unlimited logging bpf: ppp0 attached bpf: ppp1 attached new masks: bio 4008c040, tty 4003003a, net 4007003a bpf: lo0 attached Linux-ELF exec handler installed ata0-master: success setting up WDMA2 mode on PIIX chip ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 ad0: ATA-0 disk at ata0 as master ad0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 Creating DISK ad0 Creating DISK wd0 ata0-slave: success setting up WDMA2 mode on PIIX chip ad1: piomode=4 dmamode=2 udmamode=2 cblid=0 ad1: ATA-3 disk at ata0 as slave ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, WDMA2 Creating DISK ad1 Creating DISK wd1 ata1-master: success setting up WDMA2 mode on PIIX chip ad2: piomode=4 dmamode=2 udmamode=2 cblid=0 ad2: ATA-4 disk at ata1 as master ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, WDMA2 Creating DISK ad2 Creating DISK wd2 ata1-slave: piomode=3 dmamode=0 udmamode=-1 dmaflag=1 ata1-slave: timeout waiting for command=ef s=00 e=00 ata1-slave: failed setting up PIO3 mode on generic chip acd0: CDROM drive at ata1 as slave acd0: read 171KB/s (689KB/s), 256KB buffer, ??? acd0: Reads: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked, lock protected Waiting 2 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. Mounting root from ufs:wd0s2a wd0s1: type 0x6, start 63, end = 1745855, size 1745793 : OK wd0s2: type 0xa5, start 1745856, end = 3173183, size 1427328 : OK start_init: trying /sbin/init ad1s1: type 0x6, start 63, end = 2048255, size 2048193 : OK ad1s2: type 0x5, start 2048256, end = 3072383, size 1024128 : OK ad1s3: type 0xa5, start 3072384, end = 4999679, size 1927296 : OK ad1s5: type 0x6, start 2048319, end = 3072383, size 1024065 : OK ad2: ad_timeout: lost disk contact - resetting ata1: resetting devices .. ata1: mask=03 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip ata1-slave: timeout waiting for command=ef s=00 e=60 ata1-slave: failed setting up PIO3 mode on generic chip done ad2: ad_timeout: lost disk contact - resetting ata1: resetting devices .. ata1: mask=03 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip ata1-slave: timeout waiting for command=ef s=00 e=60 ata1-slave: failed setting up PIO3 mode on generic chip done ad2: ad_timeout: lost disk contact - resetting ata1: resetting devices .. ata1: mask=03 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip ata1-slave: timeout waiting for command=ef s=00 e=60 ata1-slave: failed setting up PIO3 mode on generic chip done ad2: ad_timeout: lost disk contact - resetting ata1-master: success setting up PIO4 mode on generic chip ad2: ad_timeout: trying fallback to PIO mode ata1: resetting devices .. ata1: mask=03 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip ata1-slave: timeout waiting for command=ef s=00 e=60 ata1-slave: failed setting up PIO3 mode on generic chip done To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 0:58:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 39D3615409; Tue, 11 Jan 2000 00:58:29 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 13F441CA0; Tue, 11 Jan 2000 16:57:45 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: frank@exit.com Cc: nsayer@FreeBSD.ORG, gandalf@vilnya.demon.co.uk (Cameron Grant), current@FreeBSD.ORG Subject: Re: neomagic 256av/256zx audio In-Reply-To: Message from Frank Mayhar of "Mon, 10 Jan 2000 21:55:47 PST." <200001110555.VAA18163@realtime.exit.com> Date: Tue, 11 Jan 2000 16:57:45 +0800 From: Peter Wemm Message-Id: <20000111085745.13F441CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frank Mayhar wrote: > Nick Sayer wrote: > > Frank Mayhar wrote: > > > Well, this doesn't help me a whole lot with pcm. > > I think it does. Try configuring pcm0 at 0x534 (4, not 0), irq 5, > > dma 0, flags 0x11 (presuming the BIOS says 0x530, irq 5, dma 0 & 1). > > This did work for me once upon a time, modulo bugs in the old pcm code. > > Sigh. I tried this. I get the *exact* same hang as before. It looks > like newpcm is trying to get the device on the pci bus without respect to > the configuration in the config file. > > The line I used was > device pcm0 at isa? port 0x534 irq 5 drq 0 flags 0x11 > with no "device pcm0" line. > > Argh. Next suggestion? Try changing the 'device pcm0 at .....' to this: options PNPBIOS device pcm0 with *no* 'at isa?'. See what happens. If it shows up in the pnp id tags but isn't recognized, show us the 'unknown*' lines from dmesg. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 1: 8:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5]) by hub.freebsd.org (Postfix) with ESMTP id 1F14F14CEB for ; Tue, 11 Jan 2000 01:08:37 -0800 (PST) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id LAA06044; Tue, 11 Jan 2000 11:08:00 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <200001110908.LAA06044@oskar.dev.nanoteq.co.za> Subject: Re: newpcm In-Reply-To: <000901bf5b4f$0e1ba520$0304020a@rings> from Cameron Grant at "Jan 10, 0 09:42:48 am" To: gandalf@vilnya.demon.co.uk (Cameron Grant) Date: Tue, 11 Jan 100 11:07:59 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running a current of yesterday and no panic this time :) thanx :) The only thing missing from my ESS1869 card is that audio is still only played through the right speaker ... so sound from the left at all. It would be nice if someone could fix this ... here is some info unknown10: at port 0x800-0x807 on isa0 sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 pcm0: on sbc0 unknown11: at port 0x201 on isa0 unknown12: at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 I'm also experiencing a dely in sound on most games ... on some it's up to 7 seconds behind the action of the game ... Xgalaga is an example of this delay .... Any ideas ... Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 1:35: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 7932415323 for ; Tue, 11 Jan 2000 01:34:59 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id PAA00477; Tue, 11 Jan 2000 15:34:54 +0600 (NOVT) (envelope-from nnd) Date: Tue, 11 Jan 2000 15:34:54 +0600 (NOVT) Message-Id: <200001110934.PAA00477@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Can't "kldload" modules due to "symbol NDFREE undefined" User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At least from the January 9 after 'cvsup', 'make buildworld','make installworld', 'make & install kernel' I can't 'kldload linux'. 'Kldload" says: kldload: can't load linux: Exec format error and /kernel says: /kernel: link_elf: symbol NDFREE undefined This is obviously caused by the next commit, but I can not see how it can be corrected (besides of reverting the commit, which is not the right solution IMHO ;-) =========================================================================== eivind 2000/01/08 08:20:06 PST Modified files: sys/kern vfs_subr.c sys/sys namei.h Log: Change NDFREE() from a macro to a function for the time being; the macro version caused intolerable bloat (30k). I'm likely to revisit this with an attempt at a smarter macro. Bloat noticed by: bde Revision Changes Path 1.243 +35 -1 src/sys/kern/vfs_subr.c 1.29 +2 -37 src/sys/sys/namei.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 1:40:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (p3E9D0DF0.dip0.t-ipconnect.de [62.157.13.240]) by hub.freebsd.org (Postfix) with ESMTP id 97C3115461 for ; Tue, 11 Jan 2000 01:40:17 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id BAA45844 for ; Tue, 11 Jan 2000 01:56:45 +0100 (CET) (envelope-from cc@devcon.net) Date: Tue, 11 Jan 2000 01:56:44 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: current@freebsd.org Subject: reported system freezes... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG so, ok, i've tried several checkout dates for sys and tested the compiled kernels. as i cannot reproduce this freeze thing, this is quite vague, but kernels up to 04 Jan 2000 worked fine, those from 05 Jan 2000 up to now don't. maybe, this is useful information. -- Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 1:41:19 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 28F8314E75; Tue, 11 Jan 2000 01:41:18 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 179C71CD817; Tue, 11 Jan 2000 01:41:18 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 11 Jan 2000 01:41:18 -0800 (PST) From: Kris Kennaway To: nnd@mail.nsk.ru Cc: current@freebsd.org Subject: Re: Can't "kldload" modules due to "symbol NDFREE undefined" In-Reply-To: <200001110934.PAA00477@wint.itfs.nsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000 nnd@mail.nsk.ru wrote: > At least from the January 9 after 'cvsup', > 'make buildworld','make installworld', 'make & install kernel' > I can't 'kldload linux'. 'Kldload" says: Probably one of these is not up to date, or is out of sync. I had this problem yesterday when my modules were out of date. Please double-check to make sure.. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 1:46:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 89BF415418; Tue, 11 Jan 2000 01:46:27 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id BAA20238; Tue, 11 Jan 2000 01:44:57 -0800 (PST) Message-Id: <200001110944.BAA20238@implode.root.com> To: Brian Fundakowski Feldman Cc: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: Crash from ^T during heavy paging In-reply-to: Your message of "Tue, 11 Jan 2000 03:34:43 EST." From: David Greenman Reply-To: dg@root.com Date: Tue, 11 Jan 2000 01:44:56 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Mon, 10 Jan 2000, Stephen McKay wrote: > >> The problem is that calcru() thinks that P_INMEM means that the proc >> structure is fully and accurately populated. But P_INMEM is one of the >> first flags set. >> >> So, calcru() and possibly some other places, are looking at a struct proc >> before it's all there. What's the "proper" way to do it? > >It should really be one of the _last_ flags set, if it's to mean anything. >I don't know how to explain the prevalance of race conditions in the old >code, except to say it probably has to do with not planning ahead. >Certainly it's not acceptable to create new race conditions now (even if >it can happen by accident). > >So, here's something to defer P_INMEM til the end, when the process is >really "ready": > >--- sys/kern/kern_fork.c Tue Dec 7 22:11:35 1999 >+++ /tmp/kern_fork.c Tue Jan 11 03:32:44 2000 >@@ -351,7 +351,7 @@ > * Increase reference counts on shared objects. > * The p_stats and p_sigacts substructs are set in vm_fork. > */ >- p2->p_flag = P_INMEM; >+ p2->p_flag = 0; > if (p1->p_flag & P_PROFIL) > startprofclock(p2); > MALLOC(p2->p_cred, struct pcred *, sizeof(struct pcred), >@@ -499,6 +499,7 @@ > microtime(&(p2->p_stats->p_start)); > p2->p_acflag = AFORK; > (void) splhigh(); >+ p2->p_flag |= P_INMEM; > p2->p_stat = SRUN; > setrunqueue(p2); > (void) spl0(); It shouldn't be necessary to set the flag inside of splhigh. If you move it up a line I think you'll have a winner. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 1:54:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from infoteka.nsk.ru (infoteka.nsk.ru [212.20.32.40]) by hub.freebsd.org (Postfix) with SMTP id 61E5915453 for ; Tue, 11 Jan 2000 01:54:17 -0800 (PST) (envelope-from nnd@infoteka.nsk.ru) Received: (qmail 27751 invoked by uid 0); 11 Jan 2000 09:54:15 -0000 Message-ID: <20000111155414.45844@mail.nsk.ru> Date: Tue, 11 Jan 2000 15:54:14 +0600 From: Charlie & To: current@freebsd.org Subject: Re: Can't "kldload" modules due to "symbol NDFREE undefined" References: <200001110934.PAA00477@wint.itfs.nsk.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Kris Kennaway on Tue, Jan 11, 2000 at 01:41:18AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 01:41:18AM -0800, Kris Kennaway wrote: > On Tue, 11 Jan 2000 nnd@mail.nsk.ru wrote: > > > At least from the January 9 after 'cvsup', > > 'make buildworld','make installworld', 'make & install kernel' > > I can't 'kldload linux'. 'Kldload" says: > > Probably one of these is not up to date, or is out of sync. I had this > problem yesterday when my modules were out of date. Please double-check to > make sure.. And what (apart from listed actions) is the best method to establish "syncronization" of the kernel, modules and kldload ? N.Dudorov P.S. I've manually 'cmp -l' linux.ko from /modules and /usr/obj/.../sys/modules/linux directories prior to sending my message ;-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 2:13:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id CE18C15437 for ; Tue, 11 Jan 2000 02:13:29 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id VAA27152; Tue, 11 Jan 2000 21:12:00 +1100 Date: Tue, 11 Jan 2000 21:11:57 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "Louis A. Mamakos" Cc: Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: Buildworld fails In-Reply-To: <200001110414.XAA46411@whizzo.transsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Louis A. Mamakos wrote: > > As Pascal Hofstee wrote: > > > With CURRENT-sources updates within an hour ago ... buildworld fails: > > > > Revert to version 1.26 of gnu/lib/libdialog/Makefile. someone broke it when > > he decided to install all the files in TESTS/... > > > > Don't forget to revert to 1.34 of lib/libncurses/Makefile for the same > > reason. Grrr. > > Yeah, this happened to me too. It seems that mtree doesn't get run > to populate the bootstrap build environment. > > Of course, installing documentation and examples into the build environment > probably is a waste of time and disk space anyway.. The build environment sets NOINFO and NOMAN. This is supposed to prevent building and installation of documentation. However, some html docmentation is now installed twice (except the install fails). The beforeinstall rule is abused to install headers, and it now installs html files and (in some cases) examples in some critical Makefiles (libdialog, libncurses, maybe more). Later in the build, the beforeinstall rule is run again as part of the install rule. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 2:35:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by hub.freebsd.org (Postfix) with ESMTP id 4828615191; Tue, 11 Jan 2000 02:35:36 -0800 (PST) (envelope-from trond@ramstind.gtf.ol.no) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id LAA75580; Tue, 11 Jan 2000 11:35:27 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Date: Tue, 11 Jan 2000 11:35:27 +0100 (CET) From: Trond Endrestol To: FreeBSD stable , FreeBSD current Subject: Making sure /var/tmp/vi.recover exists during reboot Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This is something you might want to put in /etc/rc in both -stable and -current. Scenario: /tmp is MFS, /var/tmp, /usr/tmp and /usr/local/tmp are symlinks to /tmp, and hence /var/tmp/vi.recover does not exist at reboot and causes «cosmetic interference» on the console during reboot. Solution: Add these lines after the «# Recover vi editor files.» line (about line #345): if [ ! -d /var/tmp/vi.recover ]; then mkdir /var/tmp/vi.recover; chmod 1777 /var/tmp/vi.recover; chown root:wheel /var/tmp/vi.recover; fi ---------------------------------------------------------------------- Trond Endrestøl | trond@gtf.ol.no Merkantilvegen 59HB7, | trond@ramstind.gtf.ol.no N-2815 GJØVIK, NORWAY |+47 61139424 || +47 63874242 Patron of The Art of Computer Programming| FreeBSD 3.3 & Pine 4.10 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 3: 6: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21]) by hub.freebsd.org (Postfix) with ESMTP id 65F7515366 for ; Tue, 11 Jan 2000 03:05:59 -0800 (PST) (envelope-from marc.solsona@nokia.com) Received: from mgw-i1.ntc.nokia.com (mgw-i1.ntc.nokia.com [131.228.118.60]) by mgw-x1.nokia.com (8.9.3/8.9.3/o) with ESMTP id NAA15909 for ; Tue, 11 Jan 2000 13:05:51 +0200 (EET) Received: from loki.research.nokia.com (loki.research.nokia.com [172.21.33.76]) by mgw-i1.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id NAA12047 for ; Tue, 11 Jan 2000 13:05:46 +0200 (EET) Received: from possu.research.nokia.com (possu.research.nokia.com [172.21.33.80]) by loki.research.nokia.com (8.9.3/8.9.3) with ESMTP id NAA21255 for ; Tue, 11 Jan 2000 13:02:56 +0200 (EET) Received: from nokia.com (playa.research.nokia.com [172.21.41.32]) by possu.research.nokia.com (8.9.1/8.9.1) with ESMTP id NAA17410 for ; Tue, 11 Jan 2000 13:02:55 +0200 (EET) Message-ID: <387B10D5.37E13989@nokia.com> Date: Tue, 11 Jan 2000 13:15:33 +0200 From: Marc Solsona X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: wdm not responding Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using wdm o the 3-stable branch. Since I migrated to current wdm is not reponding to keyboard. Although when I start it manually it does. Any ideas? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 3:13:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from email.spcgroup.nl (email.spcgroup.nl [212.206.124.3]) by hub.freebsd.org (Postfix) with ESMTP id 6BCB515402 for ; Tue, 11 Jan 2000 03:13:45 -0800 (PST) (envelope-from e.mons@spcgroup.nl) Received: from spcgroup.nl (fw.spcgroup.nl [212.206.124.2]) by email.spcgroup.nl (8.9.3/8.9.3) with ESMTP id NAA05470 for ; Tue, 11 Jan 2000 13:23:34 +0100 Message-ID: <387B105E.FF4E789C@spcgroup.nl> Date: Tue, 11 Jan 2000 12:13:34 +0100 From: Edwin Mons X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: wdm not responding References: <387B10D5.37E13989@nokia.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Solsona wrote: > > I'm using wdm o the 3-stable branch. Since I migrated to current wdm is > > not reponding to keyboard. Although when I start it manually it does. > Any ideas? > > Thanks > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I noticed this, too, with xdm. Putting a 'sleep 4' before starting xdm (and thus starting it after getty ran and the system was ready to use) fixed it for me.. Don't know the real cause, though. Regards, Edwin Mons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 3:17: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 113E8153BD for ; Tue, 11 Jan 2000 03:17:02 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id DAA09813; Tue, 11 Jan 2000 03:40:17 -0800 (PST) Date: Tue, 11 Jan 2000 03:40:16 -0800 From: Alfred Perlstein To: Christian Carstensen Cc: current@FreeBSD.ORG Subject: Re: reported system freezes... Message-ID: <20000111034016.L9397@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cc@devcon.net on Tue, Jan 11, 2000 at 01:56:44AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Christian Carstensen [000111 02:03] wrote: > > so, ok, > > i've tried several checkout dates for sys and tested the compiled kernels. > as i cannot reproduce this freeze thing, this is quite vague, but kernels > up to 04 Jan 2000 worked fine, those from 05 Jan 2000 up to now don't. > > maybe, this is useful information. not without your configuration... are you running vinum or softupdates? Kirk just fixed softupdates and I committed a patch to vinum just last night. If you're using vinum don't forget to update your modules, a kernel function was changed that causes it to panic unless your kernel and modules are exactly in sync. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 3:18:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id DF4F215366; Tue, 11 Jan 2000 03:18:51 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id WAA30653; Tue, 11 Jan 2000 22:18:48 +1100 Date: Tue, 11 Jan 2000 22:18:44 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Brian Fundakowski Feldman Cc: Stephen McKay , freebsd-current@FreeBSD.ORG, dt@FreeBSD.ORG Subject: Re: Crash from ^T during heavy paging In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Brian Fundakowski Feldman wrote: > On Mon, 10 Jan 2000, Stephen McKay wrote: > > > The problem is that calcru() thinks that P_INMEM means that the proc > > structure is fully and accurately populated. But P_INMEM is one of the > > first flags set. > > > > So, calcru() and possibly some other places, are looking at a struct proc > > before it's all there. What's the "proper" way to do it? > > It should really be one of the _last_ flags set, if it's to mean anything. > I don't know how to explain the prevalance of race conditions in the old > code, except to say it probably has to do with not planning ahead. > [patch deleted] I broke calcru() with the monotonicity fixes (kern_resource.c rev.1.45 (1999/03/13). Accessing p->p_stats at interrupt time is only valid if p == curproc. Fix: move the new monotonicity fields from struct pstats to struct proc. I only put them in struct pstats because they logically go with some fields in struct rusage. P_INMEM is probably not supposed to work in interrupt contexts. Checking it in ttyinfo() is a wrong fix for the bug in calcru(). It was committed in tty.c rev.1.119 (1999/05/22). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 3:19:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 6ABAF1541A for ; Tue, 11 Jan 2000 03:19:40 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id DAA09844; Tue, 11 Jan 2000 03:42:25 -0800 (PST) Date: Tue, 11 Jan 2000 03:42:25 -0800 From: Alfred Perlstein To: Edwin Mons Cc: freebsd-current@FreeBSD.ORG Subject: Re: wdm not responding Message-ID: <20000111034224.M9397@fw.wintelcom.net> References: <387B10D5.37E13989@nokia.com> <387B105E.FF4E789C@spcgroup.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <387B105E.FF4E789C@spcgroup.nl>; from e.mons@spcgroup.nl on Tue, Jan 11, 2000 at 12:13:34PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Edwin Mons [000111 03:37] wrote: > > Marc Solsona wrote: > > > > I'm using wdm o the 3-stable branch. Since I migrated to current wdm is > > > > not reponding to keyboard. Although when I start it manually it does. > > Any ideas? > > > > Thanks > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > I noticed this, too, with xdm. Putting a 'sleep 4' before starting xdm > (and thus starting it after getty ran and the system was ready to use) > fixed it for me.. Don't know the real cause, though. You ought to use the example in /etc/ttys to start it up. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 3:22:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 405F915343; Tue, 11 Jan 2000 03:22:45 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 127zNa-0002Lo-00; Tue, 11 Jan 2000 13:22:26 +0200 From: Sheldon Hearn To: Trond Endrestol Cc: FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-reply-to: Your message of "Tue, 11 Jan 2000 11:35:27 +0100." Date: Tue, 11 Jan 2000 13:22:26 +0200 Message-ID: <9039.947589746@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000 11:35:27 +0100, Trond Endrestol wrote: > This is something you might want to put in /etc/rc in both -stable > and -current. > > Scenario: > > /tmp is MFS, > /var/tmp, /usr/tmp and /usr/local/tmp are symlinks to /tmp, Not until someone can explain how making /var/tmp a symlink to /tmp is sensible, given that /var/tmp is documented as containing "temporary files that are kept between system reboots" (see hier(7)). So basically, no. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 3:33: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 16F1C15050 for ; Tue, 11 Jan 2000 03:33:01 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id D630E1CA0; Tue, 11 Jan 2000 19:32:58 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Charlie & Cc: current@freebsd.org Subject: Re: Can't "kldload" modules due to "symbol NDFREE undefined" In-Reply-To: Message from Charlie & of "Tue, 11 Jan 2000 15:54:14 +0600." <20000111155414.45844@mail.nsk.ru> Date: Tue, 11 Jan 2000 19:32:58 +0800 From: Peter Wemm Message-Id: <20000111113258.D630E1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charlie & wrote: > On Tue, Jan 11, 2000 at 01:41:18AM -0800, Kris Kennaway wrote: > > On Tue, 11 Jan 2000 nnd@mail.nsk.ru wrote: > > > > > At least from the January 9 after 'cvsup', > > > 'make buildworld','make installworld', 'make & install kernel' > > > I can't 'kldload linux'. 'Kldload" says: > > > > Probably one of these is not up to date, or is out of sync. I had this > > problem yesterday when my modules were out of date. Please double-check to > > make sure.. > > And what (apart from listed actions) is the best > method to establish "syncronization" of the kernel, modules and > kldload ? IMHO, add 'options COMPAT_LINUX' to your kernel and don't use the module if you are going to be regularly compiling the kernel and modules seperately.. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 3:38:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 1177D14F19 for ; Tue, 11 Jan 2000 03:38:41 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup1-20.iptelecom.net.ua [212.9.226.20]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA00475 for ; Tue, 11 Jan 2000 13:42:12 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id NAA30916 for ; Tue, 11 Jan 2000 13:37:40 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <387B1603.E353CD09@altavista.net> Date: Tue, 11 Jan 2000 13:37:39 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: C++ exceptions doesn't work in shared libraries Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, It seems than long-standing problem (see PR dated May '97: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=3441) with C++ exceptions in shared libraries is still here. It affects both -current and -stable branches and prevents some modern software (Mico for example) from functioning properly. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 4:10:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id EEB3514D9E for ; Tue, 11 Jan 2000 04:10:12 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 7AE251DA7; Tue, 11 Jan 2000 13:10:10 +0100 (CET) Date: Tue, 11 Jan 2000 13:10:10 +0100 From: "Dave J. Boers" To: freebsd-current@freebsd.org Subject: Still system hangs, but different Message-ID: <20000111131010.A317@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, After cvsup last night: FreeBSD relativity.student.utwente.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Ja n 11 04:48:17 CET 2000 root@relativity.student.utwente.nl:/usr/src/sys/compi le/RELATIVITY4 i386 which includes the latest softupdates changes, I still experience random system hangs, however not the same as I used to have. While the hang occured there was X11 running and mutt was in the middle of saving its mailfile (it was at 99%) and stopped responding. I killed mutt (which worked!) and reran it, closed it, ran tin and then everything hung completely. Strangely enough X continued working (things like mouse pointer, moving windows etc) but I couldn't open or close xterms. Logging in by telnet or on serial console was also impossible. After a few minutes I decided I had to do a hard reset. So I guess some problems still remain. Regards, Dave Boers. P.S. FWIW: I'm _not_ running vinum, I _am_ running softupdates and I use the ahc SCSI driver and ATA driver. -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 4:21:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id D922F1543A for ; Tue, 11 Jan 2000 04:21:26 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id SAA00652; Tue, 11 Jan 2000 18:21:22 +0600 (NOVT) (envelope-from nnd) Date: Tue, 11 Jan 2000 18:21:22 +0600 (NOVT) Message-Id: <200001111221.SAA00652@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: Can't "kldload" modules due to "symbol NDFREE undefined" In-Reply-To: <20000111113258.D630E1CA0@overcee.netplex.com.au> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000111113258.D630E1CA0@overcee.netplex.com.au> Peter Wemm wrote: > Charlie & wrote: >> On Tue, Jan 11, 2000 at 01:41:18AM -0800, Kris Kennaway wrote: >> > On Tue, 11 Jan 2000 nnd@mail.nsk.ru wrote: >> > >> > > At least from the January 9 after 'cvsup', >> > > 'make buildworld','make installworld', 'make & install kernel' >> > > I can't 'kldload linux'. 'Kldload" says: >> > >> > Probably one of these is not up to date, or is out of sync. I had this >> > problem yesterday when my modules were out of date. Please double-check to >> > make sure.. >> >> And what (apart from listed actions) is the best >> method to establish "syncronization" of the kernel, modules and >> kldload ? > > IMHO, add 'options COMPAT_LINUX' to your kernel and don't use the module if > you are going to be regularly compiling the kernel and modules seperately.. Thanks a lot for your advice(s) but on my CURRENT box I compile kernel and modules seperately only in thouse (rare enough) cases when one of them is broken. So, the problem is not in "out of sync" kernel and modules. And besides of "linux.ko" the same problem (i.e. kldload errror) have all modules with NDFREE reference - ccd.ko, cd9660.ko, coda.ko, ibcs2.ko, ibcs2_coff.ko, msdos.ko, nfs.ko, ntfs.ko, null.ko, svr4.ko, umap.ko, union.ko, vinum.ko, vn.ko. Can somebody with CURRENT system test 'kldload' some of the above modules on his machine and post the results ? N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 4:22:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (p3E9EBEB9.dip0.t-ipconnect.de [62.158.190.185]) by hub.freebsd.org (Postfix) with ESMTP id C9C2B15502 for ; Tue, 11 Jan 2000 04:22:46 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id OAA61965; Tue, 11 Jan 2000 14:25:38 +0100 (CET) (envelope-from cc@devcon.net) Date: Tue, 11 Jan 2000 14:25:37 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: reported system freezes... In-Reply-To: <20000111034016.L9397@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Alfred Perlstein wrote: > are you running vinum or softupdates? Kirk just fixed softupdates and > I committed a patch to vinum just last night. yes, i am running vinum and softupdates. i've checked out the recent sources some minutes ago, and making a new world. this will take an hour. i'll tell you, if that's working. -- Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 4:29: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id C56A915532; Tue, 11 Jan 2000 04:28:52 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 11 Jan 2000 12:28:51 +0000 (GMT) Date: Tue, 11 Jan 2000 12:28:50 +0000 From: David Malone To: David O'Brien Cc: current@FreeBSD.ORG Subject: Re: Lint still broken in -current (due to cpp). Message-ID: <20000111122850.A29700@walton.maths.tcd.ie> References: <200001071122.aa81066@salmon.maths.tcd.ie> <13429.947244567@axl.noc.iafrica.com> <20000107092847.A97211@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000107092847.A97211@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Fri, Jan 07, 2000 at 09:28:47AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 07, 2000 at 09:28:47AM -0800, David O'Brien wrote: > On Fri, Jan 07, 2000 at 01:29:27PM +0200, Sheldon Hearn wrote: > > I think lint(1) might work with this given the following small patch. > > I agree that lint might should continue to use /usr/libexec/cpp rather > than switch to /usr/bin/cpp. But not knowing anything about our lint, I > can't really say. NetBSD seem to have moved to using "/usr/bin/cc -E -U__GNUC__". OpenBSD seems to be using "/usr/libexec/cpp -U__GNUC__". FreeBSD's lint came from NetBSD, as far as I can tell. I produce diffs to make FreeBSD's lint more like NetBSD's if you like. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 4:44:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id B520C14F75 for ; Tue, 11 Jan 2000 04:44:50 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 9CB211CA0; Tue, 11 Jan 2000 20:44:48 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: nnd@mail.nsk.ru Cc: current@freebsd.org Subject: Re: Can't "kldload" modules due to "symbol NDFREE undefined" In-Reply-To: Message from nnd@mail.nsk.ru of "Tue, 11 Jan 2000 18:21:22 +0600." <200001111221.SAA00652@wint.itfs.nsk.su> Date: Tue, 11 Jan 2000 20:44:48 +0800 From: Peter Wemm Message-Id: <20000111124448.9CB211CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nnd@mail.nsk.ru wrote: > In <20000111113258.D630E1CA0@overcee.netplex.com.au> Peter Wemm wrote: > > Charlie & wrote: > >> On Tue, Jan 11, 2000 at 01:41:18AM -0800, Kris Kennaway wrote: > >> > On Tue, 11 Jan 2000 nnd@mail.nsk.ru wrote: > >> > > >> > > At least from the January 9 after 'cvsup', > >> > > 'make buildworld','make installworld', 'make & install kernel' > >> > > I can't 'kldload linux'. 'Kldload" says: > >> > > >> > Probably one of these is not up to date, or is out of sync. I had this > >> > problem yesterday when my modules were out of date. Please double-check to > >> > make sure.. > >> > >> And what (apart from listed actions) is the best > >> method to establish "syncronization" of the kernel, modules and > >> kldload ? > > > > IMHO, add 'options COMPAT_LINUX' to your kernel and don't use the module if > > you are going to be regularly compiling the kernel and modules seperately.. > > Thanks a lot for your advice(s) but on my CURRENT > box I compile kernel and modules seperately only in thouse > (rare enough) cases when one of them is broken. > > So, the problem is not in "out of sync" kernel > and modules. And besides of "linux.ko" the same problem > (i.e. kldload errror) have all modules with NDFREE reference - > ccd.ko, cd9660.ko, coda.ko, ibcs2.ko, ibcs2_coff.ko, msdos.ko, > nfs.ko, ntfs.ko, null.ko, svr4.ko, umap.ko, union.ko, vinum.ko, vn.ko. > > Can somebody with CURRENT system test 'kldload' some > of the above modules on his machine and post the results ? First of all, can you try this please? > nm /kernel | grep NDFREE c0186b64 T NDFREE This is to check that NDFREE is actually defined in your /kernel.. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 5: 3:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by hub.freebsd.org (Postfix) with ESMTP id E089C1547A for ; Tue, 11 Jan 2000 05:03:44 -0800 (PST) (envelope-from marc.solsona@nokia.com) Received: from mgw-i2.ntc.nokia.com (mgw-i2.ntc.nokia.com [131.228.118.61]) by mgw-x2.nokia.com (8.9.3/8.9.3/o) with ESMTP id PAA24734 for ; Tue, 11 Jan 2000 15:03:37 +0200 (EET) Received: from loki.research.nokia.com (loki.research.nokia.com [172.21.33.76]) by mgw-i2.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id PAA25208 for ; Tue, 11 Jan 2000 15:03:32 +0200 (EET) Received: from possu.research.nokia.com (possu.research.nokia.com [172.21.33.80]) by loki.research.nokia.com (8.9.3/8.9.3) with ESMTP id PAA26121 for ; Tue, 11 Jan 2000 15:03:31 +0200 (EET) Received: from nokia.com (playa.research.nokia.com [172.21.41.32]) by possu.research.nokia.com (8.9.1/8.9.1) with ESMTP id PAA04675 for ; Tue, 11 Jan 2000 15:03:30 +0200 (EET) Message-ID: <387B2D27.F23FCF49@nokia.com> Date: Tue, 11 Jan 2000 15:16:23 +0200 From: Marc Solsona X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: wdm not responding References: <387B10D5.37E13989_nokia.com@ns.sol.net> <20000111034224.M9397_fw.wintelcom.net@ns.sol.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Both solutions seem to work with xdm, but not with wdm. It's not a big trauma but may be I should contact the wdm mantainer. Marc Alfred Perlstein wrote: * Edwin Mons [000111 03:37] wrote: > > > > Marc Solsona wrote: > > > > > > I'm using wdm o the 3-stable branch. Since I migrated to current wdm is > > > > > > not reponding to keyboard. Although when I start it manually it does. > > > Any ideas? > > > > > > Thanks > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > I noticed this, too, with xdm. Putting a 'sleep 4' before starting xdm > > (and thus starting it after getty ran and the system was ready to use) > > fixed it for me.. Don't know the real cause, though. > > You ought to use the example in /etc/ttys to start it up. > > -Alfred > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 5:14:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from infoteka.nsk.ru (infoteka.nsk.ru [212.20.32.40]) by hub.freebsd.org (Postfix) with SMTP id 2EB101543F for ; Tue, 11 Jan 2000 05:14:49 -0800 (PST) (envelope-from nnd@infoteka.nsk.ru) Received: (qmail 5363 invoked by uid 0); 11 Jan 2000 13:14:47 -0000 Message-ID: <20000111191447.53354@mail.nsk.ru> Date: Tue, 11 Jan 2000 19:14:47 +0600 From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: Can't "kldload" modules due to "symbol NDFREE undefined" References: <200001111221.SAA00652@wint.itfs.nsk.su> <20000111124448.9CB211CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e In-Reply-To: <20000111124448.9CB211CA0@overcee.netplex.com.au>; from Peter Wemm on Tue, Jan 11, 2000 at 08:44:48PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 08:44:48PM +0800, Peter Wemm wrote: > > Can somebody with CURRENT system test 'kldload' some > > of the above modules on his machine and post the results ? > > First of all, can you try this please? > > > nm /kernel | grep NDFREE > c0186b64 T NDFREE > > This is to check that NDFREE is actually defined in your /kernel.. nm -o /kernel* | grep NDFREE /kernel:c0176000 T NDFREE /kernel.UP:c0173f3c T NDFREE /kernel.old:c0175fc0 T NDFREE ls -l /kernel* -r-xr-xr-x 1 root wheel 1829054 11 ÑÎ× 13:20 /kernel -rwxr-xr-x 1 root wheel 2552869 5 ÑÎ× 20:36 /kernel.GENERIC -r-xr-xr-x 1 root wheel 1771990 11 ÑÎ× 13:22 /kernel.UP -r-xr-xr-x 1 root wheel 1828576 10 ÑÎ× 15:25 /kernel.old 'kernel.UP' is nonSMP-kernel and 'kernel' -SMP one otherwise their are the same. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 5:26:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 38E5E14C1C for ; Tue, 11 Jan 2000 05:26:09 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id TAA00275; Tue, 11 Jan 2000 19:26:06 +0600 (NOVT) (envelope-from nnd) Date: Tue, 11 Jan 2000 19:26:06 +0600 (NOVT) Message-Id: <200001111326.TAA00275@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: Can't "kldload" modules due to "symbol NDFREE undefined" In-Reply-To: <20000111191447.53354@mail.nsk.ru> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000111191447.53354@mail.nsk.ru> nnd@mail.nsk.ru wrote: In the meantime I make another test - reboot the system and on the loader prompt say: disk2s1a> load modules/linux.ko disk2s1a> boot and the system boots up successfully and kldstat shows 'linux.ko' module and Linux version of the Adobe's Acrobat Reader works ! So the problem is in the kernel's elf_loader ? N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 5:31:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 501C214A18 for ; Tue, 11 Jan 2000 05:31:07 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id OAA70953; Tue, 11 Jan 2000 14:30:50 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: "Cameron Grant" Cc: Subject: Re: newpcm References: <000901bf5b4f$0e1ba520$0304020a@rings> From: Dag-Erling Smorgrav Date: 11 Jan 2000 14:30:49 +0100 In-Reply-To: "Cameron Grant"'s message of "Mon, 10 Jan 2000 09:42:48 -0000" Message-ID: Lines: 15 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Cameron Grant" writes: > would everyone who currently has an issue outstanding with newpcm please > report it to me in the next few days directly, please, so i can get an idea > of what needs work before release. i need as much detail as possible. My SB128 still doesn't attach: root@des ~# pciconf -l | grep none none0@pci0:10:0: class=0x040100 card=0x13711274 chip=0x13713274 rev=0x06 hdr=0x00 root@des ~# grep 1371 /var/run/dmesg.boot pci0: unknown card (vendor=0x3274, dev=0x1371) at 10.0 irq 5 DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 6: 8:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by hub.freebsd.org (Postfix) with ESMTP id 8FA0414F64 for ; Tue, 11 Jan 2000 06:08:25 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: from extremis.demon.co.uk ([194.222.242.30]) by anchor-post-32.mail.demon.net with smtp (Exim 2.12 #1) id 1281yB-000HTa-0W for freebsd-current@FreeBSD.ORG; Tue, 11 Jan 2000 14:08:24 +0000 Received: (qmail 1909 invoked by uid 1010); 11 Jan 2000 13:21:50 -0000 Date: Tue, 11 Jan 2000 13:21:50 +0000 From: George Cox To: Andreas Klemm Cc: freebsd-current@FreeBSD.ORG Subject: Re: -pipe switch in kernel compilation Message-ID: <20000111132150.A1314@extremis.demon.co.uk> References: <20000110165543.A5720@extremis.demon.co.uk> <20000111073939.A31293@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <20000111073939.A31293@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Tue, Jan 11, 2000 at 07:39:40AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11/01 07:39, Andreas Klemm wrote: > Where 4 MB isn't sufficient anymore with a GENERIC kernel. You need at least > 6 MB or so to boot, then compile a custom kernel and then, if you are lucky, > can perhaps run with 4 MB. Here are the two constituent process of a compilation spotted earlier today: PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 1897 root 31 0 4224K 4096K STOP 1 0:04 13.32% 7.91% cc1 1898 root -6 0 1616K 1216K STOP 0 0:00 0.00% 0.00% as So it looks like a round 6M is required for a '-pipe' enabled compilation. Thank heavens for lower memory prices! :-) > But that information is about 1-2 years old, don't know, if we perhaps > already need 6-8 MB nowadays... Though it's zillions better than M$ crap. Absolutely. My computer is a free software-only zone. :-) best; gjvc -- [gjvc] 4.4BSD 4.ever! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 6:41:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id C662D15000 for ; Tue, 11 Jan 2000 06:41:35 -0800 (PST) (envelope-from eculp@EnContacto.Net) Received: from EnContacto.Net (local-27.local.net [192.168.1.27]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id GAA61903; Tue, 11 Jan 2000 06:41:29 -0800 (PST) (envelope-from eculp@EnContacto.Net) Message-ID: <387B4119.39E60169@EnContacto.Net> Date: Tue, 11 Jan 2000 06:41:29 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Cameron Grant Cc: freebsd-current@FreeBSD.ORG Subject: Re: newpcm References: <000901bf5b4f$0e1ba520$0304020a@rings> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Cameron Grant" writes: > would everyone who currently has an issue outstanding with newpcm please > report it to me in the next few days directly, please, so i can get an idea > of what needs work before release. i need as much detail as possible. My ess1869, current as of Sunday, still repeats the end of wav and au files 0-3 times and I get no sound from amp playing a mp3. It acts as though the volume were down, and cpu usage drops off to nothing and it never finishes. It just blocks sound until it is killed. Mpg movies have sound with no repeating using mtvp. These conditions seem to change some everything there is a change in buffering. This is especially noticeable if you enable sound in kde. Is anyone else seeing this with an ess186? ? Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 7:20: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 56BD4154D4 for ; Tue, 11 Jan 2000 07:19:48 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 9C6DD1CD1; Tue, 11 Jan 2000 23:19:45 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Dag-Erling Smorgrav Cc: "Cameron Grant" , freebsd-current@FreeBSD.ORG Subject: Re: newpcm In-Reply-To: Message from Dag-Erling Smorgrav of "11 Jan 2000 14:30:49 +0100." Date: Tue, 11 Jan 2000 23:19:45 +0800 From: Peter Wemm Message-Id: <20000111151945.9C6DD1CD1@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > "Cameron Grant" writes: > > would everyone who currently has an issue outstanding with newpcm please > > report it to me in the next few days directly, please, so i can get an idea > > of what needs work before release. i need as much detail as possible. > > My SB128 still doesn't attach: > > root@des ~# pciconf -l | grep none > none0@pci0:10:0: class=0x040100 card=0x13711274 chip=0x13713274 rev=0x 06 hdr=0x00 > root@des ~# grep 1371 /var/run/dmesg.boot > pci0: unknown card (vendor=0x3274, dev=0x1371) at 10.0 irq 5 Hmm.. different vendor id? peter@overcee[11:16pm]~src/sys/dev/sound/pci-383> grep ES1371_PCI_ID * es137x.c:#define ES1371_PCI_ID 0x13711274 es137x.c: } else if (pci_get_devid(dev) == ES1371_PCI_ID) { es137x.c: if (pci_get_devid(dev) == ES1371_PCI_ID) { Does the following hack work? Index: es137x.c =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/pci/es137x.c,v retrieving revision 1.10 diff -u -r1.10 es137x.c --- es137x.c 2000/01/05 02:03:55 1.10 +++ es137x.c 2000/01/11 15:18:52 @@ -70,6 +70,7 @@ /* PCI IDs of supported chips */ #define ES1370_PCI_ID 0x50001274 #define ES1371_PCI_ID 0x13711274 +#define ES1371_PCI_ID2 0x13713274 /* device private data */ struct es_info; @@ -703,7 +704,8 @@ if (pci_get_devid(dev) == ES1370_PCI_ID) { device_set_desc(dev, "AudioPCI ES1370"); return 0; - } else if (pci_get_devid(dev) == ES1371_PCI_ID) { + } else if (pci_get_devid(dev) == ES1371_PCI_ID || + pci_get_devid(dev) == ES1371_PCI_ID2) { device_set_desc(dev, "AudioPCI ES1371"); return 0; } @@ -766,7 +768,8 @@ goto bad; } - if (pci_get_devid(dev) == ES1371_PCI_ID) { + if (pci_get_devid(dev) == ES1371_PCI_ID || + pci_get_devid(dev) == ES1371_PCI_ID2) { if(-1 == es1371_init(es, pci_get_revid(dev))) { device_printf(dev, "unable to initialize the card\n"); goto bad; Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 7:30:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 038FC154DE for ; Tue, 11 Jan 2000 07:30:22 -0800 (PST) (envelope-from daeron@wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id B7CCA2001; Tue, 11 Jan 2000 16:30:17 +0100 (CET) Date: Tue, 11 Jan 2000 16:30:17 +0100 From: Pascal Hofstee To: Alfred Perlstein Cc: freebsd-current@freebsd.org Subject: Re: freezing... Message-ID: <20000111163017.A50249@shadowmere.student.utwente.nl> References: <55926.947513027@critter.freebsd.dk> <200001101945.LAA29394@apollo.backplane.com> <20000110142156.F9397@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000110142156.F9397@fw.wintelcom.net>; from bright@wintelcom.net on Mon, Jan 10, 2000 at 02:21:56PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 02:21:56PM -0800, Alfred Perlstein wrote: > * Matthew Dillon [000110 12:11] wrote: > > I've reproduced the softupdates ftruncate panic and have a core dump > > to play with. > > I don't have a panic, but rather many processes start to get stuck > in "getblk", unfortunatly they all don't stem from a common codepath, > although the first process that wedged appears to have come through > indir_trunc: I just experienced the same thing here on my CURRENT system with Kirk's latest SoftUpdates patches included. i have right now a buildworld stuck in "getblk" on rm ... and a "getblk" hang for Mozilla Tinderbox Build on gcc. The Mozilla Tinderbox build "hang" however seems to be reproducible. I have had two consecutive "hangs" at the same spot: checking for gtk-config... /usr/X11R6/bin/gtk-config which results in a stuck gcc process. I will try to build a kernel with kdb support as soon as my buildworld finishes (if it will finish) and see if I can provide a proper backtrace. -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 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+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 8:28:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 87B84154B0 for ; Tue, 11 Jan 2000 08:28:53 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 96ABC1E31; Tue, 11 Jan 2000 17:28:46 +0100 (CET) Date: Tue, 11 Jan 2000 17:28:46 +0100 From: "Dave J. Boers" To: freebsd-current@freebsd.org Subject: Re: Still system hangs, but different Message-ID: <20000111172846.A361@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000111131010.A317@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000111131010.A317@relativity.student.utwente.nl>; from djb@relativity.student.utwente.nl on Tue, Jan 11, 2000 at 01:10:10PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 01:10:10PM +0100, Dave J. Boers wrote: > So I guess some problems still remain. replying to self here.... I have had the second occurence of the hang and I can provide some more information this time. The thing that hang's is disk i/o. The system continues to work correctly but does not repond to any form of i/o. Therefore, logins, top, kill, incoming mail, whatever requires disk i/o doesn't work. I left the system in this state for 15 minutes, but no error messages, nor kernel panic. The disk drive light was OFF. The only thing that helps is the reset button. Is there something in some sort of infinite loop here? This is an SMP system with the ATA driver and with Kirk's latest softupdates changes included. See my previous mail for more uname -a. Regards, Dave Boers. P.S. I have to go now, but I will try if I can compile a kernel with debugging in it and see if I can make a backtrace (would be my first one ever) this evening. -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 8:36:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 409FD151FA for ; Tue, 11 Jan 2000 08:36:25 -0800 (PST) (envelope-from daeron@wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 1140B1FFA; Tue, 11 Jan 2000 16:30:17 +0100 (CET) Date: Tue, 11 Jan 2000 16:30:17 +0100 From: Pascal Hofstee To: Alfred Perlstein Cc: freebsd-current@freebsd.org Subject: Re: freezing... Message-ID: <20000111163017.A50249@shadowmere.student.utwente.nl> References: <55926.947513027@critter.freebsd.dk> <200001101945.LAA29394@apollo.backplane.com> <20000110142156.F9397@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000110142156.F9397@fw.wintelcom.net>; from bright@wintelcom.net on Mon, Jan 10, 2000 at 02:21:56PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 02:21:56PM -0800, Alfred Perlstein wrote: > * Matthew Dillon [000110 12:11] wrote: > > I've reproduced the softupdates ftruncate panic and have a core dump > > to play with. > > I don't have a panic, but rather many processes start to get stuck > in "getblk", unfortunatly they all don't stem from a common codepath, > although the first process that wedged appears to have come through > indir_trunc: I just experienced the same thing here on my CURRENT system with Kirk's latest SoftUpdates patches included. i have right now a buildworld stuck in "getblk" on rm ... and a "getblk" hang for Mozilla Tinderbox Build on gcc. The Mozilla Tinderbox build "hang" however seems to be reproducible. I have had two consecutive "hangs" at the same spot: checking for gtk-config... /usr/X11R6/bin/gtk-config which results in a stuck gcc process. I will try to build a kernel with kdb support as soon as my buildworld finishes (if it will finish) and see if I can provide a proper backtrace. -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 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+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 8:47:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.102]) by hub.freebsd.org (Postfix) with ESMTP id C86B5154D0 for ; Tue, 11 Jan 2000 08:47:09 -0800 (PST) (envelope-from ortmann@us.ibm.com) Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22]) by e2.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id LAA44430 for ; Tue, 11 Jan 2000 11:46:05 -0500 From: ortmann@us.ibm.com Received: from D51MTA04.pok.ibm.com (d51mta04.pok.ibm.com [9.117.200.32]) by northrelay02.pok.ibm.com (8.8.8m2/NCO v2.06) with SMTP id LAA158460 for ; Tue, 11 Jan 2000 11:47:05 -0500 Received: by D51MTA04.pok.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 85256863.005C33A3 ; Tue, 11 Jan 2000 11:47:05 -0500 X-Lotus-FromDomain: IBMUS To: freebsd-current@freebsd.org Message-ID: <85256863.005C32AA.00@D51MTA04.pok.ibm.com> Date: Tue, 11 Jan 2000 10:46:53 -0600 Subject: an announcement about "Next Generation e-business" Mime-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=YIFuhpU0eW5K6OxO7vMaIrDVl6wGvWR4CzWbJAfcok9SYb0zWmLXpnm0" Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0__=YIFuhpU0eW5K6OxO7vMaIrDVl6wGvWR4CzWbJAfcok9SYb0zWmLXpnm0 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-transfer-encoding: quoted-printable Since this was publically announced I can forward this to the group. I wish the *bsd's were included. (Odd text and formatting below is due to Lotus Notes) -- Daniel Ortmann, IBM Circuit Technology, Rochester, MN 55901-7829 ortmann@vnet.ibm.com or ortmann@us.ibm.com and 507.253.6795 (external) ortmann@rchland.ibm.com and tieline 8.553.6795 (internal) ortmann@isl.net and 507.288.7732 (home) "The answers are so simple, and we all know where to look, but it's easier just to avoid the question." -- Kansas ---------------------- Forwarded by Daniel Ortmann/Rochester/IBM on 01/11/2000 10:42 AM --------------------------- Enterprise Systems Group Samuel J. Palmisano ________________ From: SJP Comm/Somers/IBM @ IBMUS on 01/10/2000 09:14 AM EST To: ESG EMPLOYEES US07 0021, ESG EMPLOYEES US07 0022, ESG EMPLOYEES U= S07 0023, ESG EMPLOYEES US08 0001, ESG EMPLOYEES US08 0002, ESG EMPLO= YEES US09 0001 cc: Subject: Next Generation e-business During the past two-to-three months, we've taken a close look at our se= rver business and what we need to do to get our momentum back. Today we're taking a first step by making a significant announcement to= support Linux and the open source movement and to drive the next genera= tion of the Internet. We intend to be a leader in our industry by: making all of our server platforms Linux ready; engaging closely with the Linux community to help Linux evolve; and= , making IBM technologies available to the Linux and open source communities. This is important news for IBM and for our customers. Here's why: Over four years ago, IBM stated that the Internet was about more than j= ust browsers; it was about a new way of doing business. Since then, IBM's leadership and view of e-business have helped transform the world. We believe we're now on the brink of another important shift in the technology world. The next generation of e-business will see customers= increasingly demand open standards for interoperability across disparat= e platforms. Linux -- a community-developed version of UNIX -- will play= a pivotal role in this. We will embrace Linux on our server platforms --= and help it become one of those open standards as a natural extension of ou= r commitment to e-business and the next generation of the Internet. To spearhead that work effort, we are creating a new organization, head= ed by Dr. Irving Wladawsky-Berger, who has been named vice president, technology and strategy, reporting to me. He was general manager, Inte= rnet Division, Software Group. Irving?s organization will have responsibility for our UNIX software efforts, advanced architectures and technologies, and IBM's next-genera= tion Internet strategy. With IBM as the industry?s e-business leader, there= is no longer the need for a stand-alone Internet Division, since the entir= e company has been focused on Internet themes for several years. As we look to the future, we will continue our aggressive push in the U= NIX marketplace with our industry-leading RS/6000 and NUMA-Q servers, our award-winning AIX operating system and our efforts to evolve AIX in Pro= ject Monterey. We believe the long-term growth of the Internet is about common applica= tion platforms that can harness leading-edge technologies and simplify customers' choices. We believe Linux will develop into that type of co= mmon platform. By getting in early and being a key player in the open sourc= e community, IBM will be a leader in working with the industry to advance= Linux into the future and bring our customers into the next generation = of e-business. This is a long-term play. Significantly, this is not only about server= s. There is a huge opportunity for services. For software. For all of IB= M. So this is one step. You'll be hearing from me in the next few weeks o= n other key initiatives that, in aggregate, will restore our momentum and= help us turn our business around. Stay tuned. (Embedded image moved to file: pic10901.pcx) Senior Vice President & Group Executive Enterprise Systems Group You may read more about IBM's Linux activities, RS/6000, NUMA-Q and AIX= successes at http://w3.ibm.com/servergroup = --0__=YIFuhpU0eW5K6OxO7vMaIrDVl6wGvWR4CzWbJAfcok9SYb0zWmLXpnm0 Content-type: application/octet-stream; name="pic10901.pcx" Content-Disposition: attachment; filename="pic10901.pcx" Content-transfer-encoding: base64 CgUBCAAAAABjADoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAABZAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAADz/9n/zf/G/8P/wv/z/9n/zf/G/8P/wv/z/9n/zf/G/8P/wv/t/8HwoMIA wdHa/83/xv/D/8L/7P/B3cUAwfrZ/83/xv/D/8L/6//B28IArcHkwgDB9Nn/zf/G/8P/wv/q/8Hi wgDBwcH8weyZr9r/zf/G/8P/wv/p/8H0wgDBxcH8wf7B0gDB49r/zf/G/8P/wv/p/6wAt8H4wf/B 9Ke/2v/N/8f/w//C/+j/wdzCAMHswf/B/sHTAMHi2v/N/8f/w//C/+f/wf7CAMHSwf7B/8Hvnq7b /83/x//D/8L/5//B3QCkwfnB/8H5vQDB7Nv/zf/H/8P/wv/m/8H+ogDB1cL/wdwAwcPb/87/x//D /8L/5v/B8wCXwfTB/8H1ogDB+tv/zv/H/8P/wv/m/8HMAMHHwf/B/MHHAMHh3P/O/8f/w//C/+b/ pwDB38H+wdsAwcXc/87/x//E/8L/5f/B88IAwfLB5wCywfzc/87/x//E/8L/5f/B7gCgwfQApMHz 3f/O/8f/xP/C/+X/wesAoLsAwebd/8//x//E/8L/5f/B4cMAwcTe/8//x//E/8L/5f/B78IAosH9 3v/P/8f/xP/C/+X/wd3CAMHi3v/P/8j/xP/C/+X/ncIA3//P/8j/xP/C/+P/wf7B18MA3//P/8j/ xP/C/+L/wf7ByACXwgDB+t7/z//I/8T/wv/i/8HTAKjB6LMAwd3e/8//yP/E/8L/4P/B/sHSAKLB 58H+wdsAqN7/z//I/8T/wv/f/8H+wdIAm8Hhwv/B78IAwe/e/8//x//E/8L/3//BywCgwdvB/cL/ wf2yALzL/8H4weDBysHj1v/L/8b/w//B/93/wf7BzcIAwd/B/cT/wdXCAMH8x//B/cHwwcPDAKDB 9sv/wfvB6MHtwfvO/8f/xP/C/8T/wefBw77CwMHXwc3B5cHr0P/B1cIAwc7G/8H0ngDB3cb/wfbB wcUAssT/wfnB/cT/wfjB2aTCAMHezv/H/8T/wv/D/8HZywCWt8HNwefB8cj/wcfCAMHJwf3G/8H+ wdLCAMH8xP/B7p/GAMHJwf/B/cHotQDBxcH/wfrB1JrGAMHuzv/H/8P/wv/D/8HkxwCkmsgAtMHR wezB/cH/wf3B08IAwc/B+cj/wfedAMHMw//B8cMAwdnBy8MAwdfB463EAMHLm8QAwdq/wwDB3sH4 wf7D/8H7wfrB7cHdwdTBzsHKwcCzrq+ztrnBzMHSwezC/8H/xP/B4sQAwc7B/cP/wfTB6sHOwcLH AJbDALrB5MH8yf/B1sIAwfvB/8H9vcIAoqjDAKunygCawenB/8HwxQCzwcO/s8sAxACowdHB/sL/ xf/B/MHfpgCYwfDI/8H5wejB1cHCmccAssHMweHB78H6xf/B78IAwd3B/8H3ywCoxQCzwerB88H9 w//B65bNAJmmwrG8wcXByMHJwcbBz8Hrwf7C/8j/wf7B8sH9zP/B/JfCAJjHALHBz8HfwefB7cHv we6xAJnB/8H+vMgAs8LrwwCYwePB/cf/wfTBzZjEAJy5wcjB38HywfjB+cj/xP/C/9b/wfy8wgDB 8cL/wfLB0KPNAML/wf7B7cHqwfHB7MHCnbzB7ML/wfqnAMHDwfnM/8H5wfDB8sH2y//G/8P/wf/V /8H8vgCXwe/G/8H9wfTB17XIAMHZyP/B/cX/wfzB+MH+1P/K/8X/wv/B/9T/wf6zAJzB9M3/wfvf /9D/yP/E/8L/0//B9K8AqsH15//T/8r/xf/C/8H/0v/B6sIAncH45//U/8r/xf/C/8H/0P/B/sHs wgCm6P/U/8r/xf/D/8H/0P/B4cIAo8H76P/U/8r/xf/D/8H/zv/B/sHLwgCowfrp/9T/yv/F/8P/ wf/N/8H8vcIAqcH66f/V/8r/xf/D/8H/zP/B96XCAL/B/sb/wfzB/dL/wfvc/87/x//E/8L/y//B 8sMAwcHB/ur/1f/L/8X/w//B/8r/wfHDAMHN6//W/8v/xf/D/8H/yf/B2sMAwdzB/uv/1v/L/8X/ w//B/8f/wfvBzsMAwePs/9b/y//G/8P/wf/F/8H+wc/EAMHe7f/W/8v/xv/D/8H/xP/B+qDEAMHl 7f/X/8v/xv/D/8H/w//B/rjEAMHo7v/X/8v/xv/D/8H/wv/B/pvEAMHo7v/X/8z/xv/D/8H/wv+z wwCywfLv/9f/zP/G/8P/wf/C/8MAwcfw/9j/zP/G/8P/wf/C/8HUAMHh8P/Y/8z/xv/D/8L/8//Z /83/xv/D/8L/8//Z/83/xv/D/8L/DAAAAAEBAQICAgMDAwQEBAUFBQYGBgcHBwgICAkJCQoKCgsL CwwMDA0NDQ4ODg8PDxAQEBERERISEhMTExQUFBUVFRYWFhcXFxgYGBkZGRoaGhsbGxwcHB0dHR4e Hh8fHyAgICEhISIiIiMjIyQkJCUlJSYmJicnJygoKCkpKSoqKisrKywsLC0tLS4uLi8vLzAwMDEx MTIyMjMzMzQ0NDU1NTY2Njc3Nzg4ODk5OTo6Ojs7Ozw8PD09PT4+Pj8/P0BAQEFBQUJCQkNDQ0RE REVFRUZGRkdHR0hISElJSUpKSktLS0xMTE1NTU5OTk9PT1BQUFFRUVJSUlNTU1RUVFVVVVZWVldX V1hYWFlZWVpaWltbW1xcXF1dXV5eXl9fX2BgYGFhYWJiYmNjY2RkZGVlZWZmZmdnZ2hoaGlpaWpq amtra2xsbG1tbW5ubm9vb3BwcHFxcXJycnNzc3R0dHV1dXZ2dnd3d3h4eHl5eXp6ent7e3x8fH19 fX5+fn9/f4CAgIGBgYKCgoODg4SEhIWFhYaGhoeHh4iIiImJiYqKiouLi4yMjI2NjY6Ojo+Pj5CQ kJGRkZKSkpOTk5SUlJWVlZaWlpeXl5iYmJmZmZqampubm5ycnJ2dnZ6enp+fn6CgoKGhoaKioqOj o6SkpKWlpaampqenp6ioqKmpqaqqqqurq6ysrK2tra6urq+vr7CwsLGxsbKysrOzs7S0tLW1tba2 tre3t7i4uLm5ubq6uru7u7y8vL29vb6+vr+/v8DAwMHBwcLCwsPDw8TExMXFxcbGxsfHx8jIyMnJ ycrKysvLy8zMzM3Nzc7Ozs/Pz9DQ0NHR0dLS0tPT09TU1NXV1dbW1tfX19jY2NnZ2dra2tvb29zc 3N3d3d7e3t/f3+Dg4OHh4eLi4uPj4+Tk5OXl5ebm5ufn5+jo6Onp6erq6uvr6+zs7O3t7e7u7u/v 7/Dw8PHx8fLy8vPz8/T09PX19fb29vf39/j4+Pn5+fr6+vv7+/z8/P39/f7+/v///w== --0__=YIFuhpU0eW5K6OxO7vMaIrDVl6wGvWR4CzWbJAfcok9SYb0zWmLXpnm0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 8:56:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.2hip.net (gizmo.2hip.net [208.241.12.2]) by hub.freebsd.org (Postfix) with ESMTP id 332C014C47 for ; Tue, 11 Jan 2000 08:56:25 -0800 (PST) (envelope-from rnoland@gizmo.2hip.net) Received: (from rnoland@localhost) by gizmo.2hip.net (8.9.3/8.9.3) id LAA02562; Tue, 11 Jan 2000 11:56:19 -0500 (EST) (envelope-from rnoland) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14459.24755.490808.223016@gizmo.2hip.net> Date: Tue, 11 Jan 2000 11:56:19 -0500 (EST) From: "Robert C. Noland III" To: Pascal Hofstee Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: freezing... In-Reply-To: <20000111163017.A50249@shadowmere.student.utwente.nl> References: <55926.947513027@critter.freebsd.dk> <200001101945.LAA29394@apollo.backplane.com> <20000110142156.F9397@fw.wintelcom.net> <20000111163017.A50249@shadowmere.student.utwente.nl> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW, a couple weeks ago, I saw the same problem over NFS when autoconf tried to test for gtk-config... It would pretty consistantly hang... robert. Pascal Hofstee writes: >On Mon, Jan 10, 2000 at 02:21:56PM -0800, Alfred Perlstein wrote: >> * Matthew Dillon [000110 12:11] wrote: >> > I've reproduced the softupdates ftruncate panic and have a core dump >> > to play with. >> >> I don't have a panic, but rather many processes start to get stuck >> in "getblk", unfortunatly they all don't stem from a common codepath, >> although the first process that wedged appears to have come through >> indir_trunc: > >I just experienced the same thing here on my CURRENT system with Kirk's >latest SoftUpdates patches included. i have right now a buildworld stuck in >"getblk" on rm ... and a "getblk" hang for Mozilla Tinderbox Build on gcc. > >The Mozilla Tinderbox build "hang" however seems to be reproducible. >I have had two consecutive "hangs" at the same spot: > > checking for gtk-config... /usr/X11R6/bin/gtk-config > >which results in a stuck gcc process. >I will try to build a kernel with kdb support as soon as my buildworld >finishes (if it will finish) and see if I can provide a proper backtrace. > >-- >-------------------- > Pascal Hofstee - daeron@shadowmere.student.utwente.nl > >-----BEGIN GEEK CODE BLOCK----- >Version: 3.1 >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+ >------END GEEK CODE BLOCK------ > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 9:46:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from web2105.mail.yahoo.com (web2105.mail.yahoo.com [128.11.68.249]) by hub.freebsd.org (Postfix) with SMTP id 936B415406 for ; Tue, 11 Jan 2000 09:46:46 -0800 (PST) (envelope-from valsho@yahoo.com) Received: (qmail 12407 invoked by uid 60001); 11 Jan 2000 17:46:42 -0000 Message-ID: <20000111174642.12406.qmail@web2105.mail.yahoo.com> Received: from [147.226.5.3] by web2105.mail.yahoo.com; Tue, 11 Jan 2000 09:46:42 PST Date: Tue, 11 Jan 2000 09:46:42 -0800 (PST) From: "Valentin S. Chopov" Subject: newpcm - duplex/simplex To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my notebook I have pnp CS4232. It has to work in duplex mode - 2 dmas, but it's buggy, and works only in simplex mode - 1 dma (play + capture). Is it possible to add a option to force using of simplex mode on pnp cards? Thanks, Val __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 10:17:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id B084714BC4 for ; Tue, 11 Jan 2000 10:17:06 -0800 (PST) (envelope-from arno@heho.snv.jussieu.fr) Received: from hall.snv.jussieu.fr (hall.snv.jussieu.fr [134.157.37.2]) by shiva.jussieu.fr (8.9.3/jtpda-5.3.2) with ESMTP id TAA18090 for ; Tue, 11 Jan 2000 19:17:03 +0100 (CET) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.37.22]) by hall.snv.jussieu.fr (8.8.8/jtpda-5.2) with SMTP id TAA02794 for ; Tue, 11 Jan 2000 19:09:23 +0100 (CET) Received: by heho.snv.jussieu.fr (4.1/jf930126) at Tue, 11 Jan 00 19:17:02 +0100 To: freebsd-current@freebsd.org Subject: Re: Still system hangs, but different References: <20000111131010.A317@relativity.student.utwente.nl> <20000111172846.A361@relativity.student.utwente.nl> From: arno@heho.snv.jussieu.fr (Arno J. Klaassen) Date: 11 Jan 2000 19:17:01 +0100 In-Reply-To: "Dave J. Boers"'s message of Tue, 11 Jan 2000 17:28:46 +0100 Message-Id: Lines: 25 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI, Dave Boers wrote: > This is an SMP system with the ATA driver and with Kirk's latest > softupdates changes included. same here on an SMP system, sym-scsi driver and softupdates; (BTW, I installed sunday's sources on a mono-processor, sym-scsi, softupdates, system without apparent problems) Regards, Arno -- Arno J. Klaassen INSERM U483, University Pierre et Marie Curie 9, quai Saint Bernard 75 252 Paris Cedex 5 arno@ccr.jussieu.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 10:21:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5AB2C14C3A for ; Tue, 11 Jan 2000 10:21:48 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA39855; Tue, 11 Jan 2000 10:21:48 -0800 (PST) (envelope-from dillon) Date: Tue, 11 Jan 2000 10:21:48 -0800 (PST) From: Matthew Dillon Message-Id: <200001111821.KAA39855@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: Re: Still system hangs, but different References: <20000111131010.A317@relativity.student.utwente.nl> <20000111172846.A361@relativity.student.utwente.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Everyone, make sure you are using at least version 1.47 of ffs_softdep.c. If you manage (with the latest ffs_softdep.c ... 1.47) to get a lockup and your system still works well enough to run commands, and you were smart enough to keep your kernel.debug lying around, then the following would be helpful: gdb -k kernel.debug /dev/mem proc (the pid of the stuck process) back proc (the pid of the next stuck process) back And a 'ps axl' output would be good too (trimmed if you know what to trim out). I think there may still a problem but I haven't been able to reproduce it yet. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 10:27:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id CF58D154A3 for ; Tue, 11 Jan 2000 10:27:27 -0800 (PST) (envelope-from forrie@forrie.net) Received: (from forrie@localhost) by forrie.net (8.10.0.Beta10/8.10.0.Beta10) id e0BIRRI53185 for freebsd-current@freebsd.org; Tue, 11 Jan 2000 13:27:27 -0500 (EST) Date: Tue, 11 Jan 2000 13:27:27 -0500 From: Forrest Aldrich To: freebsd-current@freebsd.org Subject: config tool breaks Message-ID: <20000111132727.A53156@forrie.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this a bug, or did I miss something on the list that changed this procedure: cd /usr/src/sys/i386/conf) bash-2.03# config MYMACHINE config: files.i386: No such file or directory bash-2.03# exit The files.* is missing, etc. No changes after a cvsup. _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 10:31:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 9F4BC14D32 for ; Tue, 11 Jan 2000 10:31:19 -0800 (PST) (envelope-from dervish@goku.cl.msu.edu) Received: (from dervish@localhost) by goku.cl.msu.edu (8.9.3/8.9.3) id NAA47701; Tue, 11 Jan 2000 13:37:01 -0500 (EST) (envelope-from dervish) Date: Tue, 11 Jan 2000 13:37:00 -0500 From: Bush Doctor To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: config tool breaks Message-ID: <20000111133700.C82713@goku.cl.msu.edu> References: <20000111132727.A53156@forrie.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000111132727.A53156@forrie.net>; from forrie@forrie.net on Tue, Jan 11, 2000 at 01:27:27PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Forrest Aldrich aka (forrie@forrie.net) said: > Is this a bug, or did I miss something on the list > that changed this procedure: > > > cd /usr/src/sys/i386/conf) > > bash-2.03# config MYMACHINE > config: files.i386: No such file or directory > bash-2.03# exit > > The files.* is missing, etc. No changes after a cvsup. Did you build a new config first? > > > > _F > #:^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 10:41: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from astralblue.com (adsl-209-76-108-39.dsl.snfc21.pacbell.net [209.76.108.39]) by hub.freebsd.org (Postfix) with ESMTP id 4DA6014E05 for ; Tue, 11 Jan 2000 10:40:57 -0800 (PST) (envelope-from ab@astralblue.com) Received: from localhost (ab@localhost) by astralblue.com (8.9.3/8.9.3) with ESMTP id KAA17805; Tue, 11 Jan 2000 10:40:51 -0800 (PST) (envelope-from ab@astralblue.com) Date: Tue, 11 Jan 2000 10:40:51 -0800 (PST) From: "Eugene M. Kim" To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: config tool breaks In-Reply-To: <20000111132727.A53156@forrie.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently there has been a change in config directory layout (all *.i386 files has been moved from /sys/i386/conf to /sys/conf), so you have to rebuild /usr/sbin/config first. HTH, Eugene PS. The Handbook is, once again, your friend :-). On Tue, 11 Jan 2000, Forrest Aldrich wrote: | Is this a bug, or did I miss something on the list | that changed this procedure: | | | cd /usr/src/sys/i386/conf) | | bash-2.03# config MYMACHINE | config: files.i386: No such file or directory | bash-2.03# exit | | The files.* is missing, etc. No changes after a cvsup. | | | | _F | | | To Unsubscribe: send mail to majordomo@FreeBSD.org | with "unsubscribe freebsd-current" in the body of the message | -- Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 10:49: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 291FA14F00 for ; Tue, 11 Jan 2000 10:49:00 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA31298; Tue, 11 Jan 2000 19:38:19 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00512; Tue, 11 Jan 2000 19:38:30 +0100 (CET) (envelope-from wilko) Date: Tue, 11 Jan 2000 19:38:29 +0100 From: Wilko Bulte To: Andreas Klemm Cc: George Cox , freebsd-current@FreeBSD.ORG Subject: Re: -pipe switch in kernel compilation Message-ID: <20000111193829.A409@yedi.iaf.nl> References: <20000110165543.A5720@extremis.demon.co.uk> <20000111073939.A31293@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000111073939.A31293@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Tue, Jan 11, 2000 at 07:39:40AM +0100 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 07:39:40AM +0100, Andreas Klemm wrote: > On Mon, Jan 10, 2000 at 04:55:43PM +0000, George Cox wrote: > > G'day, > > > > While compiling a kernel today, I noticed that the '-pipe' option to gcc > > was not being used. Is there any reason for this? > > I think this is the (historical) default, so that people with > only 4-8 MB of RAM don't get into trouble ;-) > > Where 4 MB isn't sufficient anymore with a GENERIC kernel. > You need at least 6 MB or so to boot, then compile a custom > kernel and then, if you are lucky, can perhaps run with 4 MB. FWIW: 3.3R ran (crawled?) in 4Mb. I tried it 2 months ago on a 386SX40 with 4Mb. Compiling a GENERIC kernel was 5 hours or so ;-) That is when I gave up on my idea to 'make buildworld'. But still impressive, it was stable. Wilko -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 12:29: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by hub.freebsd.org (Postfix) with ESMTP id 8281114D44 for ; Tue, 11 Jan 2000 12:29:00 -0800 (PST) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id NAA07477; Tue, 11 Jan 2000 13:27:49 -0700 (MST) (envelope-from drussell@saturn-tech.com) Date: Tue, 11 Jan 2000 13:27:49 -0700 (MST) From: Doug Russell To: Pascal Hofstee Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: freezing... In-Reply-To: <20000111163017.A50249@shadowmere.student.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Pascal Hofstee wrote: > I just experienced the same thing here on my CURRENT system with Kirk's > latest SoftUpdates patches included. i have right now a buildworld stuck in > "getblk" on rm ... and a "getblk" hang for Mozilla Tinderbox Build on gcc. > > The Mozilla Tinderbox build "hang" however seems to be reproducible. > I have had two consecutive "hangs" at the same spot: > > checking for gtk-config... /usr/X11R6/bin/gtk-config > > which results in a stuck gcc process. > I will try to build a kernel with kdb support as soon as my buildworld > finishes (if it will finish) and see if I can provide a proper backtrace. I think this goes away if you manually specify the path to gtk-config. I remember I had this problem some weeks ago while trying to build M12 on -CURRENT. I'm not saying you should need to do this, and it is likely a compiler issue that is causing it, but I did get it to work without modifying code. Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 12:33:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by hub.freebsd.org (Postfix) with ESMTP id 3EF7814D80 for ; Tue, 11 Jan 2000 12:33:21 -0800 (PST) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id NAA08091; Tue, 11 Jan 2000 13:32:50 -0700 (MST) (envelope-from drussell@saturn-tech.com) Date: Tue, 11 Jan 2000 13:32:49 -0700 (MST) From: Doug Russell To: Wilko Bulte Cc: freebsd-current@FreeBSD.ORG Subject: Re: -pipe switch in kernel compilation In-Reply-To: <20000111193829.A409@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Wilko Bulte wrote: > FWIW: 3.3R ran (crawled?) in 4Mb. I tried it 2 months ago on a 386SX40 with > 4Mb. > > Compiling a GENERIC kernel was 5 hours or so ;-) That is when I gave up > on my idea to 'make buildworld'. > > But still impressive, it was stable. See, I knew there was a reason I hung on to all these 1M 30 pin SIMMs. :) Old 386/40s sure make nice little router/modem/whatever boxes. :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 12:50: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 3F3C314EC5; Tue, 11 Jan 2000 12:49:57 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id PAA11395; Tue, 11 Jan 2000 15:49:54 -0500 (EST) Date: Tue, 11 Jan 2000 15:49:54 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: ** HEADS UP ** chown&chgrp moved again In-Reply-To: <20000107082513.A96136@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Jan 2000, David O'Brien wrote: > This is a heads up to let you know that you need to > > rm -f /sbin/chwon /bin/chgrp > > after your next `make world'. Additionally you need to install a new > /dev/MAKEDEV (mergmaster(8) will assist you in this). > > A while back I moved the install location for chown and chgrp from > /usr/sbin and /usr/bin to /sbin and /bin. This was because of > MAKEDEV(8)'s dependence on them, and thus forced /usr to be mounted for > correct operation of MAKEDEV(8). Of course that is bad since you could > easily be trying to create the device node to even mount /usr. > > This week, I have added chown-like functionality to mknod(8) and restored > chown & chgrp back to their previous locations. MAKEDEV has been > updated to use the new functionality of mknod(8). > > However, do to this moving around of chown & chgrp's install location, > you may easily have stale versions in /sbin and /bin. > > -- > -- David (obrien@NUXI.com) > > David, I just noticed that this note in 4.0's RELNOTES about the relocation doesn't appear applicable anymore: `chown' has moved from "/usr/sbin" to "/sbin". This is due to dependencies on it by `MAKEDEV'. Please update any scripts that have "/usr/sbin" hardcoded in them. Since `chgrp' is a link to `chown', `chgrp' has moved from "/usr/bin" to "/bin" to reside on the same partition. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 12:53:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2942315360 for ; Tue, 11 Jan 2000 12:53:07 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA36720; Tue, 11 Jan 2000 13:53:02 -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.9.3/8.8.3) with ESMTP id NAA06370; Tue, 11 Jan 2000 13:53:10 -0700 (MST) Message-Id: <200001112053.NAA06370@harmony.village.org> To: Doug Russell Subject: Re: -pipe switch in kernel compilation Cc: Wilko Bulte , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Jan 2000 13:32:49 MST." References: Date: Tue, 11 Jan 2000 13:53:10 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Russell writes: : See, I knew there was a reason I hung on to all these 1M 30 pin SIMMs. :) : Old 386/40s sure make nice little router/modem/whatever boxes. :) Until their hard disks go south :-(. The biggest problems I have with them is that they also tend to dislike newer ATA disks. Then again, I have 512k 72pin SIMMS around for when I want to try to boot the kernel in 2MB of memory. Not that I want to do this very often... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 12:54:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from nic-31-c23-178.mn.mediaone.net (nic-31-c23-178.mn.mediaone.net [24.31.23.178]) by hub.freebsd.org (Postfix) with ESMTP id 5957B15283 for ; Tue, 11 Jan 2000 12:54:39 -0800 (PST) (envelope-from jstock@winterzone.com) Received: from localhost (localhost [127.0.0.1]) by nic-31-c23-178.mn.mediaone.net (8.9.3/8.9.3) with ESMTP id OAA30508 for ; Tue, 11 Jan 2000 14:53:23 -0600 (CST) (envelope-from jstock@winterzone.com) Date: Tue, 11 Jan 2000 14:53:23 -0600 (CST) From: "Jeremy L. Stock" X-Sender: jstock@nic-31-c23-178.mn.mediaone.net To: freebsd-current@FreeBSD.ORG Subject: World Breakage in sys/modules/ukbd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A buildworld done in the last hour with a fresh cvsup fails with the following: touch opt_usb.h echo > ukbd.h echo '#define KBD_INSTALL_CDEV 1' > opt_kbd.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../ include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/ukbd/../../ dev/usb/ukbd.c /usr/src/sys/modules/ukbd/../../dev/usb/ukbd.c:46: opt_ukbd.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/ukbd. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. [2:34pm] 2 [/usr/src]:nic-31-c23-178# exit exit Script done on Tue Jan 11 14:35:13 2000 -- Jeremy L. Stock ICQ 46329337 Fax # 612-629-6540 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 13: 5:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 5B59D14CF7 for ; Tue, 11 Jan 2000 13:05:06 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id NAA10756; Tue, 11 Jan 2000 13:03:54 -0800 (PST) Date: Tue, 11 Jan 2000 13:03:54 -0800 From: Brooks Davis To: Warner Losh Cc: Doug Russell , Wilko Bulte , freebsd-current@FreeBSD.ORG Subject: Re: -pipe switch in kernel compilation Message-ID: <20000111130354.A10601@orion.ac.hmc.edu> References: <200001112053.NAA06370@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200001112053.NAA06370@harmony.village.org>; from imp@village.org on Tue, Jan 11, 2000 at 01:53:10PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 01:53:10PM -0700, Warner Losh wrote: > In message Doug Russell writes: > : See, I knew there was a reason I hung on to all these 1M 30 pin SIMMs. :) > : Old 386/40s sure make nice little router/modem/whatever boxes. :) > > Until their hard disks go south :-(. The biggest problems I have with > them is that they also tend to dislike newer ATA disks. I think that's why IBM has jumpers on some of their disks that limit them to 2GB. I can't see why else you would want to take a perfectly good 8GB+ disk and use it as a 2GB drive. Of course, some of them may not even tolerate that much space. -- Brooks -- "Those who desire to give up freedom in order to gain security, will not have, nor do they deserve, either one" --Thomas Jefferson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 13:25:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mango.attlabs.att.com (gatemp.ipo.att.com [135.197.1.2]) by hub.freebsd.org (Postfix) with ESMTP id E2CE014E4A for ; Tue, 11 Jan 2000 13:25:06 -0800 (PST) (envelope-from fenner@mango.attlabs.att.com) Received: (from fenner@localhost) by mango.attlabs.att.com (8.9.3/8.9.3) id NAA51609; Tue, 11 Jan 2000 13:24:59 -0800 (PST) (envelope-from fenner) From: Bill Fenner Message-Id: <200001112124.NAA51609@mango.attlabs.att.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=19701020; charset=US-ASCII To: current@freebsd.org Subject: "make world" log parser Date: Tue, 11 Jan 2000 13:24:59 -0800 Versions: dmail (bsd44) 2.2c/makemail 2.8t Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --19701020 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline I often want to know where in a "make world" I am, so I wrote this quick little script. It breaks out the major sections, like -------------------------------------------------------------- >>> Cleaning up the elf obj tree -------------------------------------------------------------- and the directory progress indicators, and displays all of the major sections, the last directory progress indicator, and the last 5 lines of log. So you get something like -------------------------------------------------------------- >>> elf make world started on Tue Jan 11 11:19:42 PST 2000 -------------------------------------------------------------- >>> Cleaning up the temporary elf build tree -------------------------------------------------------------- >>> Making make -------------------------------------------------------------- >>> Making mtree -------------------------------------------------------------- >>> Making hierarchy -------------------------------------------------------------- >>> Cleaning up the elf obj tree -------------------------------------------------------------- ===> gnu/lib/libreadline/history/doc rm -f history.info history.info.gz history.texi rm -f .depend /usr/src/gnu/lib/libreadline/history/GPATH /usr/src/gnu/lib/libreadline/history/GRTAGS /usr/src/gnu/lib/libreadline/history/GSYMS /usr/src/gnu/lib/libreadline/history/GTAGS ===> gnu/lib/libreadline/history/doc ===> gnu/lib/libreadline/history/doc rm -f history.info history.info.gz history.texi ===> gnu/lib/libreadline/readline rm -f a.out readline.o vi_mode.o funmap.o keymaps.o parens.o search.o rltty.o complete.o bind.o isearch.o display.o signals.o util.o kill.o undo.o macro.o input.o callback.o terminal.o nls.o xmalloc.o history.o histexpand.o histfile.o histsearch.o shell.o tilde.o readline.o.tmp vi_mode.o.tmp funmap.o.tmp keymaps.o.tmp parens.o.tmp search.o.tmp rltty.o.tmp complete.o.tmp bind.o.tmp isearch.o.tmp display.o.tmp signals.o.tmp util.o.tmp kill.o.tmp undo.o.tmp macro.o.tmp input.o.tmp callback.o.tmp terminal.o.tmp nls.o.tmp xmalloc.o.tmp history.o.tmp histexpand.o.tmp histfile.o.tmp histsearch.o.tmp shell.o.tmp tilde.o.tmp readline.3.gz readline.3.cat.gz Anyway, I think it's so cool that I'm convinced that someone else will like it too, so I'm sending it to -current =) Bill --19701020 Content-Type: application/x-perl; name="whereintheworld"; x-unix-mode=0555 Content-Disposition: attachment; filename="whereintheworld" #!/usr/bin/perl # # whereintheworld # Parses "make world" output and summarize where it's been so far. # # Bill Fenner 11 January 2000 # # $Id: whereintheworld,v 1.2 2000/01/11 21:18:37 fenner Exp $ # use strict; my $lastarrow = undef; my $inside = 0; my @lines = (); my $thresh = 5; my $lastwasdash = 0; my $file = $ARGV[0] || (-f "/usr/src/world.out" ? "/usr/src/world.out" : "-"); open(LOG, $file) || die "$file: $!\n"; while () { if (/^------------/) { $inside = !$inside; print unless ($lastwasdash); $lastwasdash = 1; next; } if ($inside && /^>>>/) { print; $lastwasdash = 0; next; } push(@lines, $_); if ($#lines > $thresh) { my $line = shift(@lines); $lastarrow = $line if ($line =~ /^===>/); } } exit if ($lastwasdash); if ($lines[0] !~ /^===>/ && $lastarrow) { print $lastarrow, "...\n"; } print @lines; --19701020-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 13:46:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 9654F14E37 for ; Tue, 11 Jan 2000 13:46:45 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 3F4E71DA7; Tue, 11 Jan 2000 22:46:39 +0100 (CET) Date: Tue, 11 Jan 2000 22:46:39 +0100 From: "Dave J. Boers" To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Still system hangs, but different Message-ID: <20000111224639.B720@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000111131010.A317@relativity.student.utwente.nl> <20000111172846.A361@relativity.student.utwente.nl> <200001111821.KAA39855@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001111821.KAA39855@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Jan 11, 2000 at 10:21:48AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 10:21:48AM -0800, Matthew Dillon wrote: > Everyone, make sure you are using at least version 1.47 of > ffs_softdep.c. I have. > I think there may still a problem but I haven't been able to reproduce > it yet. Don't know if this helps, but the problem seems to occur only after a certain uptime or a certain amount of i/o operations for that matter. My uptimes are typically about 6 hours before it happens. I've had two occurences of it and both times it happend while mutt was working on some large mailfiles (20 Mb or so). Once it was sorting a file and the other time it was sending a message and immediately afterward rereading the "outbox" file. It's a bit difficult to do anything like gdb or ps once it happens, because disk i/o is impossible. Once I had a running top and saw that mutt remained in the "wait" state. I have noticed that other i/o related things go awry sometimes also with version 1.47 of ffs_softdep.c. I once couldn't "rm -fR" a build tree no matter how hard or often I tried. The rm process just hung. I had to reboot an old kernel just to delete the build tree. Regards, Dave Boers. -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 13:50:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C569214E8A for ; Tue, 11 Jan 2000 13:50:21 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA36915; Tue, 11 Jan 2000 14:50:18 -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.9.3/8.8.3) with ESMTP id OAA06787; Tue, 11 Jan 2000 14:50:26 -0700 (MST) Message-Id: <200001112150.OAA06787@harmony.village.org> To: Brooks Davis Subject: Re: -pipe switch in kernel compilation Cc: Doug Russell , Wilko Bulte , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Jan 2000 13:03:54 PST." <20000111130354.A10601@orion.ac.hmc.edu> References: <20000111130354.A10601@orion.ac.hmc.edu> <200001112053.NAA06370@harmony.village.org> Date: Tue, 11 Jan 2000 14:50:26 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000111130354.A10601@orion.ac.hmc.edu> Brooks Davis writes: : On Tue, Jan 11, 2000 at 01:53:10PM -0700, Warner Losh wrote: : > In message Doug Russell writes: : > : See, I knew there was a reason I hung on to all these 1M 30 pin SIMMs. :) : > : Old 386/40s sure make nice little router/modem/whatever boxes. :) : > : > Until their hard disks go south :-(. The biggest problems I have with : > them is that they also tend to dislike newer ATA disks. : : I think that's why IBM has jumpers on some of their disks that limit : them to 2GB. I can't see why else you would want to take a perfectly : good 8GB+ disk and use it as a 2GB drive. Of course, some of them may : not even tolerate that much space. I've retired perfectly good systems that can't handle having a 600MB disk connected to them. Anything over 540MB seems to give it fits, although I suppose that a BIOS upgrade would help. I couldn't even lie to the BIOS and tell it that the drive's geometry was such that only 540MB would be used. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 13:57:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 8125915056 for ; Tue, 11 Jan 2000 13:57:06 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40333>; Wed, 12 Jan 2000 08:49:18 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: -pipe switch in kernel compilation In-reply-to: <20000111130354.A10601@orion.ac.hmc.edu>; from brooks@one-eyed-alien.net on Wed, Jan 12, 2000 at 07:58:12AM +1100 To: freebsd-current@FreeBSD.ORG Message-Id: <00Jan12.084918est.40333@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200001112053.NAA06370@harmony.village.org> <20000111130354.A10601@orion.ac.hmc.edu> Date: Wed, 12 Jan 2000 08:49:16 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Jan-12 07:58:12 +1100, Brooks Davis wrote: >I think that's why IBM has jumpers on some of their disks that limit >them to 2GB. I can't see why else you would want to take a perfectly >good 8GB+ disk and use it as a 2GB drive. The volumes probably mean it's not cost-effective to either continue to produce smaller older technology drives, or design a new small drive. > Of course, some of them may not even tolerate that much space. AFAIK, the BIOS in my Toshiba T1850 won't allow anything bigger than 130MB. Getting FreeBSD into my current 80MB isn't fun (and the major reason it hasn't been updated from 2.2.5 - I can't cut 3.x down far enough to fit, and -current is even larger). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 13:58:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B1731151F5 for ; Tue, 11 Jan 2000 13:57:58 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA36970 for ; Tue, 11 Jan 2000 14:57:57 -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.9.3/8.8.3) with ESMTP id OAA06924 for ; Tue, 11 Jan 2000 14:58:06 -0700 (MST) Message-Id: <200001112158.OAA06924@harmony.village.org> Subject: Re: -pipe switch in kernel compilation To: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Jan 2000 14:50:26 MST." <200001112150.OAA06787@harmony.village.org> References: <200001112150.OAA06787@harmony.village.org> <20000111130354.A10601@orion.ac.hmc.edu> <200001112053.NAA06370@harmony.village.org> Date: Tue, 11 Jan 2000 14:58:05 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Before you ask, I've also tried to use the tapr[*] CF <-> IDE adapter to see if I could get these systems to boot off a 16MB CF card with no luck. I even have a mini486 based system from NEC that I bought surplus that I thought could use the CF card, but no joy. Works great on all the modern machines I've tried it on. likely a BIOS issue, but I don't wanna write bios for a machine that only cost me $49.99 that has no docs. Warner [*] http://www.tapr.org/, as featured on slashdot a long time ago. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 14: 4:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 93CEA14E8A for ; Tue, 11 Jan 2000 14:04:15 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA08334; Tue, 11 Jan 2000 22:49:47 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03500; Tue, 11 Jan 2000 22:15:49 +0100 (CET) (envelope-from wilko) Date: Tue, 11 Jan 2000 22:15:49 +0100 From: Wilko Bulte To: Doug Russell Cc: freebsd-current@FreeBSD.ORG Subject: Re: -pipe switch in kernel compilation Message-ID: <20000111221549.A3443@yedi.iaf.nl> Reply-To: freebsd-chat@FreeBSD.ORG References: <20000111193829.A409@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from drussell@saturn-tech.com on Tue, Jan 11, 2000 at 01:32:49PM -0700 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 01:32:49PM -0700, Doug Russell wrote: > > On Tue, 11 Jan 2000, Wilko Bulte wrote: > > > FWIW: 3.3R ran (crawled?) in 4Mb. I tried it 2 months ago on a 386SX40 with > > 4Mb. > > > > Compiling a GENERIC kernel was 5 hours or so ;-) That is when I gave up > > on my idea to 'make buildworld'. > > > > But still impressive, it was stable. > > See, I knew there was a reason I hung on to all these 1M 30 pin SIMMs. :) > Old 386/40s sure make nice little router/modem/whatever boxes. :) I guess with Picobsd it would run better. People wanted to can the board, brandnew in the wrapper. That is when I rescued it (for no good reason other than curiosity what FreeBSD would think of it). [followup to -chat] -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 14: 5:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from xena.cs.waikato.ac.nz (xena.cs.waikato.ac.nz [130.217.241.20]) by hub.freebsd.org (Postfix) with ESMTP id 1CA0D1502A for ; Tue, 11 Jan 2000 14:05:07 -0800 (PST) (envelope-from joerg@lucy.cs.waikato.ac.nz) Received: from lucy.cs.waikato.ac.nz (joerg@lucy.cs.waikato.ac.nz [130.217.241.12]) by xena.cs.waikato.ac.nz (8.9.3/8.9.3) with ESMTP id LAA07469; Wed, 12 Jan 2000 11:04:58 +1300 (NZDT) Received: (from joerg@localhost) by lucy.cs.waikato.ac.nz (8.9.3/8.9.0) id LAA03479; Wed, 12 Jan 2000 11:04:56 +1300 (NZDT) Date: Wed, 12 Jan 2000 11:04:56 +1300 From: Joerg Micheel To: current@freebsd.org Cc: joerg@cs.waikato.ac.nz Subject: Additional option to ls -l for large files Message-ID: <20000112110456.X5228@cs.waikato.ac.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Organization: SCMS, The University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... drained by Solaris 7 SPARC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently dealing with an increasing set of *very* large files, most of them in the order of gigabytes. It becomes impossible to figure the size of a file with ls -l with 9 or more digits displayed. I would propose a new flag to ls which will together with option -l change the unit to kilobytes for files larger than one megabyte, to megabytes for files larger than one gigabyte and gigabytes for files larger than one terabyte. A 'k', 'm' or 'g' respectively should be appended. Would such a patch find the blessing of the team and the maintainer of ls ? Joerg -- Joerg B. Micheel Email: Waikato Applied Network Dynamics Phone: +64 7 8384794 The University of Waikato, CompScience Fax: +64 7 8384155 Private Bag 3105 Pager: +64 868 38222 Hamilton, New Zealand Plan: TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 14:21:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 1AE6714E09 for ; Tue, 11 Jan 2000 14:21:55 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA25652; Tue, 11 Jan 2000 14:21:38 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001112221.OAA25652@gndrsh.dnsmgr.net> Subject: Re: Additional option to ls -l for large files In-Reply-To: <20000112110456.X5228@cs.waikato.ac.nz> from Joerg Micheel at "Jan 12, 2000 11:04:56 am" To: joerg@cs.waikato.ac.nz (Joerg Micheel) Date: Tue, 11 Jan 2000 14:21:38 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm currently dealing with an increasing set of *very* large files, > most of them in the order of gigabytes. It becomes impossible to > figure the size of a file with ls -l with 9 or more digits displayed. > I would propose a new flag to ls which will together with option -l > change the unit to kilobytes for files larger than one megabyte, to > megabytes for files larger than one gigabyte and gigabytes for files > larger than one terabyte. A 'k', 'm' or 'g' respectively should be > appended. > > Would such a patch find the blessing of the team and the maintainer > of ls ? Another thing that ``works for me''. Only make it ki, mi, and gi to fit with the new binary mode international appreviation standards, unless of cource you use base 10 divisors. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 14:23:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 49F6E14C58; Tue, 11 Jan 2000 14:23:06 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id XAA07229; Tue, 11 Jan 2000 23:23:02 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id XAA01612; Tue, 11 Jan 2000 23:22:59 +0100 (MEZ) Date: Tue, 11 Jan 2000 23:22:59 +0100 From: Martin Blapp To: current@freebsd.org Cc: billf@freebsd.org Subject: proposed /etc/rc.network change ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I propose to change rc.network in the way that portmapper and the nfs services are started _before_ any nfs filesystems get mounted. This will fix loopback and local mounts in fstab. But cause portmap is located in /usr/sbin, we have to move it into /sbin, else some nfs mounted /usr users will complain ! And here is the patch: . Just look at the part in the middle '/etc/rc.network'. Thanks for discussions und suggestions ! Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 14:24: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id 6F46515497 for ; Tue, 11 Jan 2000 14:24:02 -0800 (PST) (envelope-from fn@gatekeeper.radio-do.de) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by gatekeeper.radio-do.de (Postfix) with ESMTP id EDAFEBD5C; Tue, 11 Jan 2000 23:23:54 +0100 (MET) Received: (from fn@localhost) by trinity.radio-do.de (8.9.3/8.9.3) id XAA23327; Tue, 11 Jan 2000 23:23:54 +0100 (CET) (envelope-from fn@gatekeeper.radio-do.de) Date: Tue, 11 Jan 2000 23:23:54 +0100 From: Frank Nobis To: Joerg Micheel Cc: current@FreeBSD.ORG Subject: Re: Additional option to ls -l for large files Message-ID: <20000111232354.A23124@radio-do.de> References: <20000112110456.X5228@cs.waikato.ac.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000112110456.X5228@cs.waikato.ac.nz> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 11:04:56AM +1300, Joerg Micheel wrote: > [ls whith sizes in k,M] > > Would such a patch find the blessing of the team and the maintainer > of ls ? You could try gnuls -h -fn- -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 14:39:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from xena.cs.waikato.ac.nz (xena.cs.waikato.ac.nz [130.217.241.20]) by hub.freebsd.org (Postfix) with ESMTP id EEDF014FE9 for ; Tue, 11 Jan 2000 14:39:26 -0800 (PST) (envelope-from joerg@lucy.cs.waikato.ac.nz) Received: from lucy.cs.waikato.ac.nz (joerg@lucy.cs.waikato.ac.nz [130.217.241.12]) by xena.cs.waikato.ac.nz (8.9.3/8.9.3) with ESMTP id LAA08220; Wed, 12 Jan 2000 11:39:23 +1300 (NZDT) Received: (from joerg@localhost) by lucy.cs.waikato.ac.nz (8.9.3/8.9.0) id LAA03919; Wed, 12 Jan 2000 11:39:21 +1300 (NZDT) Date: Wed, 12 Jan 2000 11:35:28 +1300 From: Joerg Micheel To: current@freebsd.org Cc: Joerg Micheel Subject: Re: Additional option to ls -l for large files Message-ID: <20000112113528.Y5228@cs.waikato.ac.nz> References: <20000112110456.X5228@cs.waikato.ac.nz> <20000111232354.A23124@radio-do.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Received: from lucy.cs.waikato.ac.nz (joerg@lucy.cs.waikato.ac.nz [130.217.241.12]) by xena.cs.waikato.ac.nz (8.9.3/8.9.3) with ESMTP id LAA08129; Wed, 12 Jan 2000 11:35:30 +1300 (NZDT) Received: (from joerg@localhost) by lucy.cs.waikato.ac.nz (8.9.3/8.9.0) id LAA03912; Wed, 12 Jan 2000 11:35:28 +1300 (NZDT) In-Reply-To: <20000111232354.A23124@radio-do.de>; from Frank Nobis on Tue, Jan 11, 2000 at 11:23:54PM +0100 Organization: SCMS, The University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... drained by Solaris 7 SPARC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 11:23:54PM +0100, Frank Nobis wrote: > On Wed, Jan 12, 2000 at 11:04:56AM +1300, Joerg Micheel wrote: > > [ls whith sizes in k,M] > > > > Would such a patch find the blessing of the team and the maintainer > > of ls ? > > You could try gnuls -h As much as I tried - this is not within GNU fileutils. Which version and package are you referring to ? Are you using a FreeBSD system ? Joerg PS: Frank, you are unreachable directly, so I had to post back to the list. relay.orbs.net is blocking your domain, please fix it. -- Joerg B. Micheel Email: Waikato Applied Network Dynamics Phone: +64 7 8384794 The University of Waikato, CompScience Fax: +64 7 8384155 Private Bag 3105 Pager: +64 868 38222 Hamilton, New Zealand Plan: TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 14:45:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from jester.ti.com (jester.ti.com [192.94.94.1]) by hub.freebsd.org (Postfix) with ESMTP id C3E6B14D94 for ; Tue, 11 Jan 2000 14:45:56 -0800 (PST) (envelope-from ntakpe@ffab.tide.ti.com) Received: from dlep9.itg.ti.com ([157.170.135.38]) by jester.ti.com (8.9.3/8.9.3) with ESMTP id QAA28625; Tue, 11 Jan 2000 16:44:39 -0600 (CST) Received: from dlep9.itg.ti.com (localhost [127.0.0.1]) by dlep9.itg.ti.com (8.9.3/8.9.3) with ESMTP id QAA02862; Tue, 11 Jan 2000 16:45:16 -0600 (CST) Received: from wrks2host.ffab.tide.ti.com (wrks2host.ffab.tide.ti.com [137.167.200.37]) by dlep9.itg.ti.com (8.9.3/8.9.3) with ESMTP id QAA02858; Tue, 11 Jan 2000 16:45:14 -0600 (CST) Received: from ishtar.ffab.tide.ti.com (ishtar.ffab.tide.ti.com [137.167.200.61]) by wrks2host.ffab.tide.ti.com (8.8.8+Sun/8.8.8) with ESMTP id XAA16600; Tue, 11 Jan 2000 23:45:13 +0100 (MET) Received: from ishtar.ffab.tide.ti.com (IDENT:ntakpe@ishtar.ffab.tide.ti.com [137.167.200.61]) by ishtar.ffab.tide.ti.com (8.9.3/8.9.3) with ESMTP id XAA18852; Tue, 11 Jan 2000 23:45:12 +0100 Message-ID: <387BB277.3B24640C@ishtar.ffab.tide.ti.com> Date: Tue, 11 Jan 2000 23:45:11 +0100 From: Jean Louis Ntakpe Organization: TI Freising - Automation Group X-Sender: "Jean Louis Ntakpe" <@ishtar.ffab.tide.ti.com> (Unverified) X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i586) X-Accept-Language: en MIME-Version: 1.0 To: Joerg Micheel Cc: current@FreeBSD.ORG Subject: Re: Additional option to ls -l for large files References: <20000112110456.X5228@cs.waikato.ac.nz> <20000111232354.A23124@radio-do.de> <20000112113528.Y5228@cs.waikato.ac.nz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joerg Micheel wrote: > > On Tue, Jan 11, 2000 at 11:23:54PM +0100, Frank Nobis wrote: > > On Wed, Jan 12, 2000 at 11:04:56AM +1300, Joerg Micheel wrote: > > > [ls whith sizes in k,M] > > > > > > Would such a patch find the blessing of the team and the maintainer > > > of ls ? > > > > You could try gnuls -h > > As much as I tried - this is not within GNU fileutils. Which version and > package are you referring to ? Are you using a FreeBSD system ? > > Joerg > see packages-3.4-release (or whatever version you run) : gnuls-4.0.tgz regards, -- Jean Louis Ntakpe Texas Instruments - Freising Wafer Fab Automation Group Haggerty Str. 1 D-85350 Freising, Germany Phone +49 8161 80-3816 Fax +49 8161 80-3762 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 14:46:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 67CC81547C for ; Tue, 11 Jan 2000 14:46:38 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id A1DAEC6; Tue, 11 Jan 2000 14:46:33 -0800 (PST) Date: Tue, 11 Jan 2000 14:46:33 -0800 From: Chris Piazza To: Joerg Micheel Cc: current@FreeBSD.ORG Subject: Re: Additional option to ls -l for large files Message-ID: <20000111144633.A360@norn.ca.eu.org> References: <20000112110456.X5228@cs.waikato.ac.nz> <20000111232354.A23124@radio-do.de> <20000112113528.Y5228@cs.waikato.ac.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000112113528.Y5228@cs.waikato.ac.nz>; from joerg@cs.waikato.ac.nz on Wed, Jan 12, 2000 at 11:35:28AM +1300 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 11:35:28AM +1300, Joerg Micheel wrote: > On Tue, Jan 11, 2000 at 11:23:54PM +0100, Frank Nobis wrote: > > On Wed, Jan 12, 2000 at 11:04:56AM +1300, Joerg Micheel wrote: > > > [ls whith sizes in k,M] > > > > > > Would such a patch find the blessing of the team and the maintainer > > > of ls ? > > > > You could try gnuls -h > > As much as I tried - this is not within GNU fileutils. Which version and > package are you referring to ? Are you using a FreeBSD system ? > /usr/ports/misc/gnuls -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 14:46:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id B7E371548E for ; Tue, 11 Jan 2000 14:46:47 -0800 (PST) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id XAA17828; Tue, 11 Jan 2000 23:47:07 +0100 (MET) Received: by petra.hos.u-szeged.hu (Linux Smail3.2.0.92 #1) id m128A8B-000oZcC; Tue, 11 Jan 2000 22:51:15 +0000 () Date: Tue, 11 Jan 2000 23:51:13 +0100 From: Szilveszter Adam To: current@freebsd.org Subject: Additional option to ls -l for large files Message-ID: <20000111235113.D24526@petra.hos.u-szeged.hu> Mail-Followup-To: current@freebsd.org References: <20000112110456.X5228@cs.waikato.ac.nz> <20000111232354.A23124@radio-do.de> <20000112113528.Y5228@cs.waikato.ac.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000112113528.Y5228@cs.waikato.ac.nz> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 11:35:28AM +1300, Joerg Micheel wrote: > > You could try gnuls -h > > As much as I tried - this is not within GNU fileutils. Which version and > package are you referring to ? Are you using a FreeBSD system ? > > Joerg Hi! Have you tried it in: /usr/ports/misc/gnuls ? Sometimes they are in different places than you would expect, like colorls, colortail etc. Hope it helps. Regards: Szilveszter ADAM -- ------------------------------------------------------------------------------- * Szilveszter ADAM * JATE Szeged * email: sziszi@petra.hos.u-szeged.hu * * Homepage : none * alternate email: cc@flanker.itl.net.ua * * Finger sziszi@petra.hos.u-szeged.hu for PGP key. * * I prefer using the door instead of Windows(tm)... * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 14:50: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 9B47F14F26 for ; Tue, 11 Jan 2000 14:49:56 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA25732; Tue, 11 Jan 2000 14:49:39 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001112249.OAA25732@gndrsh.dnsmgr.net> Subject: Re: Additional option to ls -l for large files In-Reply-To: <8070C3A4E99ED211A63200105A19B99B3174A2@mail.edifecs.com> from Michael VanLoon at "Jan 11, 2000 02:39:50 pm" To: MichaelV@EDIFECS.COM (Michael VanLoon) Date: Tue, 11 Jan 2000 14:49:39 -0800 (PST) Cc: joerg@cs.waikato.ac.nz, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Charset windows-1252 unsupported, skipping...] Arghh... windblows... > >> I'm currently dealing with an increasing set of *very* large files, > >> most of them in the order of gigabytes. It becomes impossible to > >> figure the size of a file with ls -l with 9 or more digits displayed. > >> I would propose a new flag to ls which will together with option -l > >> change the unit to kilobytes for files larger than one megabyte, to > >> megabytes for files larger than one gigabyte and gigabytes for files > >> larger than one terabyte. A 'k', 'm' or 'g' respectively should be > >> appended. > >> > >> Would such a patch find the blessing of the team and the maintainer > >> of ls ? > > > >Another thing that ``works for me''. Only make it ki, mi, and gi > >to fit with the new binary mode international appreviation standards, > >unless of cource you use base 10 divisors. > > Why not KB, MB or GB, since that's what you're actually reporting? Because KB MB and GB mean different things than KiB MiB and GiB. K = 10^3, Ki = 2^10 M = 10^6 Mi = 2^20 G = 10^9 Gi = 2^30 > What is this "binary mode international abbreviation standard"? See above... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 14:56:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from xena.cs.waikato.ac.nz (xena.cs.waikato.ac.nz [130.217.241.20]) by hub.freebsd.org (Postfix) with ESMTP id 263AF14D71 for ; Tue, 11 Jan 2000 14:56:33 -0800 (PST) (envelope-from joerg@lucy.cs.waikato.ac.nz) Received: from lucy.cs.waikato.ac.nz (joerg@lucy.cs.waikato.ac.nz [130.217.241.12]) by xena.cs.waikato.ac.nz (8.9.3/8.9.3) with ESMTP id LAA08674; Wed, 12 Jan 2000 11:56:30 +1300 (NZDT) Received: (from joerg@localhost) by lucy.cs.waikato.ac.nz (8.9.3/8.9.0) id LAA04233; Wed, 12 Jan 2000 11:56:29 +1300 (NZDT) Date: Wed, 12 Jan 2000 11:56:28 +1300 From: Joerg Micheel To: Jean Louis Ntakpe Cc: current@freebsd.org Subject: Re: Additional option to ls -l for large files Message-ID: <20000112115628.Z5228@cs.waikato.ac.nz> References: <20000112110456.X5228@cs.waikato.ac.nz> <20000111232354.A23124@radio-do.de> <20000112113528.Y5228@cs.waikato.ac.nz> <387BB277.3B24640C@ishtar.ffab.tide.ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <387BB277.3B24640C@ishtar.ffab.tide.ti.com>; from Jean Louis Ntakpe on Tue, Jan 11, 2000 at 11:45:11PM +0100 Organization: SCMS, The University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... drained by Solaris 7 SPARC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 11:45:11PM +0100, Jean Louis Ntakpe wrote: > Joerg Micheel wrote: > > > > On Tue, Jan 11, 2000 at 11:23:54PM +0100, Frank Nobis wrote: > > > On Wed, Jan 12, 2000 at 11:04:56AM +1300, Joerg Micheel wrote: > > > > [ls whith sizes in k,M] > > > > > > > > Would such a patch find the blessing of the team and the maintainer > > > > of ls ? > > > > > > You could try gnuls -h > > > > As much as I tried - this is not within GNU fileutils. Which version and > > package are you referring to ? Are you using a FreeBSD system ? > > > > Joerg > > > > see packages-3.4-release (or whatever version you run) : > gnuls-4.0.tgz Ok, ok. I admit, silly me. I ran into inconsistent documentation, the fileutils html page on www.gnu.org doesn't include -h yet. Yes, I guess -h is what I was looking for. Thanks. Joerg -- Joerg B. Micheel Email: Waikato Applied Network Dynamics Phone: +64 7 8384794 The University of Waikato, CompScience Fax: +64 7 8384155 Private Bag 3105 Pager: +64 868 38222 Hamilton, New Zealand Plan: TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 15:13:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id AB08014E99 for ; Tue, 11 Jan 2000 15:13:55 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA37233; Tue, 11 Jan 2000 16:13:53 -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.9.3/8.8.3) with ESMTP id QAA07511; Tue, 11 Jan 2000 16:14:02 -0700 (MST) Message-Id: <200001112314.QAA07511@harmony.village.org> To: "Rodney W. Grimes" Subject: Re: Additional option to ls -l for large files Cc: MichaelV@EDIFECS.COM (Michael VanLoon), joerg@cs.waikato.ac.nz, current@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Jan 2000 14:49:39 PST." <200001112249.OAA25732@gndrsh.dnsmgr.net> References: <200001112249.OAA25732@gndrsh.dnsmgr.net> Date: Tue, 11 Jan 2000 16:14:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001112249.OAA25732@gndrsh.dnsmgr.net> "Rodney W. Grimes" writes: : Because KB MB and GB mean different things than KiB MiB and GiB. : : K = 10^3, Ki = 2^10 : M = 10^6 Mi = 2^20 : G = 10^9 Gi = 2^30 kB and kiB are the proper abreviations, not KB and KiB. I don't know if miB or MiB is correct, likely MiB. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 15:29:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 0BB7714D77 for ; Tue, 11 Jan 2000 15:29:17 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA66118; Tue, 11 Jan 2000 18:28:48 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200001112249.OAA25732@gndrsh.dnsmgr.net> References: <200001112249.OAA25732@gndrsh.dnsmgr.net> Date: Tue, 11 Jan 2000 18:29:08 -0500 To: "Rodney W. Grimes" , MichaelV@EDIFECS.COM (Michael VanLoon) From: Garance A Drosihn Subject: Re: Additional option to ls -l for large files Cc: joerg@cs.waikato.ac.nz, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:49 PM -0800 1/11/00, Rodney W. Grimes wrote: > > >Another thing that ``works for me''. Only make it ki, mi, and gi > > >to fit with the new binary mode international appreviation standards, > > >unless of cource you use base 10 divisors. > > > > Why not KB, MB or GB, since that's what you're actually reporting? > >Because KB MB and GB mean different things than KiB MiB and GiB. > >K = 10^3, Ki = 2^10 >M = 10^6 Mi = 2^20 >G = 10^9 Gi = 2^30 personally, I'd just as soon use K, M, and G and have it mean the base-10 values. If I'm looking at a decimal number for one file (because it's small enough), I don't want a base-2 version of the similar number for some other (larger) file in the same listing. (ie, whatever letters you use, please just divide the values by 1000 instead of 1024). --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 15:34:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from po8.andrew.cmu.edu (PO8.ANDREW.CMU.EDU [128.2.10.108]) by hub.freebsd.org (Postfix) with ESMTP id DA36E15139 for ; Tue, 11 Jan 2000 15:34:23 -0800 (PST) (envelope-from tcrimi+@andrew.cmu.edu) Received: (from postman@localhost) by po8.andrew.cmu.edu (8.9.3/8.9.3) id SAA11749; Tue, 11 Jan 2000 18:34:21 -0500 (EST) Received: via switchmail; Tue, 11 Jan 2000 18:34:20 -0500 (EST) Received: from unix4.andrew.cmu.edu via qmail ID ; Tue, 11 Jan 2000 18:27:51 -0500 (EST) Received: from unix4.andrew.cmu.edu via qmail ID ; Tue, 11 Jan 2000 18:27:51 -0500 (EST) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix4.andrew.cmu.edu.sun4m.54 via MS.5.6.unix4.andrew.cmu.edu.sun4_51; Tue, 11 Jan 2000 18:27:51 -0500 (EST) Message-ID: Date: Tue, 11 Jan 2000 18:27:51 -0500 (EST) From: Thomas Valentino Crimi To: Yoshinobu Inoue Subject: Re: IPv6 testing...willing to help Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, looks like I'll join the fray as well. I've just turned on IPSec between two machines, an i386 and Alpha, both running very recent currents, each has the IPSEC and IPSEC_ESP config options set, but does not have IP6 support enabled. I used setkey and could establish what appear to be encrypted connections using vanilla telnet between the hosts, (can someone recommend a good packet sniffer to ensure this? tcpflow ignored connections between the ipsec hosts. I used tcpdump -x with a large snaplen and saw that sending a constant stream of the 0's yeilded the different packets.) What is curious, though, is that during a telnet, running any command to dump a large amount of information to the screen will lock up the connection forcing me to login again. Similar things happen with ftp (locked up after logging in when I first issue an ls). The surest way to lock up teh connection is to go to /sys/compile/KERN and do an ls. Data piped to more (a screenful at a time) seems to be ok, but substancially more locks up TCP connections. This does not occur with NFS (I build a kernel using it). I notice that setkey -D yeilds different numbers between the machines in terms of "current:" bytes. What data can I provide to help in fixing this problem? Regards. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 16: 0:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id A2ECB154E4 for ; Tue, 11 Jan 2000 16:00:36 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id KAA02810; Wed, 12 Jan 2000 10:30:28 +1030 (CST) (envelope-from newton) Date: Wed, 12 Jan 2000 10:30:28 +1030 From: Mark Newton To: gandalf@vilnya.demon.co.uk Cc: freebsd-current@FreeBSD.ORG Subject: Re: newpcm Message-ID: <20000112103028.G2420@internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Cameron Grant" writes: > would everyone who currently has an issue outstanding with newpcm please > report it to me in the next few days directly, please, so i can get an idea > of what needs work before release. i need as much detail as possible. SB AWE64 (ISA) works fine for most things, but audio is *very* scratchy and up to five seconds behind the action in Quake-II (these problems didn't exist with the old snd0 controller). Linux RealPlayer, mpg123, and just about everything else I've tried it with are happy, though. -current from Jan 9, dmesg is: sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 9 drq 0,5 on isa0 sbc0: setting card to irq 9, drq 0, 5 pcm0: on sbc0 /dev/sndstat says: newton@atdot> cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 11 2000 09:18:06 Installed devices: pcm0: at io 0x220 irq 9 drq 0:5 (1/1 channels duplex) - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 16: 3:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 7311014D94 for ; Tue, 11 Jan 2000 16:03:18 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 26332 invoked from network); 12 Jan 2000 00:03:13 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 12 Jan 2000 00:03:13 -0000 Message-ID: <387BC4A6.3B7DF57A@cvzoom.net> Date: Tue, 11 Jan 2000 19:02:46 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Additional option to ls -l for large files References: <200001112249.OAA25732@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn wrote: [trimmed list of recipients to just -current] > personally, I'd just as soon use K, M, and G and have it mean > the base-10 values. If I'm looking at a decimal number for one > file (because it's small enough), I don't want a base-2 version > of the similar number for some other (larger) file in the same > listing. > > (ie, whatever letters you use, please just divide the values > by 1000 instead of 1024). Or else we could put both in. There could be either a command-line option or env variable set that selects between decimal (true metric) or powers of two (computer metric, or whatever). - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 16: 7:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 8096D153B2; Tue, 11 Jan 2000 16:07:24 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.9.3/8.9.3) with UUCP id CAA05964; Wed, 12 Jan 2000 02:15:16 +0300 (MSK) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id BAA28576; Wed, 12 Jan 2000 01:32:34 +0300 (MSK) Date: Wed, 12 Jan 2000 01:32:34 +0300 From: Alexey Zelkin To: current@FreeBSD.org, dillon@FreeBSD.org Subject: vn device strange behaviour Message-ID: <20000112013234.A28567@scorpion.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I just discovered some strange points about using vn devices (files) as swap devices. I have placed below some output gathered with script(1) and now some comments. 1) I can easy unconfigure vn device which already mounted as swap device and then remove swapfile without any problems. I not sure about behaviour of the swapper when it will try to allocate swap from /dev/vn0c. 2) When I am creating small file (about 100k) and try to mount it as swap device swapinfo(8) output looks broken. 3) I could not mount three and more vn devices as swap devices. BTW, I also got strange results once (but I could not reporoduce it later): swapinfo(8) shown that I have three swap devices mounted: /dev/wd0s1b, /dev/rvn0c and /dev/#46:10. What's that ? I'll try to reproduce it again, but ... Comments ? ------------------------------------------------- 1) # dd if=/dev/zero of=swapfile count=1 bs=50m 1+0 records in 1+0 records out 52428800 bytes transferred in 8.401941 secs (6240082 bytes/sec) # vnconfig -e /dev/vn0c swapfile swap # swapon /dev/vn0c # swapinfo Device 1K-blocks Used Avail Capacity Type /dev/wd0s1b 32640 2640 30000 8% Interleaved /dev/rvn0c 51072 0 51072 0% Interleaved Total 83712 2640 81072 3% # vnconfig -u /dev/vn0c # swapinfo Device 1K-blocks Used Avail Capacity Type /dev/wd0s1b 32640 2640 30000 8% Interleaved /dev/rvn0c 51072 0 51072 0% Interleaved Total 83712 2640 81072 3% # vnconfig -e /dev/vn0c swapfile swap # swapon /dev/vn0c swapon: /dev/vn0c: device already in use # vnconfig -u /dev/vn0c # rm swapfile # swapinfo Device 1K-blocks Used Avail Capacity Type /dev/wd0s1b 32640 2640 30000 8% Interleaved /dev/rvn0c 51072 0 51072 0% Interleaved Total 83712 2640 81072 3% # 2) # dd if=/dev/zero of=smallswap count=1 bs=100k 1+0 records in 1+0 records out 102400 bytes transferred in 0.003174 secs (32261453 bytes/sec) # vnconfig -c /dev/vn1c smallswap swap # swapon /dev/vn1c # swapinfo Device 1K-blocks Used Avail Capacity Type /dev/wd0s1b 32640 2212 30428 7% Interleaved /dev/rvn1c -28 -28 0 100% Interleaved Total 83684 2184 81500 3% # 3) # swapinfo Device 1K-blocks Used Avail Capacity Type /dev/wd0s1b 32640 0 32640 0% Interleaved /dev/rvn0c 51072 0 51072 0% Interleaved /dev/rvn1c 51072 0 51072 0% Interleaved Total 134784 0 134784 0% # vnconfig -c /dev/vn2c smallswap # swapon /dev/vn2c swapon: /dev/vn2c: Invalid argument # -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@FreeBSD.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 16: 8:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id E8AAD14D17; Tue, 11 Jan 2000 16:08:28 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from vigrid.com (pm3-pt6.pcnet.net [206.105.29.80]) by pcnet1.pcnet.com (8.8.7/PCNet) with ESMTP id TAA13123; Tue, 11 Jan 2000 19:08:22 -0500 (EST) Message-ID: <387BC58B.959E54BF@vigrid.com> Date: Tue, 11 Jan 2000 19:06:35 -0500 From: "Daniel M. Eischen" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Cc: cg@FreeBSD.org Subject: Support for ESS1878 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've got sound working on my laptop with ESS1878 with -current as of Jan 10th: sbc1: at port 0x220-0x22f,0x388-0x38b,0x300-0x301 irq 7 drq 1,0 on isa0 pcm0: on sbc1 Anyone mind if I commit the following patch to add support for this chip? Index: sbc.c =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/isa/sbc.c,v retrieving revision 1.15 diff -u -r1.15 sbc.c --- sbc.c 1999/12/26 10:51:47 1.15 +++ sbc.c 2000/01/12 00:02:08 @@ -208,6 +208,7 @@ {0x68187316, "ESS ES1868"}, /* ESS1868 */ {0x69187316, "ESS ES1869"}, /* ESS1869 */ {0xacb0110e, "ESS ES1869 (Compaq OEM)"}, /* CPQb0ac */ + {0x78187316, "ESS ES1878"}, /* ESS1878 */ {0x79187316, "ESS ES1879"}, /* ESS1879 */ {0x88187316, "ESS ES1888"}, /* ESS1888 */ {0x07017316, "ESS ES1888 (DEC OEM)"}, /* ESS0107 */ Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 16: 9:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id F2EE015449 for ; Tue, 11 Jan 2000 16:09:31 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca44-58.ix.netcom.com [209.111.212.186]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id QAA46646 for ; Tue, 11 Jan 2000 16:09:27 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id QAA89430; Tue, 11 Jan 2000 16:08:55 -0800 (PST) Date: Tue, 11 Jan 2000 16:08:55 -0800 (PST) Message-Id: <200001120008.QAA89430@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: current@FreeBSD.org Subject: crashes From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have people seen these? === node82 1/2 === bash-2.02# gdb -k *.22 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"...(no debugging symbols found)... IdlePTD 2945024 initial pcb at 25fb60 panicstr: ffs_blkfree: freeing free block panic messages: --- panic: ffs_blkfree: freeing free block syncing disks... 244 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 giving up on 2 buffers Uptime: 8d23h21m29s dumping to dev #wd/0x20001, offset 917632 dump ata0: resetting devices .. done 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 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 --- #0 0xc012fbd0 in boot () (kgdb) bt #0 0xc012fbd0 in boot () #1 0xc012ff54 in poweroff_wait () #2 0xc01c75d5 in ffs_blkfree () #3 0xc01cb626 in handle_workitem_freeblocks () #4 0xc01c9bbf in softdep_process_worklist () #5 0xc0156ff3 in sched_sync () #6 0xc0204620 in fork_trampoline () Cannot access memory at address 0x2000. (kgdb) quit === === node82 2/2 === bash-2.02# gdb -k *.23 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"...(no debugging symbols found)... IdlePTD 2945024 initial pcb at 25fb60 panicstr: page fault panic messages: --- panic: handle_allocdirect_partdone: lost dep 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:0xc01c9832 stack pointer = 0x10:0xc0242fbc frame pointer = 0x10:0xc0242fc0 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: 9h27m2s dumping to dev #wd/0x20001, offset 917632 dump ata0: resetting devices .. done 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 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 --- #0 0xc012fbd0 in boot () (kgdb) bt #0 0xc012fbd0 in boot () #1 0xc012ff54 in poweroff_wait () #2 0xc021226d in trap_fatal () #3 0xc0211f45 in trap_pfault () #4 0xc0211b2b in trap () #5 0xc01c9832 in acquire_lock () #6 0xc01cc45e in softdep_disk_io_initiation () #7 0xc0167173 in spec_strategy () #8 0xc0166cad in spec_vnoperate () #9 0xc01d813d in ufs_vnoperatespec () #10 0xc01d7bbd in ufs_strategy () #11 0xc01d810d in ufs_vnoperate () #12 0xc014f958 in bwrite () #13 0xc0154a0e in vop_stdbwrite () #14 0xc0154869 in vop_defaultop () #15 0xc01d810d in ufs_vnoperate () #16 0xc0150772 in vfs_bio_awrite () #17 0xc01d1921 in ffs_fsync () #18 0xc01d03d0 in ffs_sync () #19 0xc01595e3 in sync () #20 0xc012f9a3 in boot () #21 0xc012ff54 in poweroff_wait () #22 0xc01ccba1 in handle_allocdirect_partdone () #23 0xc01cc952 in softdep_disk_write_complete () #24 0xc0151bca in biodone () #25 0xc01ed8d2 in ad_interrupt () #26 0xc01eadf6 in ataintr () (kgdb) quit === === node87 1/1 === bash-2.02# gdb -k *.6 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"...(no debugging symbols found)... IdlePTD 2945024 initial pcb at 25fb60 panicstr: softdep_lock: lock held by -2 panic messages: --- panic: handle_allocdirect_partdone: lost dep syncing disks... panic: softdep_lock: lock held by -2 Uptime: 9d1h24m57s dumping to dev #wd/0x20001, offset 917632 dump ata0: resetting devices .. done 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 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 --- #0 0xc012fbd0 in boot () (kgdb) bt #0 0xc012fbd0 in boot () #1 0xc012ff54 in poweroff_wait () #2 0xc01c9851 in acquire_lock () #3 0xc01cc516 in initiate_write_filepage () #4 0xc01cc3e3 in softdep_disk_io_initiation () #5 0xc0167173 in spec_strategy () #6 0xc0166cad in spec_vnoperate () #7 0xc01d813d in ufs_vnoperatespec () #8 0xc01d7bbd in ufs_strategy () #9 0xc01d810d in ufs_vnoperate () #10 0xc014f958 in bwrite () #11 0xc0154a0e in vop_stdbwrite () #12 0xc0154869 in vop_defaultop () #13 0xc01d810d in ufs_vnoperate () #14 0xc014fb46 in bawrite () #15 0xc01d188f in ffs_fsync () #16 0xc01d03d0 in ffs_sync () #17 0xc01595e3 in sync () #18 0xc012f9a3 in boot () #19 0xc012ff54 in poweroff_wait () #20 0xc01ccba1 in handle_allocdirect_partdone () #21 0xc01cc952 in softdep_disk_write_complete () #22 0xc0151bca in biodone () #23 0xc01ed8d2 in ad_interrupt () #24 0xc01eadf6 in ataintr () #25 0x80ddc62 in ?? () #26 0x80de251 in ?? () #27 0x80ddd46 in ?? () #28 0x80de09c in ?? () #29 0x80ddfb6 in ?? () #30 0x80de131 in ?? () #31 0x80de131 in ?? () #32 0x80de2a5 in ?? () #33 0x80ddd46 in ?? () #34 0x80de09c in ?? () #35 0x80ddfb6 in ?? () #36 0x80de131 in ?? () #37 0x80ddfb6 in ?? () #38 0x80de131 in ?? () #39 0x80de131 in ?? () #40 0x80ddfb6 in ?? () #41 0x80ddfc5 in ?? () #42 0x80ddfd7 in ?? () #43 0x80de131 in ?? () #44 0x80ddfc5 in ?? () #45 0x80de131 in ?? () #46 0x80de131 in ?? () #47 0x80ddfc5 in ?? () #48 0x80ddfd7 in ?? () #49 0x80de131 in ?? () #50 0x80ddfc5 in ?? () #51 0x80de131 in ?? () #52 0x80ddfc5 in ?? () #53 0x80de131 in ?? () #54 0x80ddfc5 in ?? () #55 0x80ddfd7 in ?? () #56 0x80de131 in ?? () #57 0x80ddfd7 in ?? () #58 0x80de131 in ?? () #59 0x80ddfc5 in ?? () #60 0x80de131 in ?? () #61 0x80ddfd7 in ?? () #62 0x80ddfd7 in ?? () #63 0x80de131 in ?? () #64 0x80ddfc5 in ?? () ---Type to continue, or q to quit--- #65 0x80ddf78 in ?? () #66 0x80dd7e3 in ?? () #67 0x80eee12 in ?? () #68 0x8118c39 in ?? () #69 0x80ef5ef in ?? () #70 0x80ef154 in ?? () #71 0x8118c39 in ?? () #72 0x80ef5ef in ?? () #73 0x80ef30a in ?? () #74 0x80ee495 in ?? () #75 0x80ed0ac in ?? () #76 0x80ee196 in ?? () #77 0x80ec180 in ?? () #78 0x80eca08 in ?? () #79 0x80ee196 in ?? () #80 0x80ec180 in ?? () #81 0x80ecc07 in ?? () #82 0x80ee196 in ?? () #83 0x80ec180 in ?? () #84 0x80ef57d in ?? () #85 0x80ef154 in ?? () #86 0x80ee264 in ?? () #87 0x80ec015 in ?? () #88 0x80ee196 in ?? () #89 0x80ec180 in ?? () #90 0x80ecc07 in ?? () #91 0x80ee196 in ?? () #92 0x80ec180 in ?? () #93 0x80ebff5 in ?? () #94 0x80ee196 in ?? () #95 0x80ec180 in ?? () #96 0x80ecc07 in ?? () #97 0x80ee196 in ?? () #98 0x80ec180 in ?? () #99 0x80ebff5 in ?? () #100 0x80ee196 in ?? () #101 0x80ec180 in ?? () #102 0x80eccb8 in ?? () #103 0x80ee196 in ?? () #104 0x80ec180 in ?? () #105 0x80ef57d in ?? () #106 0x80ef30a in ?? () #107 0x80ee52c in ?? () #108 0x80ec180 in ?? () #109 0x80ecc07 in ?? () #110 0x80ee196 in ?? () #111 0x80ec180 in ?? () #112 0x80ef57d in ?? () #113 0x80ef30a in ?? () #114 0x80ee52c in ?? () #115 0x80ec180 in ?? () #116 0x80ecc07 in ?? () #117 0x80ee196 in ?? () #118 0x80ec180 in ?? () #119 0x80ef57d in ?? () #120 0x80ef30a in ?? () #121 0x80ee52c in ?? () #122 0x80eeffd in ?? () #123 0x8118c39 in ?? () #124 0x80ef5ef in ?? () #125 0x80ef154 in ?? () #126 0x8118c39 in ?? () #127 0x80ef5ef in ?? () #128 0x80ef154 in ?? () #129 0x8118c39 in ?? () ---Type to continue, or q to quit--- #130 0x80ef5ef in ?? () #131 0x80ef30a in ?? () #132 0x80ee495 in ?? () #133 0x8097484 in ?? () #134 0x80ed337 in ?? () #135 0x80974b3 in ?? () #136 0x80ecf64 in ?? () #137 0x80973f5 in ?? () #138 0x8097051 in ?? () #139 0x8097149 in ?? () #140 0x809623f in ?? () #141 0x804d5fd in ?? () (kgdb) q === Both machines are of -current, Dec 26 vintage. These machines died building -current packages. (Gee, sounds like real heroes.) These crashes usually result in fsck -p failing during subsequent reboot. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 16:13:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id BA33C14DFE for ; Tue, 11 Jan 2000 16:13:16 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 28432 invoked from network); 12 Jan 2000 00:13:15 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 12 Jan 2000 00:13:15 -0000 Message-ID: <387BC701.61C7EDF6@cvzoom.net> Date: Tue, 11 Jan 2000 19:12:49 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Any Wine or Mozilla hackers here? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I figured I'd address these two issues in one posting here. First of all, does anyone work with Mozilla by checking out the source code by anon cvs? One of the build stages does a "cvs co" when you do gmake -f client.mk. There's a lot of long pauses where you see a lot of "waiting for lock in..." and "obtained lock in..." I was thinking that for such a large project as Mozilla (>>100 MB), cvsup would be much better than cvs. Of course, it might be a little too late in the project to convince the Mozilla team to switch now. Anyone try talking the team into using cvsup? Wine: There's a thing where certain Windows programs need to use Ring level 0, whatever that is. I guess Wine needs ring level 0 for certain programs that use VxDs (supervisor mode). AFAIK, most programs use ring level 2. I was thinking maybe a kernel module may be able to put us in ring level 0, or is that too risky? Of course, Wine is a low priority thing, but does anyone here hack on Wine, or have any comments on this? - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 16:15:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 6E00815326 for ; Tue, 11 Jan 2000 16:15:40 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id BAA19954; Wed, 12 Jan 2000 01:15:07 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id BAA05049; Wed, 12 Jan 2000 01:15:07 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id BAA01308; Wed, 12 Jan 2000 01:14:49 +0100 (CET) (envelope-from ticso) Date: Wed, 12 Jan 2000 01:14:48 +0100 From: Bernd Walter To: "Justin T. Gibbs" Cc: djb@Wit389306.student.utwente.nl, current@FreeBSD.ORG Subject: Re: Strange SCSI related system hang Message-ID: <20000112011447.B1144@cicely8.cicely.de> References: <20000109134916.A382@relativity.student.utwente.nl> <200001110004.RAA01471@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200001110004.RAA01471@narnia.plutotech.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 05:04:09PM -0700, Justin T. Gibbs wrote: > In article <20000109134916.A382@relativity.student.utwente.nl> you wrote: > > Hi all, > > > > This morning I had a very strange (at least I've never seen it before) SCSI > > related system hang. The system simply stopped responding at 9:30:03 am > > this morning. I found it in this state at 13:20. It had been hanging > > _hard_. No response to console, serial terminal or network. After a hard > > reset the system came back online normally and is working normally again. > > > > Note that the machine had an uptime of 4 days, 14 hours before the problem > > occured and it never happened before. > > > > Could this be a hardware problem? > > Perhaps. Is your WD drive getting hot? The ahc driver believes that, > during a message out phase, the target simply dropped off the bus. > It may be that the ahc driver did something to provoke that, but without > a bus analyzer on the drive, it is hard to know. According to the > progrom counter, we are waiting for the target to request the next > byte at the time this occurs, but that request never comes. If it only happens from time to time it also could be a power loss. Check your power cabling to be shure. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 16:32:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 7030F14DDE for ; Tue, 11 Jan 2000 16:32:21 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id BAA20847; Wed, 12 Jan 2000 01:31:22 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id BAA05129; Wed, 12 Jan 2000 01:31:22 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id BAA01350; Wed, 12 Jan 2000 01:31:04 +0100 (CET) (envelope-from ticso) Date: Wed, 12 Jan 2000 01:31:03 +0100 From: Bernd Walter To: Doug Russell Cc: Wilko Bulte , freebsd-current@FreeBSD.ORG Subject: Re: -pipe switch in kernel compilation Message-ID: <20000112013103.A1288@cicely8.cicely.de> References: <20000111193829.A409@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 01:32:49PM -0700, Doug Russell wrote: > > On Tue, 11 Jan 2000, Wilko Bulte wrote: > > > FWIW: 3.3R ran (crawled?) in 4Mb. I tried it 2 months ago on a 386SX40 with > > 4Mb. > > > > Compiling a GENERIC kernel was 5 hours or so ;-) That is when I gave up > > on my idea to 'make buildworld'. > > > > But still impressive, it was stable. > > See, I knew there was a reason I hung on to all these 1M 30 pin SIMMs. :) > Old 386/40s sure make nice little router/modem/whatever boxes. :) > Yes and a recent current still works :) Including the IPv6 parts that are already in current. cicely4# dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Jan 9 16:48:52 CET 2000 ticso@cicely5.cicely.de:/var/d0/src-2000-01-07/src/sys/compile/CICELY4 Timecounter "i8254" frequency 1193182 Hz CPU: i386DX (386-class CPU) real memory = 8388608 (8192K bytes) avail memory = 5668864 (5536K bytes) Preloaded elf kernel "kernel" at 0xc02ba000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02ba09c. npx0: on motherboard npx0: using IRQ 13 interface isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 fd1: <1200-KB 5.25" drive> on fdc0 drive 1 WARNING: "fd" is usurping "fd"'s cdevsw[] WARNING: "fd" is usurping "fd"'s bmaj aha0 at port 0x334-0x337 irq 11 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-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2 at port 0x3e8-0x3ef irq 5 on isa0 sio2: type 16550A sio3 at port 0x2e8-0x2ef irq 7 on isa0 sio3: type 16550A ed0 at port 0x300-0x31f iomem 0xcc000-0xcffff irq 10 on isa0 ed0: supplying EUI64: 00:00:c0:ff:fe:27:94:9f ed0: address 00:00:c0:27:94:9f, type WD8013WC (16 bit) 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: 5.000MB/s transfers (5.000MHz, offset 8) da0: 958MB (1962030 512 byte sectors: 64H 32S/T 958C) -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 16:39:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 6DD9614EF2 for ; Tue, 11 Jan 2000 16:39:26 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:mZY8MvEDd1MlzCNi7M63HyO44WaiDrZf@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id JAA29874; Wed, 12 Jan 2000 09:39:12 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA03330; Wed, 12 Jan 2000 09:44:39 +0900 (JST) Message-Id: <200001120044.JAA03330@zodiac.mech.utsunomiya-u.ac.jp> To: "Jeremy L. Stock" Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: World Breakage in sys/modules/ukbd In-reply-to: Your message of "Tue, 11 Jan 2000 14:53:23 CST." References: Date: Wed, 12 Jan 2000 09:44:38 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, sorry. Apply the attached patch to /sys/modules/ukbd/Makefile. Kazu >A buildworld done in the last hour with a fresh cvsup fails with the >following: > >touch opt_usb.h >echo > ukbd.h >echo '#define KBD_INSTALL_CDEV 1' > opt_kbd.h >rm -f .depend >mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../ >include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/ukbd/../../ >dev/usb/ukbd.c >/usr/src/sys/modules/ukbd/../../dev/usb/ukbd.c:46: opt_ukbd.h: No such file or > >directory >mkdep: compile failed >*** Error code 1 [...] Index: Makefile =================================================================== RCS file: /src/CVS/src/sys/modules/ukbd/Makefile,v retrieving revision 1.8 diff -u -r1.8 Makefile --- Makefile 1999/11/28 18:53:31 1.8 +++ Makefile 1999/12/13 10:07:14 @@ -5,15 +5,18 @@ .PATH: ${.CURDIR}/../../dev/usb KMOD = ukbd SRCS = bus_if.h device_if.h vnode_if.h \ - opt_usb.h ukbd.h opt_kbd.h \ + opt_usb.h ukbd.h opt_kbd.h opt_ukbd.h \ ukbd.c NOMAN = -CLEANFILES = ukbd.h opt_kbd.h +CLEANFILES = ukbd.h opt_kbd.h opt_ukbd.h ukbd.h: echo > ukbd.h opt_kbd.h: echo '#define KBD_INSTALL_CDEV 1' > opt_kbd.h + +opt_ukbd.h: + echo > opt_ukbd.h .include To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 16:57:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from parsons.rh.rit.edu (res112b-165.rh.rit.edu [129.21.112.165]) by hub.freebsd.org (Postfix) with ESMTP id 72F2315031 for ; Tue, 11 Jan 2000 16:57:24 -0800 (PST) (envelope-from mfisher@csh.rit.edu) Received: from mfisher (helo=localhost) by parsons.rh.rit.edu with local-esmtp (Exim 2.12 #1) id 128C67-000Jzy-00; Tue, 11 Jan 2000 19:57:15 -0500 Date: Tue, 11 Jan 2000 19:57:14 -0500 (EST) From: Mike Fisher X-Sender: mfisher@res112b-165.rh.rit.edu To: "Rodney W. Grimes" Cc: current@FreeBSD.ORG Subject: Re: Additional option to ls -l for large files In-Reply-To: <200001112249.OAA25732@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 11 Jan 2000, Rodney W. Grimes wrote: > Because KB MB and GB mean different things than KiB MiB and GiB. > > K = 10^3, Ki = 2^10 > M = 10^6 Mi = 2^20 > G = 10^9 Gi = 2^30 Why not use Knuth's (good) suggestion for differentiating these prefixes? http://www-cs-faculty.stanford.edu/~knuth/news99.html Page down to the ``What is a kilobyte?'' section. Note where he says that bad ideas don't have to be accepted simply because they are the standard. - -- Mike "The man who puts all the guns and all the decision-making power into the hands of the central government and then says, 'Limit yourself'; it is he who is truly the impractical utopian." -- Murray Rothbard -----BEGIN PGP SIGNATURE----- Version: PGP for Personal Privacy 5.0i Comment: Charset: noconv iQA+AwUBOHvRa+G+Jfm/z6tNEQKeQgCYsgMjGJuEIzSdGuOZhzD9bGyCEACfWGXU If3lwGo63sD2JmuIWRkvwbw= =gxx6 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 17:11: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 3C3CB154D4; Tue, 11 Jan 2000 17:10:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 2C9301CD812; Tue, 11 Jan 2000 17:10:59 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 11 Jan 2000 17:10:59 -0800 (PST) From: Kris Kennaway To: Donn Miller Cc: current@freebsd.org Subject: Re: Any Wine or Mozilla hackers here? In-Reply-To: <387BC701.61C7EDF6@cvzoom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Donn Miller wrote: > I figured I'd address these two issues in one posting here. First of > all, does anyone work with Mozilla by checking out the source code by > anon cvs? One of the build stages does a "cvs co" when you do gmake They should use cvs -R to do it read-only.. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 17:42:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B980A14E7B for ; Tue, 11 Jan 2000 17:42:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA65875; Tue, 11 Jan 2000 17:41:59 -0800 (PST) (envelope-from dillon) Date: Tue, 11 Jan 2000 17:41:59 -0800 (PST) From: Matthew Dillon Message-Id: <200001120141.RAA65875@apollo.backplane.com> To: Alexey Zelkin Cc: current@FreeBSD.ORG Subject: Re: vn device strange behaviour References: <20000112013234.A28567@scorpion.crimea.ua> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :hi, : :I just discovered some strange points about using vn devices (files) as :swap devices. : :I have placed below some output gathered with script(1) and now :some comments. : :1) I can easy unconfigure vn device which already mounted as swap device :and then remove swapfile without any problems. I not sure about behaviour :of the swapper when it will try to allocate swap from /dev/vn0c. : :2) When I am creating small file (about 100k) and try to mount it as swap :device swapinfo(8) output looks broken. : :3) I could not mount three and more vn devices as swap devices. : :BTW, I also got strange results once (but I could not reporoduce it later): :swapinfo(8) shown that I have three swap devices mounted: /dev/wd0s1b, :/dev/rvn0c and /dev/#46:10. What's that ? I'll try to reproduce it again, :but ... : :Comments ? Don't unconfigure a VN device mounted as swap unless you want your system to die a horrible death. It shouldn't allow it to happen, but it does and that's a bug. The first 128K of any swap partition is left alone by the swap subsystem in order to ensure that the disklabel (if any) is not overwritten. Do not configure tiny swap spaces -- apart from being useless they will cause swapinfo to print confusing output. By default the kernel is configured to support 4 SWAP partitions. Therefore you can only configure a maximum of 4 SWAP partiions. You can change this in the kernel config. Note however that setting the number arbitrarily high will cause a huge amount of KVM to be wasted. Four is usually enough for anyone. At some point in the future it will be possible to unconfigure swap, but not right now. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 18: 2:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 2103B14F9D for ; Tue, 11 Jan 2000 18:02:30 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id SAA26378; Tue, 11 Jan 2000 18:01:54 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001120201.SAA26378@gndrsh.dnsmgr.net> Subject: Re: Additional option to ls -l for large files In-Reply-To: from Garance A Drosihn at "Jan 11, 2000 06:29:08 pm" To: drosih@rpi.edu (Garance A Drosihn) Date: Tue, 11 Jan 2000 18:01:53 -0800 (PST) Cc: MichaelV@EDIFECS.COM (Michael VanLoon), joerg@cs.waikato.ac.nz, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 2:49 PM -0800 1/11/00, Rodney W. Grimes wrote: > > > >Another thing that ``works for me''. Only make it ki, mi, and gi > > > >to fit with the new binary mode international appreviation standards, > > > >unless of cource you use base 10 divisors. > > > > > > Why not KB, MB or GB, since that's what you're actually reporting? > > > >Because KB MB and GB mean different things than KiB MiB and GiB. > > > >K = 10^3, Ki = 2^10 > >M = 10^6 Mi = 2^20 > >G = 10^9 Gi = 2^30 > > personally, I'd just as soon use K, M, and G and have it mean > the base-10 values. If I'm looking at a decimal number for one > file (because it's small enough), I don't want a base-2 version > of the similar number for some other (larger) file in the same > listing. > > (ie, whatever letters you use, please just divide the values > by 1000 instead of 1024). Please don't, there is already far to much precedence in both the computing world and other commands (df -k and du -k come to mind right off the top of my head, sysinstall uses them in the disklabel and partition editor, etc) df man page: -k Use 1024-byte (1-Kbyte) blocks rather than the default. Note that this overrides the BLOCKSIZE specification from the environ- ment. du man page: -k Display block counts in 1024-byte (1-Kbyte) blocks. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 18:31:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-104.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.232]) by hub.freebsd.org (Postfix) with ESMTP id 98B5C15139 for ; Tue, 11 Jan 2000 18:31:09 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA34148; Wed, 12 Jan 2000 00:58:21 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA64247; Tue, 11 Jan 2000 20:52:22 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001112052.UAA64247@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Stephan van Beerschoten Cc: freebsd-current@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: PPP connections die in current.... In-Reply-To: Message from Stephan van Beerschoten of "Sun, 09 Jan 2000 23:47:55 +0100." <20000109234755.B11681@supra.rotterdam.luna.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 20:52:22 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Jan 09, 2000 at 02:20:51PM -0800, William Woods wrote: > > Running 4.0 -current as of today.....on a DEC Alphaststion 233 when I dial out > > I connect for about 30 seconds then it dies...here is a copy of the ppp.log > > I got the same thing once in a while. I'm using PPPoE. I cannot quote the > 4 referring lines out of the logs, they have already scrolled out. > > But i'm talking about a daily updated cvs-system and almost (bi)-weekly > compiled worlds. By ``the same'' do you mean that you're establishing the PPPoE session ok and your ISP is sending REQs but refusing to acknowledge yours ? > -Steve > > -- > Stephan van Beerschoten Email: stephanb@luna.nl > Network Engineer Luna Internet Services > PGP fingerprint 4557 9761 B212 FB4C 778D 3529 C42A 2D27 -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 18:31:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-104.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.232]) by hub.freebsd.org (Postfix) with ESMTP id 1452814D88; Tue, 11 Jan 2000 18:31:27 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA34151; Wed, 12 Jan 2000 00:59:37 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA48886; Tue, 11 Jan 2000 20:50:56 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001112050.UAA48886@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: William Woods Cc: freebsd-current@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: PPP connections die in current.... In-Reply-To: Message from William Woods of "Sun, 09 Jan 2000 14:20:51 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 20:50:56 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Running 4.0 -current as of today.....on a DEC Alphaststion 233 when I dial out > I connect for about 30 seconds then it dies...here is a copy of the ppp.log [.....] Well, you're receiving data from the peer, but the peer is not sending any response to your config request. From what I can see, ppp is behaving exactly right. I have no idea what your ISP is expecting - he's sending exactly the same REQ as you are. You could try ``set accmap 000a0000'', but I'll bet it won't help. I think you're stuck with asking your ISP to tell you what their side thinks it's doing. You could also try ``set log +physical'' to see if anything funny is being read from the device and dropped, but again I expect nada :-( > ---------------------------------- > E-Mail: William Woods > Date: 09-Jan-00 > Time: 14:17:46 > FreeBSD 3.4 > ---------------------------------- -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 18:34:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 43E9615467 for ; Tue, 11 Jan 2000 18:34:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA66268; Tue, 11 Jan 2000 18:34:50 -0800 (PST) (envelope-from dillon) Date: Tue, 11 Jan 2000 18:34:50 -0800 (PST) From: Matthew Dillon Message-Id: <200001120234.SAA66268@apollo.backplane.com> To: asami@cs.berkeley.edu (Satoshi Asami) Cc: current@FreeBSD.ORG Subject: Re: crashes References: <200001120008.QAA89430@silvia.hip.berkeley.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Have people seen these? : :#0 0xc012fbd0 in boot () :(kgdb) bt :#0 0xc012fbd0 in boot () :#1 0xc012ff54 in poweroff_wait () :#2 0xc01c75d5 in ffs_blkfree () :#3 0xc01cb626 in handle_workitem_freeblocks () :#4 0xc01c9bbf in softdep_process_worklist () :#5 0xc0156ff3 in sched_sync () :#6 0xc0204620 in fork_trampoline () :Cannot access memory at address 0x2000. :(kgdb) quit :=== I have occassionally seen this failure when setting vfs.vmiodirenable to 1. I have not seen it otherwise. Please upgrade your system to the latest ffs_softdep.c, vers 1.47. This will fix a number of other problems but may not fix this one. If you can reproduce this bug reliably w/ the latest ffs_softdep.c then we may have a chance of finding it. :#5 0xc01c9832 in acquire_lock () :#6 0xc01cc45e in softdep_disk_io_initiation () :#7 0xc0167173 in spec_strategy () :#8 0xc0166cad in spec_vnoperate () :#9 0xc01d813d in ufs_vnoperatespec () :#10 0xc01d7bbd in ufs_strategy () :#11 0xc01d810d in ufs_vnoperate () :#12 0xc014f958 in bwrite () :#13 0xc0154a0e in vop_stdbwrite () :#14 0xc0154869 in vop_defaultop () :#15 0xc01d810d in ufs_vnoperate () :#16 0xc0150772 in vfs_bio_awrite () :#17 0xc01d1921 in ffs_fsync () :#18 0xc01d03d0 in ffs_sync () :#19 0xc01595e3 in sync () :#20 0xc012f9a3 in boot () :#21 0xc012ff54 in poweroff_wait () :#22 0xc01ccba1 in handle_allocdirect_partdone () :#23 0xc01cc952 in softdep_disk_write_complete () :#24 0xc0151bca in biodone () :#25 0xc01ed8d2 in ad_interrupt () :#26 0xc01eadf6 in ataintr () :(kgdb) quit I don't know about this one. :panicstr: softdep_lock: lock held by -2 :panic messages: :--- :panic: handle_allocdirect_partdone: lost dep : :syncing disks... panic: softdep_lock: lock held by -2 :Uptime: 9d1h24m57s : :dumping to dev #wd/0x20001, offset 917632 :dump ata0: resetting devices .. done :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 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 :--- :#0 0xc012fbd0 in boot () :(kgdb) bt :#0 0xc012fbd0 in boot () :#1 0xc012ff54 in poweroff_wait () :#2 0xc01c9851 in acquire_lock () :#3 0xc01cc516 in initiate_write_filepage () :#4 0xc01cc3e3 in softdep_disk_io_initiation () :#5 0xc0167173 in spec_strategy () :#6 0xc0166cad in spec_vnoperate () :#7 0xc01d813d in ufs_vnoperatespec () :#8 0xc01d7bbd in ufs_strategy () :#9 0xc01d810d in ufs_vnoperate () :#10 0xc014f958 in bwrite () :#11 0xc0154a0e in vop_stdbwrite () :#12 0xc0154869 in vop_defaultop () :#13 0xc01d810d in ufs_vnoperate () :#14 0xc014fb46 in bawrite () :#15 0xc01d188f in ffs_fsync () :#16 0xc01d03d0 in ffs_sync () :#17 0xc01595e3 in sync () :#18 0xc012f9a3 in boot () :#19 0xc012ff54 in poweroff_wait () :#20 0xc01ccba1 in handle_allocdirect_partdone () :#21 0xc01cc952 in softdep_disk_write_complete () :#22 0xc0151bca in biodone () :#23 0xc01ed8d2 in ad_interrupt () :#24 0xc01eadf6 in ataintr () This is new to me too. Any chance you can get a kernel core dump on these machines instead of just rebooting? And have a debug kernel for them? :Both machines are of -current, Dec 26 vintage. These machines died :building -current packages. (Gee, sounds like real heroes.) These :crashes usually result in fsck -p failing during subsequent reboot. : :Satoshi Yes, the fsck thingy happens to me too though if this is a Dec 26 kernel you should definitely update it -- I seem to recall something related to fsck being fixed around that time frame and there was a softupdates fix after that time frame for a bug occuring before the time frame committed as well (separate from the current spate of softupdates issues). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 18:38: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id 9A5E614F2D; Tue, 11 Jan 2000 18:37:36 -0800 (PST) (envelope-from akm@mail.theinternet.com.au) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id MAA77235; Wed, 12 Jan 2000 12:38:13 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <200001120238.MAA77235@mail.theinternet.com.au> Subject: Re: PPP connections die in current.... In-Reply-To: <200001112050.UAA48886@hak.lan.Awfulhak.org> from Brian Somers at "Jan 11, 2000 8:50:56 pm" To: brian@Awfulhak.org (Brian Somers) Date: Wed, 12 Jan 2000 12:38:13 +1000 (EST) Cc: freebsd@cybcon.com, freebsd-current@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG, brian@hak.lan.Awfulhak.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG +----[ Brian Somers ]--------------------------------------------- | > Running 4.0 -current as of today.....on a DEC Alphaststion 233 when I dial out | > I connect for about 30 seconds then it dies...here is a copy of the ppp.log | [.....] | | Well, you're receiving data from the peer, but the peer is not | sending any response to your config request. From what I can see, | ppp is behaving exactly right. | | I have no idea what your ISP is expecting - he's sending exactly the | same REQ as you are. | | You could try ``set accmap 000a0000'', but I'll bet it won't help. I | think you're stuck with asking your ISP to tell you what their side | thinks it's doing. You could also try ``set log +physical'' to see | if anything funny is being read from the device and dropped, but | again I expect nada :-( Try disabling compression. I've seen this before also, when ppp was trying to talk to pppd. I think it's specifically related to DEFLATE compression, it was a while ago now that I saw it. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 18:42: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-104.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.232]) by hub.freebsd.org (Postfix) with ESMTP id CEF1C154AB; Tue, 11 Jan 2000 18:41:49 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA34696; Wed, 12 Jan 2000 02:41:43 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA06239; Wed, 12 Jan 2000 02:45:51 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001120245.CAA06239@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Andrew Kenneth Milton Cc: brian@Awfulhak.org (Brian Somers), freebsd@cybcon.com, freebsd-current@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG, brian@hak.lan.Awfulhak.org, brian@hak.lan.Awfulhak.org Subject: Re: PPP connections die in current.... In-Reply-To: Message from Andrew Kenneth Milton of "Wed, 12 Jan 2000 12:38:13 +1000." <200001120238.MAA77235@mail.theinternet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 02:45:51 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > +----[ Brian Somers ]--------------------------------------------- > | > Running 4.0 -current as of today.....on a DEC Alphaststion 233 when I dial out > | > I connect for about 30 seconds then it dies...here is a copy of the ppp.log > | [.....] > | > | Well, you're receiving data from the peer, but the peer is not > | sending any response to your config request. From what I can see, > | ppp is behaving exactly right. > | > | I have no idea what your ISP is expecting - he's sending exactly the > | same REQ as you are. > | > | You could try ``set accmap 000a0000'', but I'll bet it won't help. I > | think you're stuck with asking your ISP to tell you what their side > | thinks it's doing. You could also try ``set log +physical'' to see > | if anything funny is being read from the device and dropped, but > | again I expect nada :-( > > Try disabling compression. I've seen this before also, when ppp was > trying to talk to pppd. > > I think it's specifically related to DEFLATE compression, it was a while > ago now that I saw it. Compression hasn't yet been negotiated. No compression takes place on these initial LCP packets. > -- > Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton > The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | > ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon > PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 18:48:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from pop3.ids.net (pop3.ids.net [155.212.1.107]) by hub.freebsd.org (Postfix) with ESMTP id 0BCB115139 for ; Tue, 11 Jan 2000 18:48:23 -0800 (PST) (envelope-from CGiordano@ids.net) Received: from ids.net (dyn177g.egr-ri.ids.net [155.212.223.177]) by pop3.ids.net (8.9.3/8.9.3) with ESMTP id VAA28061; Tue, 11 Jan 2000 21:48:01 -0500 (EST) Message-ID: <387C3130.4930E69B@ids.net> Date: Wed, 12 Jan 2000 02:45:52 -0500 From: Chris Giordano Reply-To: CGiordano@ids.net X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Reinier Bezuidenhout , freebsd-current@FreeBSD.ORG Subject: Re: newpcm References: <200001110908.LAA06044@oskar.dev.nanoteq.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Reinier Bezuidenhout wrote: > > I'm also experiencing a dely in sound on most games ... on some > it's up to 7 seconds behind the action of the game ... > > Xgalaga is an example of this delay .... > > Any ideas ... Luigi Rizzo explained this behavior in the old pcm driver about a year or so ago. I believe it was due to some applications setting a fixed buffering size with the SETFRAGMENT(?) ioctl, which was not implemented in old pcm and then mistakenly writing smaller than intended sound samples because they assumed a different buffer size. I don't know if this applies to newpcm, but it sounds like the same symptoms. Check the -current mailing list archives for pcm0 and xgalaga. Chris Giordano cgiordano@ids.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 19:54:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A270A154D4 for ; Tue, 11 Jan 2000 19:54:39 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA66873; Tue, 11 Jan 2000 19:54:33 -0800 (PST) (envelope-from dillon) Date: Tue, 11 Jan 2000 19:54:33 -0800 (PST) From: Matthew Dillon Message-Id: <200001120354.TAA66873@apollo.backplane.com> To: "Dave J. Boers" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Still system hangs, but different References: <20000111131010.A317@relativity.student.utwente.nl> <20000111172846.A361@relativity.student.utwente.nl> <200001111821.KAA39855@apollo.backplane.com> <20000111224639.B720@relativity.student.utwente.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Tue, Jan 11, 2000 at 10:21:48AM -0800, Matthew Dillon wrote: :> Everyone, make sure you are using at least version 1.47 of :> ffs_softdep.c. : :I have. Wait a sec. I've reviewed all the messages from you and I think something got mixed together. I'm not convinced that your particular problems are softupdates related. I recommend turning off softupdates entirely for a few days to find out. I recommend enabling DDB in the kernel config. The next time it locks up switch to the console (if you were in X) - which should work - and then ctl-alt-esc into DDB. From there do a 'ps' and see if any processes are stuck in weird states. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 20:12:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 6E378154E0; Tue, 11 Jan 2000 20:12:29 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id UAA73215; Tue, 11 Jan 2000 20:12:28 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id UAA37043; Tue, 11 Jan 2000 20:12:14 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001120412.UAA37043@realtime.exit.com> Subject: Re: neomagic 256av/256zx audio In-Reply-To: <20000111085745.13F441CA0@overcee.netplex.com.au> from Peter Wemm at "Jan 11, 2000 04:57:45 pm" To: peter@netplex.com.au (Peter Wemm) Date: Tue, 11 Jan 2000 20:12:14 -0800 (PST) Cc: frank@exit.com, nsayer@FreeBSD.ORG, gandalf@vilnya.demon.co.uk (Cameron Grant), current@FreeBSD.ORG Reply-To: frank@exit.com 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > Try changing the 'device pcm0 at .....' to this: > > options PNPBIOS > device pcm0 > > with *no* 'at isa?'. See what happens. If it shows up in the pnp id tags but > isn't recognized, show us the 'unknown*' lines from dmesg. Tried that. The config and dmesg output follows. (It didn't work.) (Irrelevant bits deleted.) options PNPBIOS device pcm0 Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Tue Jan 11 19:14:54 PST 2000 frank@auton.exit.com:/usr/local/src/sys/compile/AUTON Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (397.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 134152192 (131008K bytes) sio0: gdb debugging port avail memory = 126783488 (123812K bytes) Preloaded elf kernel "kernel" at 0xc0312000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: mem 0xfec00000-0xfecfffff,0xfe800000-0xfebfffff,0xfd000000-0xfdffffff at device 0.0 on pci1 pcm0: this is a non-ac97 NM256AV, not attaching chip1: mem 0xfe700000-0xfe7fffff,0xfe000000-0xfe3fffff irq 11 at device 0.1 on pci1 pcic-pci0: at device 4.0 on pci0 pcic-pci1: at device 4.1 on pci0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xfcd0-0xfcdf at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 uhci0: port 0xfce0-0xfcff irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: port 0x2180-0x218f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 2180 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 8000 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 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <4 virtual consoles, flags=0x200> pcic: polling, can't alloc 0 pcic: polling, can't alloc 0 pcic0: on isa0 pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A 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/7 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port unknown0: at port 0x80,0x401-0x407 iomem 0xfff80000-0xffffffff on isa0 unknown1: at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown: can't assign resources unknown2: at port 0x40-0x43 irq 0 on isa0 unknown3: at port 0x70-0x71,0x72-0x73 irq 8 on isa0 unknown4: at iomem 0-0x9ffff,0xdc000-0xfffff,0x100000-0x7ffffff on isa0 unknown: can't assign resources unknown5: at port 0xf0-0xff irq 13 on isa0 unknown: can't assign resources unknown6: at port 0xcf8-0xcff on isa0 unknown: can't assign resources unknown7: on isa0 unknown: can't assign resources unknown: can't assign resources unknown8: at port 0x220-0x22f,0x530-0x537,0x388-0x38f,0x320-0x321 irq 5 drq 0,1 on isa0 unknown: can't assign resources unknown: can't assign resources ad0: ATA-4 disk at ata0 as master ad0: 4645MB (9514260 sectors), 10068 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, WDMA2 acd0: Reads: CD-R, CD-RW, CD-DA stream acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-RW 120mm data disc loaded, unlocked Mounting root from ufs:/dev/ad0s2a pccard: card inserted, slot 0 pccard: card inserted, slot 1 sio1 at port 0x2f8-0x2ff irq 3 slot 0 on pccard0 sio1: type 16550A ep0: No irq?! -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 20:33:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust175.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 74EEC14F2D; Tue, 11 Jan 2000 20:33:12 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Tue, 11 Jan 2000 23:33:12 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Bruce Evans Cc: Stephen McKay , freebsd-current@FreeBSD.ORG, dt@FreeBSD.ORG Subject: Re: Crash from ^T during heavy paging In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Bruce Evans wrote: > I broke calcru() with the monotonicity fixes (kern_resource.c rev.1.45 > (1999/03/13). Accessing p->p_stats at interrupt time is only valid if > p == curproc. > > Fix: move the new monotonicity fields from struct pstats to struct > proc. I only put them in struct pstats because they logically go with > some fields in struct rusage. > > P_INMEM is probably not supposed to work in interrupt contexts. > Checking it in ttyinfo() is a wrong fix for the bug in calcru(). It > was committed in tty.c rev.1.119 (1999/05/22). Do you want to do this work, or shall I take out a bit of time and do it? I'm wondering since quite often when someone fixes something, you've got a similar fix already sitting in your local tree :) > > Bruce -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 20:48:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 70EFA14F7E; Tue, 11 Jan 2000 20:48:11 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@pm3a-14.cybcon.com [205.147.75.143]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id UAA25374; Tue, 11 Jan 2000 20:46:55 -0800 (PST) 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: <200001120238.MAA77235@mail.theinternet.com.au> Date: Tue, 11 Jan 2000 20:48:36 -0800 (PST) From: William Woods To: Andrew Kenneth Milton Subject: Re: PPP connections die in current.... Cc: brian@hak.lan.Awfulhak.org, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, (Brian Somers) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How do I disable compression On 12-Jan-00 Andrew Kenneth Milton wrote: > +----[ Brian Somers ]--------------------------------------------- >| > Running 4.0 -current as of today.....on a DEC Alphaststion 233 when I dial >| > out >| > I connect for about 30 seconds then it dies...here is a copy of the >| > ppp.log >| [.....] >| >| Well, you're receiving data from the peer, but the peer is not >| sending any response to your config request. From what I can see, >| ppp is behaving exactly right. >| >| I have no idea what your ISP is expecting - he's sending exactly the >| same REQ as you are. >| >| You could try ``set accmap 000a0000'', but I'll bet it won't help. I >| think you're stuck with asking your ISP to tell you what their side >| thinks it's doing. You could also try ``set log +physical'' to see >| if anything funny is being read from the device and dropped, but >| again I expect nada :-( > > Try disabling compression. I've seen this before also, when ppp was > trying to talk to pppd. > > I think it's specifically related to DEFLATE compression, it was a while > ago now that I saw it. > > -- > Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton > The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | > ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon > PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message ---------------------------------- E-Mail: William Woods Date: 11-Jan-00 Time: 20:47:43 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 21:48:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 2E1F614FBE for ; Tue, 11 Jan 2000 21:48:38 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id WAA02422; Tue, 11 Jan 2000 22:48:28 -0700 (MST) Received: from ip-83-071.prc.primenet.com(207.218.83.71), claiming to be "pinyon.org" via SMTP by smtp03.primenet.com, id smtpdAAAg6aGSe; Tue Jan 11 22:48:21 2000 Received: from chomsky.Pinyon.ORG (localhost [127.0.0.1]) by pinyon.org (Postfix) with ESMTP id 436AB61; Tue, 11 Jan 2000 22:48:25 -0700 (MST) X-Mailer: exmh version 2.1.0 09/18/1999 To: Matthew Dillon Cc: "Dave J. Boers" , freebsd-current@FreeBSD.ORG Subject: Re: Still system hangs, but different In-Reply-To: Message from Matthew Dillon of "Tue, 11 Jan 2000 19:54:33 PST." <200001120354.TAA66873@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 22:48:25 -0700 From: "Russell L. Carter" Message-Id: <20000112054825.436AB61@pinyon.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG % %: %:On Tue, Jan 11, 2000 at 10:21:48AM -0800, Matthew Dillon wrote: %:> Everyone, make sure you are using at least version 1.47 of %:> ffs_softdep.c. %: %:I have. % % Wait a sec. I've reviewed all the messages from you and I think something % got mixed together. I'm not convinced that your particular problems % are softupdates related. I recommend turning off softupdates entirely % for a few days to find out. Oh they are quite surely softupdates related. I got the "X still sorta works but anything that touches the disk wedges" flu today on a very current current. Triggered by a cc build on (soft) linked filesystem, cured by reverting back a week or so. And yes, it is quite certainly v. 1.47 and ata. NBD..., if it was a real barrier to progress I'd disable softupdates. Regards, Russell % I recommend enabling DDB in the kernel config. The next time it locks % up switch to the console (if you were in X) - which should work - and % then ctl-alt-esc into DDB. From there do a 'ps' and see if any processes % are stuck in weird states. % % -Matt % Matthew Dillon % % % %To Unsubscribe: send mail to majordomo@FreeBSD.org %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 23: 3:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A198F150AF for ; Tue, 11 Jan 2000 23:03:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA67832; Tue, 11 Jan 2000 23:03:27 -0800 (PST) (envelope-from dillon) Date: Tue, 11 Jan 2000 23:03:27 -0800 (PST) From: Matthew Dillon Message-Id: <200001120703.XAA67832@apollo.backplane.com> To: "Russell L. Carter" Cc: "Dave J. Boers" , freebsd-current@FreeBSD.ORG Subject: Re: Still system hangs, but different References: <20000112054825.436AB61@pinyon.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :%:I have. :% :% Wait a sec. I've reviewed all the messages from you and I think something :% got mixed together. I'm not convinced that your particular problems :% are softupdates related. I recommend turning off softupdates entirely :% for a few days to find out. : :Oh they are quite surely softupdates related. : :I got the "X still sorta works but anything that touches the disk wedges" :flu today on a very current current. Triggered by a cc build on :(soft) linked filesystem, cured by reverting back a week or so. : :And yes, it is quite certainly v. 1.47 and ata. : :NBD..., if it was a real barrier to progress I'd disable softupdates. : :Regards, :Russell I think what we need to concentrate on is figuring out exactly what is being wedged on. Hence my DDB suggestion below. Reverting to an old -current doesn't guarentee that it's softupdates. If you turn off softupdates with tunefs on the filesystems and see if it occurs with a new kernel that will tell us for sure. (But the DDB suggestion is more important, that will tell us exactly what is going on). :% I recommend enabling DDB in the kernel config. The next time it locks :% up switch to the console (if you were in X) - which should work - and :% then ctl-alt-esc into DDB. From there do a 'ps' and see if any processes :% are stuck in weird states. :% -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 23: 9:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 96DF714D77 for ; Tue, 11 Jan 2000 23:09:33 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id XAA05255; Tue, 11 Jan 2000 23:32:50 -0800 (PST) Date: Tue, 11 Jan 2000 23:32:50 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: "Russell L. Carter" , "Dave J. Boers" , freebsd-current@FreeBSD.ORG Subject: Re: Still system hangs, but different Message-ID: <20000111233250.R9397@fw.wintelcom.net> References: <20000112054825.436AB61@pinyon.org> <200001120703.XAA67832@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001120703.XAA67832@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Jan 11, 2000 at 11:03:27PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000111 23:27] wrote: > :%:I have. > :% > :% Wait a sec. I've reviewed all the messages from you and I think something > :% got mixed together. I'm not convinced that your particular problems > :% are softupdates related. I recommend turning off softupdates entirely > :% for a few days to find out. > : > :Oh they are quite surely softupdates related. > : > :I got the "X still sorta works but anything that touches the disk wedges" > :flu today on a very current current. Triggered by a cc build on > :(soft) linked filesystem, cured by reverting back a week or so. > : > :And yes, it is quite certainly v. 1.47 and ata. > : > :NBD..., if it was a real barrier to progress I'd disable softupdates. > : > :Regards, > :Russell > > I think what we need to concentrate on is figuring out exactly what > is being wedged on. Hence my DDB suggestion below. > > Reverting to an old -current doesn't guarentee that it's softupdates. > If you turn off softupdates with tunefs on the filesystems and see > if it occurs with a new kernel that will tell us for sure. (But the > DDB suggestion is more important, that will tell us exactly what is > going on). I'm finding it easy to reboot a box by simply doing a cvsup and downloading a repo, I'm recompiling everything right now without softupdates but if you wanted what seems to be an easy to reproduce crash, try checking out the postgresql repo via cvsup. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 23:14:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from gw.one.com.au (gw.one.com.au [203.18.85.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D8CC14F17 for ; Tue, 11 Jan 2000 23:14:38 -0800 (PST) (envelope-from MAX@one.com.au) Received: from one.com.au (pxx.local [10.18.85.1]) by gw.one.com.au (8.9.2/8.9.2) with SMTP id RAA03988 for freebsd-current@freebsd.org; Wed, 12 Jan 2000 17:14:34 +1000 (EST) (envelope-from MAX@one.com.au) Date: Wed, 12 Jan 2000 17:14:34 +1000 (EST) From: MAX@one.com.au Message-Id: <200001120714.RAA03988@gw.one.com.au> Subject: uknown error Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To:freebsd-current@freebsd.org Hi all, I am trying to compile this database programme - mumps10freebsd32x86.tgz , ("MUMPS" can be download from www.mumps.org) which currently works only on i386 FreeBSD 3.2, to an Alpha machine running on FreeBSD 4.0 CURRENT-20000101. The Alpha consists of Digital Alphaserver 200 4/166. Making all in compile cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c dollar.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c eval.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c localvar.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c parse.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c routine.c Making all in database cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c db_buffer.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c db_daemon.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c db_get.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c db_ic.c db_ic.c: In function `ic_map': db_ic.c:557: warning: cast from pointer to integer of different size db_ic.c:557: warning: cast from pointer to integer of different size cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c db_kill.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c db_locate.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c db_main.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c db_set.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c db_uci.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c db_util.c db_util.c: In function `Copy_data': db_util.c:391: warning: cast from pointer to integer of different size db_util.c:392: warning: cast from pointer to integer of different size db_util.c: In function `Allign_record': db_util.c:447: warning: cast from pointer to integer of different size db_util.c:448: warning: cast from pointer to integer of different size cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c db_view.c Making all in init cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c init_create.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c init_run.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c init_start.c init_start.c: In function `INIT_Start': init_start.c:194: warning: cast from pointer to integer of different size init_start.c:194: warning: cast to pointer from integer of different size Making all in runtime cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c runtime_attn.c runtime_attn.c: In function `DoInfo': runtime_attn.c:89: warning: int format, different type arg (arg 3) cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c runtime_buildmvar.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c runtime_debug.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c runtime_func.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c runtime_pattern.c cc -I../include -Wall -g -O0 -fvolatile -DPARANOID -DTESTING -c runtime_run.c /tmp/ccaN3150.s: Assembler messages: /tmp/ccaN3150.s:27822: Error: unknown opcode `fnstenv' /tmp/ccaN3150.s:27857: Error: unknown opcode `fldenv' *** Error code 1 Stop in /usr/home/maxy/mumps/runtime. *** Error code 1 Stop in /usr/home/maxy/mumps. a snip from the "warning" files db_ic.c SemOp(SEM_GLOBAL, -curr_lock); // free lock c++; // point at next off = 0; // now start at 0 if (flag == -3) // daemon? line 557: { systab->vol[volnum - 1]->upto = ((u_int) e - (u_int) c) << 3; } db_util.c if (isdata) // if data { if (c->len == NODE_UNDEFINED) // junk record? { continue; // ignore it } } else // if a pointer line 391: { if ((int) c & 3) // if not alligned line 392: { c = (cstring *) &c->buf[2 - ((int) c & 3)]; // allign } if ((*(int *) c) == PTR_UNDEFINED) // see if that's junk { continue; // ignore it } } db_util.c //----------------------------------------------------------------------------- // Function: Allign_record // Descript: Ensure that record is on a four byte boundary // Input(s): none // Return: none // Note: Must only be called for pointer/directory blocks // void Allign_record() // allign record (int) line 447: { if ((int) record & 3) // if not alligned line 448: { record = (cstring *) &record->buf[2 - ((int) record & 3)]; // allign } return; // exit } init_start.c bzero(systab, share_size); // zot the lot systab->jobtab (jobtab *)&systab->last_blk_used[jobs + 1]; // setup jobtab pointer systab->maxjob = jobs; // save max jobs systab->start_user = (int) getpid(); // remember who started this systab->lockstart (void *)((void *)systab->jobtab + (sizeof(jobtab)*jobs)); //locktab systab->locksize = locksize; // the size systab->lockhead = NULL; // no locks currently systab->lockfree = (locktab *) systab->lockstart; // free space systab->lockfree->fwd_link = NULL; // only one systab->lockfree->size = locksize; // the whole space systab->lockfree->job = -1; // means free systab->vol[0] (vol_def *) ((void *)systab + sjlt_size);// jump to start of // volume set memory systab->vol[0]->vollab (label_block *) ((void *)systab->vol[0] + sizeof(vol_def)); // and point to label blk systab->vol[0]->map (void*)((void *)systab->vol[0]->vollab + sizeof(label_block)); // and point to map systab->vol[0]->first_free systab->vol[0]->map; // init first free systab->vol[0]->gbd_head (gbd *) ((void *)systab->vol[0]->vollab + hbuf[2]); // gbds systab->vol[0]->num_gbd = n_gbd; // number of gbds systab->vol[0]->global_buf (void *) &systab->vol[0]->gbd_head[n_gbd]; //glob buffs line 194: systab->vol[0]->zero_block (void *)((int)systab->vol[0]->global_buf+(gmb*MBYTE)); // pointer to zero blk systab->vol[0]->rbd_head (void *) ((void*)systab->vol[0]->zero_block + hbuf[3]); //rbds systab->vol[0]->rbd_end ((void *)systab + share_size); // end of share systab->vol[0]->shm_id = shar_mem_id; // set up share id systab->sem_id = sem_id; // set up semaphore id systab->vol[0]->map_dirty_flag = 0; // clear dirty map flag runtime_attn.c // DoInfo() - look after a control T // void DoInfo() { int i; // a handy int int j; // and another char ct[400]; // some space for control t char *p; // a handy pointer mvar *var; // and another bcopy("\033\067\033[99;1H",ct,9); // start off i = 9; // next char line 89: i += sprintf(&ct[i],"%d", partab.jobtab - systab->jobtab + 1); i += sprintf(&ct[i]," (%d) ", partab.jobtab->pid); p = (char *) &partab.jobtab->dostk[partab.jobtab->cur_do].rounam; // point at routine name for (j = 0; (j < 8) && (p[j]); ct[i++] = p[j++]); // copy it i += sprintf(&ct[i]," Cmds: %d ", partab.jobtab->commands); i += sprintf(&ct[i],"Grefs: %d ", partab.jobtab->grefs); var = &partab.jobtab->last_ref; // point at $R if (var->name.var_cu[0] != '\0') // something there? i += UTIL_String_Mvar(var, &ct[i], 32767); // decode it if (i > 89) i = 89; // fit on terminal bcopy("\033\133\113\033\070\0", &ct[i], 6); // and the trailing bit fprintf(stderr, "%s", ct); // output it return; // all done } Thanks for your help. Max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 23:21:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id BC0AA14D96 for ; Tue, 11 Jan 2000 23:21:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA17118 for ; Tue, 11 Jan 2000 23:21:24 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA86971 for current@FreeBSD.ORG; Tue, 11 Jan 2000 23:21:23 -0800 (PST) (envelope-from obrien) Date: Tue, 11 Jan 2000 23:21:23 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: Additional option to ls -l for large files Message-ID: <20000111232123.B86929@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001120201.SAA26378@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001120201.SAA26378@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Tue, Jan 11, 2000 at 06:01:53PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 06:01:53PM -0800, Rodney W. Grimes wrote: > > (ie, whatever letters you use, please just divide the values > > by 1000 instead of 1024). > > Please don't, there is already far to much precedence in both the > computing world and other commands (df -k and du -k come to mind Don't forget our new ``df -h''. I'm working with mharo to get "-h" added to `du'. I guess we should add it to `ls' too. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 23:30: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 99D6714DE0; Tue, 11 Jan 2000 23:29:48 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id SAA04179; Wed, 12 Jan 2000 18:29:21 +1100 Date: Wed, 12 Jan 2000 18:29:18 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Brian Fundakowski Feldman Cc: Stephen McKay , freebsd-current@FreeBSD.org, dt@FreeBSD.org Subject: Re: Crash from ^T during heavy paging In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Brian Fundakowski Feldman wrote: > On Tue, 11 Jan 2000, Bruce Evans wrote: > > ... > > Fix: move the new monotonicity fields from struct pstats to struct > > proc. I only put them in struct pstats because they logically go with > > some fields in struct rusage. > > ... > > Do you want to do this work, or shall I take out a bit of time and do > it? I'm wondering since quite often when someone fixes something, > you've got a similar fix already sitting in your local tree :) Please do the work, but send it to me for review. I didn't have a fix for this particular problem until after seeing your first mail about it. It didn't make sense for P_INMEM to be so apparently broken without it causing problems until recently. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 23:50:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta3.snfc21.pbi.net (mta3.snfc21.pbi.net [206.13.28.141]) by hub.freebsd.org (Postfix) with ESMTP id 229E015121 for ; Tue, 11 Jan 2000 23:50:57 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.117.93]) by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FO700JLZPPQIK@mta3.snfc21.pbi.net> for current@FreeBSD.ORG; Tue, 11 Jan 2000 23:49:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 82C1E9184E; Tue, 11 Jan 2000 23:49:11 -0800 (PST) Date: Tue, 11 Jan 2000 23:49:11 -0800 (PST) From: Alex Zepeda Subject: Re: Additional option to ls -l for large files In-reply-to: <387BC4A6.3B7DF57A@cvzoom.net> To: Donn Miller Cc: current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Donn Miller wrote: > Or else we could put both in. There could be either a command-line > option or env variable set that selects between decimal (true metric) > or powers of two (computer metric, or whatever). What about making ls sensitive to $BLOCKSIZE, but only if enabled with a command line option? This way you could get sizes listed in 2.5 megabytes if you so desired... - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 11 23:54:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 969661501B for ; Tue, 11 Jan 2000 23:54:48 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 3E85A1DA7; Wed, 12 Jan 2000 08:54:48 +0100 (CET) Date: Wed, 12 Jan 2000 08:54:48 +0100 From: "Dave J. Boers" To: Matthew Dillon Cc: rcarter@pinyon.org, freebsd-current@FreeBSD.ORG Subject: Re: Still system hangs, but different Message-ID: <20000112085447.A1773@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000111131010.A317@relativity.student.utwente.nl> <20000111172846.A361@relativity.student.utwente.nl> <200001111821.KAA39855@apollo.backplane.com> <20000111224639.B720@relativity.student.utwente.nl> <200001120354.TAA66873@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001120354.TAA66873@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Jan 11, 2000 at 07:54:33PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 07:54:33PM -0800, Matthew Dillon wrote: > Wait a sec. I've reviewed all the messages from you and I think something > got mixed together. I'm not convinced that your particular problems > are softupdates related. I recommend turning off softupdates entirely > for a few days to find out. Hmmm, interesting. I wonder what makes you think that. Could you elaborate? > I recommend enabling DDB in the kernel config. The next time it locks > up switch to the console (if you were in X) - which should work - and > then ctl-alt-esc into DDB. From there do a 'ps' and see if any processes > are stuck in weird states. Allright. I've included options DDB and KTRACE in my kernel. I will disable softupdates on all my filesystems and let the system run for a while. We'll see what happens. Besides, if the SCSI problem and these latest system hangs seem related to you, then please note that the SCSI related hang was of an altogether different nature (complete system hang instead of just i/o) and (important) I've removed the SCSI disk from the system (and put in into another system for separate testing) before I ever had version 1.47 of ffs_softdep.c. I've not seen any log messages from the scsi driver since I removed the drive. My system is and has always been running primarily from my IDE disk, though /usr/src and /usr/obj used to reside on the scsi disk. Regards, Dave Boers. -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 0: 3:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 796F415326 for ; Wed, 12 Jan 2000 00:03:18 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-14.iptelecom.net.ua [212.9.227.14]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA03617 for ; Wed, 12 Jan 2000 10:07:11 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id KAA36944 for ; Wed, 12 Jan 2000 10:02:02 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <387C34E5.9E9840AF@altavista.net> Date: Wed, 12 Jan 2000 10:01:42 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: C++ exceptions doesn't work in shared libraries References: <387B1603.E353CD09@altavista.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > Hi, > > It seems than long-standing problem (see PR dated May '97: > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=3441) with C++ exceptions in shared > libraries is still here. It affects both -current and -stable branches and > prevents some modern software (Mico for example) from functioning properly. Is there are any compiler guys to address my question or not? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 0:15:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 3F33314F00 for ; Wed, 12 Jan 2000 00:15:40 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id JAA16471 for ; Wed, 12 Jan 2000 09:15:36 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id JAA17098 for ; Wed, 12 Jan 2000 09:15:32 +0100 (MEZ) Date: Wed, 12 Jan 2000 09:15:32 +0100 From: Martin Blapp To: current@freebsd.org Subject: move portmap(8) from /usr/sbin to /sbin Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I think we should move portmap(8) to /sbin for the following reason: portmap(8) and therefore mountd(8) should be started before the nfs filesystems get mounted. But because portmap(8) is in /usr/sbin , users with a nfs mounted /usr filesystem or with diskless filesystems will have big problems. This will fix loopback and local mounts in fstab. Untill now this has not been possible because of the above reasons. Btw: Linux also has portmap(8) installed in /sbin. I'm prepared for a big fight :) Can you give me any arguments against this change ? Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 0:24:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id BB040154C8 for ; Wed, 12 Jan 2000 00:24:17 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id AAA27519; Wed, 12 Jan 2000 00:24:01 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001120824.AAA27519@gndrsh.dnsmgr.net> Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: from Martin Blapp at "Jan 12, 2000 09:15:32 am" To: mb@imp.ch (Martin Blapp) Date: Wed, 12 Jan 2000 00:24:01 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi, > > I think we should move portmap(8) to /sbin for the following reason: > > portmap(8) and therefore mountd(8) should be started before > the nfs filesystems get mounted. But because portmap(8) is in > /usr/sbin , users with a nfs mounted /usr filesystem or with > diskless filesystems will have big problems. > > This will fix loopback and local mounts in fstab. Untill now > this has not been possible because of the above reasons. Btw: > Linux also has portmap(8) installed in /sbin. > > I'm prepared for a big fight :) Can you give me any arguments > against this change ? It makes no since... Why would a machine that mounts /usr over nfs need to export filesystems? If it's got enough disk space to make it worth exporting stuff from the box it surely has enough space for it's own copy of /usr. You only need portmap and mountd to _export_ nfs, not to mount them. Orbit.hpc1.com:root{208}# ps ax | grep mount Orbit.hpc1.com:root{209}# ps ax | grep port Orbit.hpc1.com:root{210}# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 63503 21519 36904 37% / /dev/da0s1d 63503 458 57965 1% /tmp /dev/da0s1e 63503 483 57940 1% /var /dev/da0s1f 127023 82030 34832 70% /usr /dev/da0s1g 381103 251170 99445 72% /usr/src /dev/da0s1h 1233503 208025 926798 18% /A procfs 4 4 0 100% /proc 198.145.92.8:/A 1309170 1127463 76974 94% /mnt -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 0:32: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 5F1D514A0B for ; Wed, 12 Jan 2000 00:32:00 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id JAA16882; Wed, 12 Jan 2000 09:31:57 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id JAA19664; Wed, 12 Jan 2000 09:31:55 +0100 (MEZ) Date: Wed, 12 Jan 2000 09:31:54 +0100 From: Martin Blapp To: "Rodney W. Grimes" Cc: current@FreeBSD.ORG Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: <200001120824.AAA27519@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > portmap(8) and therefore mountd(8) should be started before > > the nfs filesystems get mounted. But because portmap(8) is in > > /usr/sbin , users with a nfs mounted /usr filesystem or with > > diskless filesystems will have big problems. I mean, that if I do the change of startup-order, diskless installations will be broken. > > This will fix loopback and local mounts in fstab. Untill now > > this has not been possible because of the above reasons. Btw: > > Linux also has portmap(8) installed in /sbin. > You only need portmap and mountd to _export_ nfs, not to mount > them. For a normal installation this is ok, but as I said, diskless installs ... Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 0:42:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta2.rcsntx.swbell.net (mta2.rcsntx.swbell.net [151.164.30.26]) by hub.freebsd.org (Postfix) with ESMTP id D9E5514FD0 for ; Wed, 12 Jan 2000 00:42:12 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta2.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FO700L32S63D4@mta2.rcsntx.swbell.net> for current@FreeBSD.ORG; Wed, 12 Jan 2000 02:42:04 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id CAA08187; Wed, 12 Jan 2000 02:42:17 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Wed, 12 Jan 2000 02:42:12 -0600 From: Chris Costello Subject: Re: Any Wine or Mozilla hackers here? In-reply-to: <387BC701.61C7EDF6@cvzoom.net> To: Donn Miller Cc: current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000112024212.B2463@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <387BC701.61C7EDF6@cvzoom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000, Donn Miller wrote: > I figured I'd address these two issues in one posting here. Shouldn't they be addressed on -hackers? That's sort of what it's for -- hackers of FreeBSD and software that runs on FreeBSD (described or not, that's how it seems to be these days). -- |Chris Costello |A closed mouth gathers no feet. `---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 0:44:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id DA1D514F00 for ; Wed, 12 Jan 2000 00:44:39 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id AAA27579; Wed, 12 Jan 2000 00:44:28 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001120844.AAA27579@gndrsh.dnsmgr.net> Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: from Martin Blapp at "Jan 12, 2000 09:31:54 am" To: mb@imp.ch (Martin Blapp) Date: Wed, 12 Jan 2000 00:44:28 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > portmap(8) and therefore mountd(8) should be started before > > > the nfs filesystems get mounted. But because portmap(8) is in > > > /usr/sbin , users with a nfs mounted /usr filesystem or with > > > diskless filesystems will have big problems. > > I mean, that if I do the change of startup-order, diskless > installations will be broken. > > > > This will fix loopback and local mounts in fstab. Untill now > > > this has not been possible because of the above reasons. Btw: > > > Linux also has portmap(8) installed in /sbin. > > > You only need portmap and mountd to _export_ nfs, not to mount > > them. > > For a normal installation this is ok, but as I said, diskless > installs ... Lets see, your booting diskless during the install, which means you have no disk to export until you have fdisk/newfs'ed one, your not going to get very far without /usr in this process. So no disk, so just what is it that you are exporting??? -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 0:46:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A76B154DC for ; Wed, 12 Jan 2000 00:46:24 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA68588; Wed, 12 Jan 2000 00:46:15 -0800 (PST) (envelope-from dillon) Date: Wed, 12 Jan 2000 00:46:15 -0800 (PST) From: Matthew Dillon Message-Id: <200001120846.AAA68588@apollo.backplane.com> To: Martin Blapp Cc: "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: move portmap(8) from /usr/sbin to /sbin References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> > portmap(8) and therefore mountd(8) should be started before :> > the nfs filesystems get mounted. But because portmap(8) is in :> > /usr/sbin , users with a nfs mounted /usr filesystem or with :> > diskless filesystems will have big problems. : :I mean, that if I do the change of startup-order, diskless :installations will be broken. : :> > This will fix loopback and local mounts in fstab. Untill now :> > this has not been possible because of the above reasons. Btw: :> > Linux also has portmap(8) installed in /sbin. : :> You only need portmap and mountd to _export_ nfs, not to mount :> them. : :For a normal installation this is ok, but as I said, diskless :installs ... : :Martin I do not like the idea of moving portmap or mountd. An NFS client should not have to run either, *even* for diskless boot. What's all this about loopback mounts in fstab about? What does that have to do with diskless startup? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 1: 6: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 1A97814A0B for ; Wed, 12 Jan 2000 01:05:52 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id KAA17856; Wed, 12 Jan 2000 10:05:44 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id KAA25143; Wed, 12 Jan 2000 10:05:42 +0100 (MEZ) Date: Wed, 12 Jan 2000 10:05:42 +0100 From: Martin Blapp To: Matthew Dillon Cc: "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: <200001120846.AAA68588@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > should not have to run either, *even* for diskless boot. > > What's all this about loopback mounts in fstab about? What does > that have to do with diskless startup? Ok. I just rethought everything. It seems that a move is unnecessary because: - Sharity light and cfs are started from /usr/loca/etc/rc.d - diskless stations do not have anything to export So are there any problems with the order change in /etc/rc.network (moving portmap and mountd to network pass_1) you can imagine ? Thanks for the fast response and your ideas. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 1:23:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 1C6B514FC6 for ; Wed, 12 Jan 2000 01:23:27 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id BAA27677; Wed, 12 Jan 2000 01:23:14 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001120923.BAA27677@gndrsh.dnsmgr.net> Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: from Martin Blapp at "Jan 12, 2000 10:05:42 am" To: mb@imp.ch (Martin Blapp) Date: Wed, 12 Jan 2000 01:23:14 -0800 (PST) Cc: dillon@apollo.backplane.com (Matthew Dillon), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi, > > > should not have to run either, *even* for diskless boot. > > > > What's all this about loopback mounts in fstab about? What does > > that have to do with diskless startup? > > Ok. I just rethought everything. It seems that a move is > unnecessary because: > > - Sharity light and cfs are started from /usr/loca/etc/rc.d > - diskless stations do not have anything to export > > So are there any problems with the order change in /etc/rc.network > (moving portmap and mountd to network pass_1) you can imagine ? They don't logically belong in pass1, which is for bringing up the network logical layer. These run above the logical layer. Also moving them to pass1 would bring up nfs exports before we brought up nfs mounts. syslogd would not be running to catch errors, etc. Moving things in /etc/rc is not to be taken lightly, it has taken 10 years to get what we have there in a shape that just DTRT for 99% of the folks. Perhaps if you can give us some specifics on exactly what it is that your having problems doing and/or what it is that you are trying to do we can come up with a correct solution. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 1:42: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from fep01-svc.mail.telepac.pt (fep01-svc.mail.telepac.pt [194.65.5.200]) by hub.freebsd.org (Postfix) with ESMTP id BA9E7154F3 for ; Wed, 12 Jan 2000 01:42:03 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: from manecao.tafkap.priv ([212.55.187.8]) by fep02-svc.mail.telepac.pt (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000110232557.BPHK703.fep02-svc.mail.telepac.pt@manecao.tafkap.priv>; Mon, 10 Jan 2000 23:25:57 +0000 Content-Length: 1338 Message-ID: X-Mailer: XFMail 1.3.1 [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: <200001102217.OAA30472@apollo.backplane.com> Date: Mon, 10 Jan 2000 23:23:32 -0000 (GMT) From: Joao Pedras To: Matthew Dillon Subject: Re: freezing... update to 1.45 of ffs_softdep.c Cc: freebsd-current@FreeBSD.ORG, Alfred Perlstein Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm am not using neither softupdates nor scsi on this machine only ide, nic de, s3 Matthew Dillon wrote: >:> I would like to know if the person reporting the getblk lockup (I think >:> it was Poul) sees that problem solved with the vinum fix that Alfred >:> posted in regards to or whether we still have an open issue. >: >:still a problem, just got snagged a few moments ago, there's a traceback >:already on the way. :) >: >:-Alfred > > Is this backed by the ata driver too? > > If so, if either you or Poul could backoff to the wd driver and see > if the problem continues, I would appreciate it. > > -Matt > Matthew Dillon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ^\ /^ O O ----------------------------------------o00-(_)-00o-------------------------- Philosophy will clip an angel's wings. -- John Keats ----------------------------------------------------------------------------- PGP key available upon request or may be cut at http://pedras.webvolution.net/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 3:22:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 7951914F2D for ; Wed, 12 Jan 2000 03:22:51 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id MAA10971; Wed, 12 Jan 2000 12:22:43 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Wed, 12 Jan 2000 12:09:11 +0100 To: Mike Fisher , "Rodney W. Grimes" From: Brad Knowles Subject: Re: Additional option to ls -l for large files Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:57 PM -0500 2000/1/11, Mike Fisher wrote: > Why not use Knuth's (good) suggestion for differentiating these prefixes? > > http://www-cs-faculty.stanford.edu/~knuth/news99.html Blech. The prefixes should be aware of the nature of the term to which they are being applied. For bytes, it is natural to use base two exponents, and therefore there should be no confusion between KB = 1024 bytes and km = 1000 meters. I really think it is (or should be) that simple. Now I guess I'm going to have to go devote a web page to this topic and tell people about it. I'm getting really sick and bloody tired of all this BS.... Of course, this is totally unrelated to -current, so follow-ups should be sent to -chat. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 3:23: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 026C215517 for ; Wed, 12 Jan 2000 03:22:57 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id MAA10949; Wed, 12 Jan 2000 12:22:38 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001112314.QAA07511@harmony.village.org> References: <200001112249.OAA25732@gndrsh.dnsmgr.net> <200001112314.QAA07511@harmony.village.org> Date: Wed, 12 Jan 2000 12:02:33 +0100 To: Warner Losh , "Rodney W. Grimes" From: Brad Knowles Subject: Re: Additional option to ls -l for large files Cc: MichaelV@EDIFECS.COM (Michael VanLoon), joerg@cs.waikato.ac.nz, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:14 PM -0700 2000/1/11, Warner Losh wrote: > kB and kiB are the proper abreviations, not KB and KiB. I don't know > if miB or MiB is correct, likely MiB. I always thought it was "k/m/b = 1,000/1,000,000/1,000,000,000" and "K/M/G = 2^10/2^20/2^30". Or was this just some convention I learned somewhere that I mistakenly thought of as an actual accepted rule? Does anyone actually believe that people will actually adopt terms like "Mibabytes"? -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 3:36:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3E1ED14EFB; Wed, 12 Jan 2000 03:36:16 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id DAA11110; Wed, 12 Jan 2000 03:59:47 -0800 (PST) Date: Wed, 12 Jan 2000 03:59:47 -0800 From: Alfred Perlstein To: current@freebsd.org Cc: mckusick@freebsd.org, dillon@freebsd.org Subject: softdep: panic: flush_pagedep_deps: flush 3 failed Message-ID: <20000112035947.T9397@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (kgdb) bt #8 0xc025c1a1 in Debugger (msg=0xc028fc72 "panic") at machine/cpufunc.h:64 #9 0xc015ac04 in panic (fmt=0xc02a0ee0 "flush_pagedep_deps: flush 3 failed") at ../../kern/kern_shutdown.c:552 #10 0xc020441a in flush_pagedep_deps (pvp=0xd8f15da0, mp=0xc1e4c400, diraddhdp=0xc204d5e4) at ../../ufs/ffs/ffs_softdep.c:4248 #11 0xc0203d20 in softdep_sync_metadata (ap=0xd8ed7b6c) at ../../ufs/ffs/ffs_softdep.c:3934 #12 0xc0207da2 in ffs_fsync (ap=0xd8ed7b6c) at ../../ufs/ffs/ffs_vnops.c:249 #13 0xc01fed0c in ffs_truncate (vp=0xd8f15da0, length=512, flags=4, cred=0xc1f4b200, p=0xd8ed4e00) at vnode_if.h:537 #14 0xc020a613 in ufs_direnter (dvp=0xd8f15da0, tvp=0xd8f14860, dirp=0xd8ed7cb8, cnp=0xd8ed7f04, newdirbp=0x0) at ../../ufs/ufs/ufs_lookup.c:842 #15 0xc020e577 in ufs_makeinode (mode=33152, dvp=0xd8f15da0, vpp=0xd8ed7ef0, cnp=0xd8ed7f04) at ../../ufs/ufs/ufs_vnops.c:2159 #16 0xc020bd90 in ufs_create (ap=0xd8ed7e10) at ../../ufs/ufs/ufs_vnops.c:183 #17 0xc020e601 in ufs_vnoperate (ap=0xd8ed7e10) at ../../ufs/ufs/ufs_vnops.c:2283 #18 0xc018b8b0 in vn_open (ndp=0xd8ed7edc, fmode=1539, cmode=384) at vnode_if.h:106 #19 0xc0187b69 in open (p=0xd8ed4e00, uap=0xd8ed7f80) at ../../kern/vfs_syscalls.c:994 #20 0xc026fcaa in syscall (frame={tf_fs = 4390959, tf_es = 3014703, tf_ds = 4390959, tf_edi = 3061976, tf_esi = 384, tf_ebp = 4434788, tf_isp = -655523884, tf_ebx = 2039808, tf_edx = 3061976, tf_ecx = 1429646, tf_eax = 5, tf_trapno = 22, tf_err = 7, tf_eip = 1876306, tf_cs = 31, tf_eflags = 518, tf_esp = 4434768, tf_ss = 47}) at ../../i386/i386/trap.c:1055 #21 0x1ca152 in ?? () This can be reproduced by doing a cvsup to get a new repo, not an update but a clean checkout, twice in the same spot. *default host=postgresql.org *default release=cvs *default delete use-rel-suffix *default base=/home/pgcvs *default prefix=/home/pgcvs pgsql Also, the fix for running out of space, can that be backported to -stable? thanks, -- -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 3:50:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from ccssu.crimea.ua (ccssu.ccssu.crimea.ua [62.244.13.130]) by hub.freebsd.org (Postfix) with ESMTP id 8196415253 for ; Wed, 12 Jan 2000 03:49:59 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by ccssu.crimea.ua (8.9.3/8.9.0) with UUCP id NAA09831; Wed, 12 Jan 2000 13:31:40 +0200 Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id MAA17839; Wed, 12 Jan 2000 12:05:00 +0300 (MSK) Date: Wed, 12 Jan 2000 12:05:00 +0300 From: Alexey Zelkin To: Matthew Dillon Cc: current@FreeBSD.org Subject: Re: vn device strange behaviour Message-ID: <20000112120500.A7221@scorpion.crimea.ua> References: <20000112013234.A28567@scorpion.crimea.ua> <200001120141.RAA65875@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <200001120141.RAA65875@apollo.backplane.com> X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, On Tue, Jan 11, 2000 at 05:41:59PM -0800, Matthew Dillon wrote: > :I just discovered some strange points about using vn devices (files) as > :swap devices. > : > :I have placed below some output gathered with script(1) and now > :some comments. > : > :1) I can easy unconfigure vn device which already mounted as swap device > :and then remove swapfile without any problems. I not sure about behaviour > :of the swapper when it will try to allocate swap from /dev/vn0c. > : > :2) When I am creating small file (about 100k) and try to mount it as swap > :device swapinfo(8) output looks broken. > : > :3) I could not mount three and more vn devices as swap devices. > : > :BTW, I also got strange results once (but I could not reporoduce it later): > :swapinfo(8) shown that I have three swap devices mounted: /dev/wd0s1b, > :/dev/rvn0c and /dev/#46:10. What's that ? I'll try to reproduce it again, > :but ... > : > :Comments ? > > Don't unconfigure a VN device mounted as swap unless you want your > system to die a horrible death. It shouldn't allow it to happen, but > it does and that's a bug. Yep, I think swapon(8) should fail in this case with something like "File is busy". > The first 128K of any swap partition is left alone by the swap subsystem > in order to ensure that the disklabel (if any) is not overwritten. Do > not configure tiny swap spaces -- apart from being useless they will > cause swapinfo to print confusing output. Why swapon(8) not handling that situation ? I mean check for vn device and its file size and then generating fatal error if its size less than 128k. Is it possible ? > By default the kernel is configured to support 4 SWAP partitions. How can I enable more swaps ? > Therefore you can only configure a maximum of 4 SWAP partiions. You > can change this in the kernel config. Note however that setting the > number arbitrarily high will cause a huge amount of KVM to be wasted. > Four is usually enough for anyone. BTW, I have described following porblem: I have one physical swap slice and tried to create three additional swapfiles. But I could not. System allowed me to create only 2 swapfiles, not 3 as you noted above. -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@FreeBSD.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 3:58:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (Postfix) with ESMTP id 4724C14D8D for ; Wed, 12 Jan 2000 03:58:30 -0800 (PST) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id MAA29577 for current@freebsd.org; Wed, 12 Jan 2000 12:58:29 +0100 (CET) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by paula.panke.de.freebsd.org (8.9.3/8.8.8) id MAA00386 for current@freebsd.org; Wed, 12 Jan 2000 12:48:51 +0100 (CET) (envelope-from wosch) Date: Wed, 12 Jan 2000 12:48:51 +0100 From: Wolfram Schneider To: current@freebsd.org Subject: swapper.core Message-ID: <20000112124850.A374@paula.panke.de.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running -current from July 1999. Now I getting a core dump of the swapper daemon (sic!!!) after booting. This is really strange ... a dying swapper and 100MB free memory. I guess it is a interupt conflict with the 3com ethernet card. $ ls -l /swapper.core -rw------- 1 root wheel 8192 Jan 12 12:32 /swapper.core 1 3C5x9 board(s) on ISA found at 0x280 ep0 at port 0x280-0x28f irq 10 on isa0 ep0: aui/utp/bnc[*UTP*] address 00:20:af:05:37:0d ep0 XXX: driver didn't set ifq_maxlen kernel trap 9 with interrupts disabled pid 193 (swapper), uid 0: exited on signal 10 (core dumped) ps -xuawww | grep swap root 0 0.0 0.0 0 0 ?? DLs 28Jan36 0:00.00 (swapper) root 193 0.0 0.0 0 0 ?? Z - 0:00.00 (swapper) -- Wolfram Schneider http://wolfram.schneider.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 4: 4: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (p3E9EBF37.dip0.t-ipconnect.de [62.158.191.55]) by hub.freebsd.org (Postfix) with ESMTP id A1F3C14D1D for ; Wed, 12 Jan 2000 04:04:05 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id OAA97921 for ; Wed, 12 Jan 2000 14:06:56 +0100 (CET) (envelope-from cc@devcon.net) Date: Wed, 12 Jan 2000 14:06:55 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: current@freebsd.org Subject: why is my current so .... stable? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, Sorry, but after my last make world (Tue Jan 11 15:07:18 CET 2000) I didn't have to reboot (ok, once, after the install ;). I'm using softupdates, vinum, smp and scsi, but the instability seems gone. I've caused heavy load on the machine for reasonable long periods, but nothing crashed. -- Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 4:10:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 60A28150AF for ; Wed, 12 Jan 2000 04:10:34 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 9069 invoked from network); 12 Jan 2000 12:10:33 -0000 Received: from lcm97.cvzoom.net (208.230.69.97) by ns.cvzoom.net with SMTP; 12 Jan 2000 12:10:33 -0000 Date: Wed, 12 Jan 2000 07:10:05 -0500 (EST) From: Donn Miller To: Christian Carstensen Cc: current@freebsd.org Subject: Re: why is my current so .... stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, Christian Carstensen wrote: > Sorry, but after my last make world (Tue Jan 11 15:07:18 CET 2000) I > didn't have to reboot (ok, once, after the install ;). I'm using > softupdates, vinum, smp and scsi, but the instability seems gone. > I've caused heavy load on the machine for reasonable long periods, but > nothing crashed. My guess is that once -current gets closer to the release date, it becomes more and more stable. I guess the period of greatest instability occurs somewhere about 1/4 to 1/2 through the -current life cycle. We could do a chart plotting stability vs. time for the life cycle of a given -current. That could help people decide whether or not they want to run -current. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 4:25: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (p3E9EBF37.dip0.t-ipconnect.de [62.158.191.55]) by hub.freebsd.org (Postfix) with ESMTP id 401EF153F7 for ; Wed, 12 Jan 2000 04:25:01 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id OAA20277; Wed, 12 Jan 2000 14:27:50 +0100 (CET) (envelope-from cc@devcon.net) Date: Wed, 12 Jan 2000 14:27:49 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: Donn Miller Cc: current@freebsd.org Subject: Re: why is my current so .... stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, Donn Miller wrote: > My guess is that once -current gets closer to the release date, it becomes > more and more stable. I guess the period of greatest instability occurs > somewhere about 1/4 to 1/2 through the -current life cycle. We could do a > chart plotting stability vs. time for the life cycle of a given > -current. That could help people decide whether or not they want to run > -current. This would be great, but I wonder from what source we could take reliable data about -current's stability. But what I've meant was: I've had these ugly system freezes not perfactly reproducable, but very often. From what I've read on current list, the problems still exist, but not on my system. At least this system runs stable for 1 day now. I'm wondering, why. -- Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 4:50:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4D07F15464 for ; Wed, 12 Jan 2000 04:50:35 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 12 Jan 2000 12:50:34 +0000 (GMT) Date: Wed, 12 Jan 2000 12:50:33 +0000 From: David Malone To: "Rodney W. Grimes" Cc: mb@imp.ch, dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: move portmap(8) from /usr/sbin to /sbin Message-ID: <20000112125033.A51579@walton.maths.tcd.ie> References: <200001120923.BAA27677@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001120923.BAA27677@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Wed, Jan 12, 2000 at 01:23:14AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 01:23:14AM -0800, Rodney W. Grimes wrote: > Also moving them to pass1 would bring up nfs exports before we > brought up nfs mounts. syslogd would not be running to catch Shouldn't nfs exports happen before nfs mounts, so that machines which have nfs interdependencies don't sit there waiting for one another? (I think we've had to change this several times in the FreeBSD rc scripts, I guess the reason it might be the other way around is incase /usr is nfs mounted?) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 5: 3:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.monmouth.com (shell.monmouth.com [209.191.58.1]) by hub.freebsd.org (Postfix) with ESMTP id DB1DE14FC6 for ; Wed, 12 Jan 2000 05:03:11 -0800 (PST) (envelope-from pechter@shell.monmouth.com) Received: (from pechter@localhost) by shell.monmouth.com (8.9.3/8.9.3) id IAA14000 for freebsd-current@freebsd.org; Wed, 12 Jan 2000 08:02:52 -0500 (EST) From: Bill/Carolyn Pechter Message-Id: <200001121302.IAA14000@shell.monmouth.com> Subject: Wired down SCSI devices problem To: freebsd-current@freebsd.org Date: Wed, 12 Jan 2000 08:02:51 -0500 (EST) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I've run into the following problem since about 1/6 or so: Have I missed something obvious, do I need the conical hat here? If so I've got a stool in the corner to sit on. The wired scsi devices no longer configure as such... I'm sure it must be me, since I've seen no messages in -current on this one. The UPDATING file didn't mention anything as well. I've been running -current on this machine since about last March and doing buildworlds every week or two. (And every day or two when work's slow.) I just did another last night. On the old configuration (only thing changed in new configuration is swap of controller key word with device key word...) disks on ncr1 (scbus0) were mapped as da0->5 and disks on ncr0 (scbus1) da10 was to be da10->13. (this gives a name of da[controller#][drive#][slice#][partition#] which is pretty close to the naming convention I used to admin on Pyramid OS/x. Now the drive on ncr1 went from da0 to da7 (which is an unused non-wired floater) and the drive on ncr0 went to da6 (another floater). I attache the relevent parts of the configuration file. I didn't see anything obvious in LINT on this and I tried both the ncr and sym drivers... Old configuration # SCSI DEVICES controller ncr0 controller ncr1 controller scbus0 at ncr1 controller scbus1 at ncr0 # DISK device da0 at scbus0 target 0 # SCSI disk device da1 at scbus0 target 1 # SCSI disk device da2 at scbus0 target 2 # SCSI disk device da3 at scbus0 target 3 # SCSI disk device da4 at scbus0 target 4 # SCSI disk device da5 at scbus0 target 5 # SCSI disk device cd0 at scbus0 target 6 #SCSI cdrom # TAPE device da10 at scbus1 target 0 # SCSI disk device da11 at scbus1 target 1 # SCSI disk device da12 at scbus1 target 2 # SCSI disk device da13 at scbus1 target 3 # SCSI disk device sa0 at scbus1 target 4 device sa1 at scbus1 target 5 unit 0 device ch0 at scbus1 target 5 unit 1 # CDROM device cd10 at scbus1 target 6 #SCSI cdrom device pass0 #CAM passthrough driver New configuration: # SCSI DEVICES device ncr0 device ncr1 device scbus0 at ncr1 device scbus1 at ncr0 options SCSI_NCR_MYADDR=7 # DISK device da0 at scbus0 target 0 # SCSI disk device da1 at scbus0 target 1 # SCSI disk device da2 at scbus0 target 2 # SCSI disk device da3 at scbus0 target 3 # SCSI disk device da4 at scbus0 target 4 # SCSI disk device da5 at scbus0 target 5 # SCSI disk device cd0 at scbus0 target 6 #SCSI cdrom # TAPE device da10 at scbus1 target 0 # SCSI disk device da11 at scbus1 target 1 # SCSI disk device da12 at scbus1 target 2 # SCSI disk device da13 at scbus1 target 3 # SCSI disk device sa0 at scbus1 target 4 device sa1 at scbus1 target 5 unit 0 device ch0 at scbus1 target 5 unit 1 # CDROM device cd10 at scbus1 target 6 #SCSI cdrom device pass0 #CAM passthrough driver Thanks again, Bill +---------------------------------------------------------------------------+ | Bill and/or Carolyn Pechter | pechter@shell.monmouth.com | | Bill Gates is a Persian cat and a monocle away from being a villain in | | a James Bond movie -- Dennis Miller | +---------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 5:10:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id CA5DF151A1 for ; Wed, 12 Jan 2000 05:10:32 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 789A61CD4; Wed, 12 Jan 2000 21:10:30 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Rodney W. Grimes" Cc: mb@imp.ch (Martin Blapp), current@FreeBSD.ORG Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: Message from "Rodney W. Grimes" of "Wed, 12 Jan 2000 00:44:28 PST." <200001120844.AAA27579@gndrsh.dnsmgr.net> Date: Wed, 12 Jan 2000 21:10:30 +0800 From: Peter Wemm Message-Id: <20000112131030.789A61CD4@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" wrote: [..] > So no disk, so just what is it that you are exporting??? Just a comment: I've seen scenarios where a local disk is attached holding a kernel, bootblocks loader etc, but otherwise booting from a server over NFS. And it exported the rest of it's disk for general use... It's easier than netbooting, allows each machine to contribute disk space to the cluster in addition to compute cycles, keyboard, screen etc. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 5:20:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id 55FCC14F3D for ; Wed, 12 Jan 2000 05:20:53 -0800 (PST) (envelope-from tom@embt.com) Received: from PARANOR (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id HAA12035; Wed, 12 Jan 2000 07:27:43 -0600 (CST) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.20000112081646.0161fcb8@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 12 Jan 2000 08:16:46 -0500 To: Brad Knowles , Warner Losh , "Rodney W. Grimes" From: Tom Embt Subject: Re: Additional option to ls -l for large files Cc: MichaelV@EDIFECS.COM (Michael VanLoon), joerg@cs.waikato.ac.nz, current@FreeBSD.ORG In-Reply-To: References: <200001112314.QAA07511@harmony.village.org> <200001112249.OAA25732@gndrsh.dnsmgr.net> <200001112314.QAA07511@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> kB and kiB are the proper abreviations, not KB and KiB. I don't know >> if miB or MiB is correct, likely MiB. > > I always thought it was "k/m/b = 1,000/1,000,000/1,000,000,000" >and "K/M/G = 2^10/2^20/2^30". Or was this just some convention I >learned somewhere that I mistakenly thought of as an actual accepted >rule? But, with the letter "M" for example, m = milli-, M = mega- Like Donn was saying, there's no reason not to do it every way. Have the different options selectable by either an environmental variable or a command line switch. I'd vote for default behavior as the traditional: K = 2^10 M = 2^20 G = 2^30 T = 2^40 P = 2^50 .. but also have options for showing the entire unclipped file length, "binary mode international abbreviation standard", and maybe even scientific or engineering notation (for kicks). Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 5:30:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id 3870314CD0 for ; Wed, 12 Jan 2000 05:30:18 -0800 (PST) (envelope-from tom@embt.com) Received: from PARANOR (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id HAA12440; Wed, 12 Jan 2000 07:37:43 -0600 (CST) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.20000112082944.01636938@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 12 Jan 2000 08:29:44 -0500 To: Christian Carstensen , Donn Miller From: Tom Embt Subject: Re: why is my current so .... stable? Cc: current@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 14:27 01/12/2000 +0100, Christian Carstensen wrote: >On Wed, 12 Jan 2000, Donn Miller wrote: > >> My guess is that once -current gets closer to the release date, it becomes >> more and more stable. I guess the period of greatest instability occurs >> somewhere about 1/4 to 1/2 through the -current life cycle. We could do a >> chart plotting stability vs. time for the life cycle of a given >> -current. That could help people decide whether or not they want to run >> -current. > >This would be great, but I wonder from what source we could take reliable >data about -current's stability. >But what I've meant was: I've had these ugly system freezes not perfactly >reproducable, but very often. From what I've read on current list, the >problems still exist, but not on my system. At least this system runs >stable for 1 day now. I'm wondering, why. > How 'bout some sort of client program that is run via the rc.d and rc.shutdown scripts? When run on bootup it checks dmesg for "WARNING: / was not properly dismounted", and tells a master server whether or not the last reboot was intentional. When run at shutdown it tells the master server the machine's uptime. Of course it would also help to send a 'uname -v' in both situations. This system would have statistical flaws, but it is still an interesting idea. Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 5:57:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 3FCC014D9C for ; Wed, 12 Jan 2000 05:57:44 -0800 (PST) (envelope-from daeron@wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 194651F28; Wed, 12 Jan 2000 14:57:42 +0100 (CET) Date: Wed, 12 Jan 2000 14:57:41 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: Buildworld Breakage Message-ID: <20000112145741.A95155@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With my CURRENT-tre updated within an hour ago ... Buildworld is broken. cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\ "2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../../ ../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/config -I/usr/obj/usr/src/i386/usr/include -o cpp gcc.o cppspec.o /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choose-te mp.o): In function `choose_temp_base': choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp. o): In function `mktemp': mktemp.o(.text+0x1e1): undefined reference to `_libc_open' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cpp. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 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+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 6: 2:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id A910D14DF0 for ; Wed, 12 Jan 2000 06:02:37 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 18547 invoked from network); 12 Jan 2000 14:02:36 -0000 Received: from lcm97.cvzoom.net (208.230.69.97) by ns.cvzoom.net with SMTP; 12 Jan 2000 14:02:36 -0000 Date: Wed, 12 Jan 2000 09:02:08 -0500 (EST) From: Donn Miller To: Pascal Hofstee Cc: freebsd-current@freebsd.org Subject: Re: Buildworld Breakage In-Reply-To: <20000112145741.A95155@shadowmere.student.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, Pascal Hofstee wrote: > With my CURRENT-tre updated within an hour ago ... Buildworld is broken. [snip] > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp. > o): In function `mktemp': > mktemp.o(.text+0x1e1): undefined reference to `_libc_open' > *** Error code 1 > Stop in /usr/src/gnu/usr.bin/cc/cpp. > *** Error code 1 > Stop in /usr/src/gnu/usr.bin/cc. > *** Error code 1 Yep, I get the same exact thing. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 6:26:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 941C414F4C for ; Wed, 12 Jan 2000 06:26:36 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id XAA08389; Wed, 12 Jan 2000 23:26:22 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id XAA04167; Wed, 12 Jan 2000 23:26:22 +0900 (JST) Received: from localhost ([192.168.245.216]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id XAA14673; Wed, 12 Jan 2000 23:26:20 +0900 (JST) To: tcrimi+@andrew.cmu.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help In-Reply-To: References: X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000112232656W.shin@nd.net.fujitsu.co.jp> Date: Wed, 12 Jan 2000 23:26:56 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 50 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've just turned on IPSec between two machines, an i386 and Alpha, > both running very recent currents, each has the IPSEC and IPSEC_ESP > config options set, but does not have IP6 support enabled. I used > setkey and could establish what appear to be encrypted connections using > vanilla telnet between the hosts, (can someone recommend a good packet > sniffer to ensure this? tcpflow ignored connections between the ipsec > hosts. I used tcpdump -x with a large snaplen and saw that sending a > constant stream of the 0's yeilded the different packets.) I recommend you to try libpcap-3.5 and tcpdump-3.5 obtained from www.tcpdump.org. As far as I tried it on the current, it successfully print out IPv6 and IPsec related headers. Please add --enable-ipv6 option for each configure. To print out IPv6 packets, tcpdump -i ifname -p ip6 To print out IPsec esp packets, tcpdump -i ifname -p esp > What is curious, though, is that during a telnet, running any command > to dump a large amount of information to the screen will lock up the > connection forcing me to login again. Similar things happen with ftp > (locked up after logging in when I first issue an ls). The surest way > to lock up teh connection is to go to /sys/compile/KERN and do an ls. > Data piped to more (a screenful at a time) seems to be ok, but > substancially more locks up TCP connections. This does not occur with > NFS (I build a kernel using it). I suppose something going wrong when multiple mbuf cluster is used for encrypted TCP connection. Because as I tried to cat several different sized files, catting files bigger than around 2048(mbuf cluster size) minus protocol header size seems to cause the problem. Because mbuf cluster could be shared by multiple outstanding packets, it might be encrypted by multiple times. I'll investigate this further. > I notice that setkey -D yeilds different numbers between the machines > in terms of "current:" bytes. That might be depends on the logging timing, the bytes are counted after esp header removal on input and with esp header on output. I'll also check this further. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 6:45:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B9C061552F for ; Wed, 12 Jan 2000 06:45:31 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 128P1d-000Krp-00 for current@FreeBSD.org; Wed, 12 Jan 2000 16:45:29 +0200 From: Sheldon Hearn To: current@FreeBSD.org Subject: NTP4 manual pages committed Date: Wed, 12 Jan 2000 16:45:28 +0200 Message-ID: <80216.947688328@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Those of you who whined about the absence of manual pages in the NTP4 package recently imported into the base system, please check your commit mail. Selected pages have been transcribed from the HTML documentation and committed to the base system. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 6:46: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 6A74214D8D for ; Wed, 12 Jan 2000 06:46:07 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id JAA77998; Wed, 12 Jan 2000 09:45:56 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001121445.JAA77998@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: Martin Blapp , "Rodney W. Grimes" , current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: move portmap(8) from /usr/sbin to /sbin References: <200001120846.AAA68588@apollo.backplane.com> In-reply-to: Your message of "Wed, 12 Jan 2000 00:46:15 PST." <200001120846.AAA68588@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 09:45:56 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What's all this about loopback mounts in fstab about? What does > that have to do with diskless startup? I've got a loopback mount in /var/db/mounttab that looks like this: 946789037 localhost /null which is there because I run cfs (a crypto file system; see /usr/ports/security/cfs). Part of the cfs startup script does this: /usr/local/sbin/cfsd && mount -o port=3049,intr localhost:/null /crypt The problem is that when you boot, the invocation of 'rpc.umntall -k' hangs for a while trying to contact the mountd or portmapper on localhost. If it was smart enough to recognize an ICMP port unreachable error and move on, we wouldn't have this problem. It's not that I think moving mountd and portmap is necessarily a good idea; this is just one scenario which perhaps has prompted this line of thought. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 6:50:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 58A0B15109; Wed, 12 Jan 2000 06:50:34 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 128P6D-000KwU-00; Wed, 12 Jan 2000 16:50:13 +0200 From: Sheldon Hearn To: Kelly Yancey Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: ** HEADS UP ** chown&chgrp moved again In-reply-to: Your message of "Tue, 11 Jan 2000 15:49:54 EST." Date: Wed, 12 Jan 2000 16:50:13 +0200 Message-ID: <80505.947688613@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000 15:49:54 EST, Kelly Yancey wrote: > David, I just noticed that this note in 4.0's RELNOTES about the > relocation doesn't appear applicable anymore: You're right. I've removed the comment from the RELNOTES.TXT for the i386 and alpha. Thanks! Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 6:59: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id DA1DD14E52 for ; Wed, 12 Jan 2000 06:59:05 -0800 (PST) (envelope-from forrie@forrie.com) Received: from Forrest (getbent@forrie.ne.mediaone.net [24.128.72.15]) by forrie.net (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id e0CEx5C73533 for ; Wed, 12 Jan 2000 09:59:05 -0500 (EST) Message-Id: <4.2.2.20000112095616.00bc8dd0@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 12 Jan 2000 09:56:40 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Breakage in FreeBSD-4.0-CURRENT Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Got this error, just now after a CVSUP: /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choos e-temp.o) : In function `choose_temp_base': choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mkt emp.o): I n function `mktemp': mktemp.o(.text+0x1e1): undefined reference to `_libc_open' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cpp. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 6:59:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id C81E415501 for ; Wed, 12 Jan 2000 06:59:11 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id PAA28377; Wed, 12 Jan 2000 15:59:06 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id PAA01830; Wed, 12 Jan 2000 15:59:04 +0100 (MEZ) Date: Wed, 12 Jan 2000 15:59:02 +0100 From: Martin Blapp To: "Louis A. Mamakos" Cc: Matthew Dillon , "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: <200001121445.JAA77998@whizzo.transsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got a loopback mount in /var/db/mounttab that looks like this: > > 946789037 localhost /null > > which is there because I run cfs (a crypto file system; see > /usr/ports/security/cfs). Part of the cfs startup script does > this: > > /usr/local/sbin/cfsd && mount -o port=3049,intr localhost:/null /crypt > > The problem is that when you boot, the invocation of 'rpc.umntall -k' > hangs for a while trying to contact the mountd or portmapper on localhost. > If it was smart enough to recognize an ICMP port unreachable error and > move on, we wouldn't have this problem. > > It's not that I think moving mountd and portmap is necessarily a good > idea; this is just one scenario which perhaps has prompted this line of That's because rpc.umntall has been called the wrong time. I have another patch which does fix this behaviour. Thanks anyway. BTW: you cannot have this line in /etc/fstab, right ? If you put localhost:/null /crypt in fstab, you will get a hang at boottime. Are there other cases for which we will have problems ? Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 7: 7:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 00B3C154D5 for ; Wed, 12 Jan 2000 07:07:46 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 343581E3A; Wed, 12 Jan 2000 16:07:44 +0100 (CET) Date: Wed, 12 Jan 2000 16:07:44 +0100 From: "Dave J. Boers" To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Still system hangs, but different Message-ID: <20000112160744.A693@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000111131010.A317@relativity.student.utwente.nl> <20000111172846.A361@relativity.student.utwente.nl> <200001111821.KAA39855@apollo.backplane.com> <20000111224639.B720@relativity.student.utwente.nl> <200001120354.TAA66873@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001120354.TAA66873@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Jan 11, 2000 at 07:54:33PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt, Like I said, I disabled softupdates on all my filesystems (and added DDB to the kernel). The system has been running 7 hours smoothly now, that's the longest uptime I've had so far with version 1.47 of ffs_softdep.c. I even recreated the directory that I couldn't delete previously and now I don't have any problems with it any more. I guess this proves that the problems I was having _were_ softupdates related. I'll leave the system running for a few more hours and then I will enable softupdates again to try if I can reproduce the problems and take a look with DDB. Regards, Dave Boers. -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 7:25:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 2F3D314E12 for ; Wed, 12 Jan 2000 07:25:56 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id AAA00891 for ; Thu, 13 Jan 2000 00:25:53 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp543.kt.rim.or.jp [202.247.140.193]) by mail1.rim.or.jp (3.7W/) id AAA15333 for ; Thu, 13 Jan 2000 00:25:54 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id AAA22576 for ; Thu, 13 Jan 2000 00:25:53 +0900 (JST) Date: Thu, 13 Jan 2000 00:25:51 +0900 Message-ID: <14460.40191.708206.82051O@localhost.sky.rim.or.jp> From: Jun Kuriyama To: current@FreeBSD.org Subject: panic in uipc_mbuf.c or if_aue.c User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got more panic with DEBUG=-g and INVARIANTS. I saved core dump at this time. This panic is caused when I tested heavy traffic via aue0 (USB ethernet adaptor) with "while looped" large file scp. I think that is only active process. My ipfw is set as default like as "65535 allow ip from any to any". Should I give some data to solve this problem? ----- Panic message ... ipfw: -1 Refuse TCP 192.168.1.7:22 192.168.1.5:1014 in via aue0 panic: m_copydata, length > size of mbuf chain ----- ----- Stack trace #10 0xc015b906 in m_copydata (m=0xc05d4e00, off=0, len=1514, cp=0xc08b8954 "...data..."...) at ../../kern/uipc_mbuf.c:727 #11 0xc021b7af in aue_encap (sc=0xc0828600, m=0xc05d4e00, idx=0) at ../../dev/usb/if_aue.c:1107 #12 0xc021b888 in aue_start (ifp=0xc0828600) at ../../dev/usb/if_aue.c:1162 #13 0xc021b6ca in aue_txeof (xfer=0xc082f080, priv=0xc082871c, status=USBD_NORMAL_COMPLETION) at ../../dev/usb/if_aue.c:1044 #14 0xc02109bd in usb_transfer_complete (xfer=0xc082f080) at ../../dev/usb/usbdi.c:815 #15 0xc020ce1f in uhci_idone (ii=0xc08afc40) at ../../dev/usb/uhci.c:1126 #16 0xc020cbf4 in uhci_check_intr (sc=0xc0830000, ii=0xc08afc40) at ../../dev/usb/uhci.c:1019 #17 0xc020cb23 in uhci_intr (arg=0xc0830000) at ../../dev/usb/uhci.c:965 #18 0xc025ba49 in intr_mux (arg=0xc059ec00) at ../../i386/isa/intr_machdep.c:569 #19 0x8052a7a in ?? () #20 0x8051e53 in ?? () #21 0x804e833 in ?? () #22 0x804f37b in ?? () #23 0x804b4ee in ?? () #24 0x804a0fd in ?? () ----- Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 7:37:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 2AFF714D6F for ; Wed, 12 Jan 2000 07:37:21 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id KAA23708; Wed, 12 Jan 2000 10:41:00 -0500 From: Bill Paul Message-Id: <200001121541.KAA23708@skynet.ctr.columbia.edu> Subject: Re: panic in uipc_mbuf.c or if_aue.c To: kuriyama@sky.rim.or.jp (Jun Kuriyama) Date: Wed, 12 Jan 2000 10:40:59 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <14460.40191.708206.82051O@localhost.sky.rim.or.jp> from "Jun Kuriyama" at Jan 13, 2000 00:25:51 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1661 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Jun Kuriyama had to walk into mine and say: > > I got more panic with DEBUG=-g and INVARIANTS. I saved core dump at > this time. We need version information! How recent is your version of -current! What's the rcsid from if_aue.c! Details please! > This panic is caused when I tested heavy traffic via aue0 (USB > ethernet adaptor) with "while looped" large file scp. I think that is > only active process. > > My ipfw is set as default like as "65535 allow ip from any to any". *sigh* No, this is not what you meant to say. What you meant to say is: "Oh, by the way, I also use ipfw. And oh, by the way, I didn't think to repeat the same test without ipfw." Try the test again with a new kernel *without* ipfw. Maybe the problem is in ipfw. Maybe it isn't, but you have to do some testing to eliminate the possibility! > Should I give some data to solve this problem? No, you should sit there and wait for the bug fairy to come and tap you with her magic wand. Print out the contents of the mbuf!! Show is what it thinks the real length is! -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 7:46:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 23B5114D35 for ; Wed, 12 Jan 2000 07:46:13 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 3B7E41CD7 for ; Wed, 12 Jan 2000 23:46:11 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: HEADS UP - glitch in config(8) scsi device wiring fixed.. Date: Wed, 12 Jan 2000 23:46:11 +0800 From: Peter Wemm Message-Id: <20000112154611.3B7E41CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For about the last 24 hours, there was a botch in the scsi device wiring support in config(8). Please make sure you are running config from -current with version 1.59 or later of mkioconf.c, or your device wiring will be most definately broken. What happened is that 'da0 at scbus0 target 3' (for example) was being generated as though there was a 'lun -2' at the end. (!). So, it wouldn't match anything, but da0 would be reserved still. The end result would be that your scsi disks would carefully avoid da0 and leave you with a less than satisfactory result. :-] "oops". Sorry folks. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 8: 0:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 80BD015571 for ; Wed, 12 Jan 2000 08:00:11 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA18836; Wed, 12 Jan 2000 08:00:10 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA17837; Wed, 12 Jan 2000 08:00:10 -0800 (PST) (envelope-from obrien) Date: Wed, 12 Jan 2000 08:00:10 -0800 From: "David O'Brien" To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: C++ exceptions doesn't work in shared libraries Message-ID: <20000112080010.A87827@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <387B1603.E353CD09@altavista.net> <387C34E5.9E9840AF@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <387C34E5.9E9840AF@altavista.net>; from sobomax@altavista.net on Wed, Jan 12, 2000 at 10:01:42AM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 10:01:42AM +0200, Maxim Sobolev wrote: > Is there are any compiler guys to address my question or not? There is, I'm the one. But there are a few things ahead in the queue. Of course a patch would make things go much faster. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 8:36:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id F045314E39; Wed, 12 Jan 2000 08:36:49 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-1.iptelecom.net.ua [212.9.227.1]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id SAA29825; Wed, 12 Jan 2000 18:40:54 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id SAA01674; Wed, 12 Jan 2000 18:36:13 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <387CAD7B.678B03E3@altavista.net> Date: Wed, 12 Jan 2000 18:36:12 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: C++ exceptions doesn't work in shared libraries References: <387B1603.E353CD09@altavista.net> <387C34E5.9E9840AF@altavista.net> <20000112080010.A87827@dragon.nuxi.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > On Wed, Jan 12, 2000 at 10:01:42AM +0200, Maxim Sobolev wrote: > > Is there are any compiler guys to address my question or not? > > There is, I'm the one. But there are a few things ahead in the queue. Please excuse me if I've offended you, but I just doubted that no one has read my message, so I've tried to check for sure ;). Hovewer it seems that I've selected wrong way to do it, so I'll try to be more patient in the future. > Of course a patch would make things go much faster. Unfortunately, I'm not one of the "compiler gurus", so it would be almost impossible for me to fix this problem. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 8:44:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 5342715567 for ; Wed, 12 Jan 2000 08:44:50 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id JAA21545; Wed, 12 Jan 2000 09:44:49 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA04446; Wed, 12 Jan 2000 09:44:48 -0700 Date: Wed, 12 Jan 2000 09:44:48 -0700 Message-Id: <200001121644.JAA04446@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: NTP4 manual pages committed In-Reply-To: <80216.947688328@axl.noc.iafrica.com> References: <80216.947688328@axl.noc.iafrica.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Those of you who whined about the absence of manual pages in the NTP4 > package recently imported into the base system, please check your commit > mail. Thanks Sheldon! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 8:55:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-111.rp-plus.de [149.221.237.111]) by hub.freebsd.org (Postfix) with ESMTP id 0C0EE15638 for ; Wed, 12 Jan 2000 08:55:48 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 174F3AB92 for ; Wed, 12 Jan 2000 17:56:07 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id RAA04220 for current@freebsd.org; Wed, 12 Jan 2000 17:55:42 +0100 (CET) (envelope-from alex) Date: Wed, 12 Jan 2000 17:55:42 +0100 From: Alexander Langer To: current@freebsd.org Subject: building GNATS with recent current Message-ID: <20000112175542.A414@cichlids.cichlids.com> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I have a recent current: FreeBSD cichlids.cichlids.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Jan 11 13:18:21 CET 2000 alex@cichlids.cichlids.com:/usr/src/sys/compile/cichlids i386 I cannot build the CVS version of GNATS with this. This is kinda strange, because with a kernel from Dec 18th I could do this. something must have changed. Can one reproduce this, too? I can. Please check out: cvs "gnats" from :pserver:anoncvs@anoncvs.cygnus.com:/cvs/gnats type ./configure --with-full-gnats (ignore the error for etc/ that stop the script and then type "make" I stop at: [...] test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include strerror.c -o pic/strerror.o gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include strerror.c test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include strsignal.c -o pic/strsignal.o gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include strsignal.c test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xatexit.c -o pic/xatexit.o gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xatexit.c test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xexit.c -o pic/xexit.o gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xexit.c test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xmalloc.c -o pic/xmalloc.o gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xmalloc.c test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xstrdup.c -o pic/xstrdup.o gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xstrdup.c test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xstrerror.c -o pic/xstrerror.o gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xstrerror.c test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include basename.c -o pic/basename.o gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include basename.c test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include insque.c -o pic/insque.o gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include insque.c rm -f libiberty.a ar rc libiberty.a argv.o choose-temp.o concat.o cplus-dem.o fdmatch.o fnmatch.o getopt.o getopt1.o getruntime.o hex.o floatformat.o objalloc.o obstack.o pexecute.o spaces.o splay-tree.o strerror.o strsignal.o xatexit.o xexit.o xmalloc.o xstrdup.o xstrerror.o basename.o insque.o ranlib libiberty.a now it just _hangs_. I can now SIGINT it. I can SIGINT a further call. I can do nothing with a third call. I EVEN cannot SIGKILL it!! gdb tells me, that it stops at wait4(). Now it becomes strange. I "cd" into the same dir, and now a "ls" hangs, too. when I do a cd dir ; ls on 3 further consoles, the SYSTEM just hangs. It _just_ hangs. no error, it only hangs. Please test, if this is the same case for you. As said, this was not the case with a kernel from Dec. 18th, therefore (same config-file) I'll not include the kernel-config here. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 9:24:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id AF65B15669 for ; Wed, 12 Jan 2000 09:24:43 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA28817; Wed, 12 Jan 2000 09:24:22 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001121724.JAA28817@gndrsh.dnsmgr.net> Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: <20000112125033.A51579@walton.maths.tcd.ie> from David Malone at "Jan 12, 2000 12:50:33 pm" To: dwmalone@maths.tcd.ie (David Malone) Date: Wed, 12 Jan 2000 09:24:21 -0800 (PST) Cc: mb@imp.ch, dillon@apollo.backplane.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Jan 12, 2000 at 01:23:14AM -0800, Rodney W. Grimes wrote: > > > Also moving them to pass1 would bring up nfs exports before we > > brought up nfs mounts. syslogd would not be running to catch > > Shouldn't nfs exports happen before nfs mounts, so that machines > which have nfs interdependencies don't sit there waiting for one > another? (I think we've had to change this several times in the > FreeBSD rc scripts, I guess the reason it might be the other way > around is incase /usr is nfs mounted?) If your talking about dead lock caused by mutual cross mounting between 2 systems via NFS the NFS rule book says ``don't do that, it hurts''. Independent of order of export/mounting the dead lock occurs. Cross mounting via NFS is a verbotten thing in the sysadmin world of production systems. :-) I have had to fix it at several sites admin'd by newbies... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 9:27:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id CD4FD1552F for ; Wed, 12 Jan 2000 09:27:19 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA28834; Wed, 12 Jan 2000 09:27:00 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001121727.JAA28834@gndrsh.dnsmgr.net> Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: <20000112131030.789A61CD4@overcee.netplex.com.au> from Peter Wemm at "Jan 12, 2000 09:10:30 pm" To: peter@netplex.com.au (Peter Wemm) Date: Wed, 12 Jan 2000 09:27:00 -0800 (PST) Cc: mb@imp.ch (Martin Blapp), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Rodney W. Grimes" wrote: > [..] > > So no disk, so just what is it that you are exporting??? > > Just a comment: > > I've seen scenarios where a local disk is attached holding a kernel, > bootblocks loader etc, but otherwise booting from a server over NFS. And > it exported the rest of it's disk for general use... It's easier than > netbooting, allows each machine to contribute disk space to the cluster in > addition to compute cycles, keyboard, screen etc. See other mail about the evilness of cross mounting NFS, this especially applies in a cluster! You can't bloody cold start the beast easily. One way I have seen it worked around is to flag the NFS mounts -background so that they don't hang the boot process. Still evil lurks in these corners of the world... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 9:33:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 93C011552C for ; Wed, 12 Jan 2000 09:33:13 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA40492; Wed, 12 Jan 2000 10:33:11 -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.9.3/8.8.3) with ESMTP id KAA15017; Wed, 12 Jan 2000 10:33:27 -0700 (MST) Message-Id: <200001121733.KAA15017@harmony.village.org> To: Brad Knowles Subject: Re: Additional option to ls -l for large files Cc: "Rodney W. Grimes" , MichaelV@EDIFECS.COM (Michael VanLoon), joerg@cs.waikato.ac.nz, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 12 Jan 2000 12:02:33 +0100." References: <200001112249.OAA25732@gndrsh.dnsmgr.net> <200001112314.QAA07511@harmony.village.org> Date: Wed, 12 Jan 2000 10:33:27 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Brad Knowles writes: : I always thought it was "k/m/b = 1,000/1,000,000/1,000,000,000" : and "K/M/G = 2^10/2^20/2^30". Or was this just some convention I : learned somewhere that I mistakenly thought of as an actual accepted : rule? This is wrong. k is Si for 10^3, but m is 10^-3. M is 10^6 and G is 10^9. K was used for a long time for 2^10. M and G were overloaded to mean 2^20 and 2^30, but some people even in the industry broke ranks (the disk drive makers) and were able to claim larger disk sizes by using the Si meaning of M rather than the CS meaning of M. I've rarely seen your meanings used anywere, except for the k vs K thing. You may want to take a look at http://physics.nist.gov/cuu/Units/binary.html for definitions of the binary stuff. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 9:49:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id E48EE15467; Wed, 12 Jan 2000 09:49:22 -0800 (PST) (envelope-from jedgar@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1003) id 79B579B6F; Wed, 12 Jan 2000 12:49:21 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 6F524BA0C; Wed, 12 Jan 2000 12:49:21 -0500 (EST) Date: Wed, 12 Jan 2000 12:49:21 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: freebsd-current@freebsd.org Cc: mckusick@freebsd.org Subject: Softupdates panic? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following backtrace comes from a panic I just had on my laptop that appears to be softupdates-related. Sources are from yesterday, re-cvsup'ing shows no new fs-related sources updated. At the time I was in the middle of compiling the Window Maker port (actually compiling the jpeglib dependency). ffs_softdep.c version below, others available upon request (along with kernel.debug/vmcore info): $FreeBSD: src/sys/contrib/softupdates/ffs_softdep.c,v 1.47 2000/01/11 06:52:35 mckusick Exp $ ata-pci0: port 0x3000-0x300f at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ad0: ATA-3 disk at ata0 as master ad0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 Script started on Wed Jan 12 12:25:45 2000 root@pluto:~# gdb -k /sys/compile/PLUTO/kernel.debug /var/crash/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 3149824 initial pcb at 28b660 panicstr: from debugger panic messages: --- panic: flush_pagedep_deps: flush 3 failed panic: from debugger Uptime: 23h19m6s dumping to dev #ad/0x30001, offset 131072 dump ata0: resetting devices .. done 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 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 boot (howto=260) at ../../kern/kern_shutdown.c:304 304 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 #1 0xc01373a5 in panic (fmt=0xc0235bf4 "from debugger") at ../../kern/kern_shutdown.c:554 #2 0xc011c419 in db_panic (addr=-1071552339, have_addr=0, count=-1, modif=0xc72a18d0 "") at ../../ddb/db_command.c:433 #3 0xc011c3b9 in db_command (last_cmdp=0xc025e8b8, cmd_table=0xc025e718, aux_cmd_tablep=0xc02878cc) at ../../ddb/db_command.c:333 #4 0xc011c47e in db_command_loop () at ../../ddb/db_command.c:455 #5 0xc011e507 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xc0216651 in kdb_trap (type=3, code=0, regs=0xc72a19d8) at ../../i386/i386/db_interface.c:158 #7 0xc0222088 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 276254, tf_esi = 256, tf_ebp = -953542112, tf_isp = -953542140, tf_ebx = -1071353856, tf_edx = 0, tf_ecx = 0, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1071552339, tf_cs = 8, tf_eflags = 582, tf_esp = -1071302401, tf_ss = -1071410141}) at ../../i386/i386/trap.c:531 #8 0xc02168ad in Debugger (msg=0xc0239423 "panic") at machine/cpufunc.h:64 #9 0xc013739c in panic (fmt=0xc0247000 "flush_pagedep_deps: flush 3 failed") at ../../kern/kern_shutdown.c:552 #10 0xc01d01f2 in flush_pagedep_deps (pvp=0xc7391ea0, mp=0xc0ffd800, diraddhdp=0xc11246a4) at ../../ufs/ffs/ffs_softdep.c:4248 #11 0xc01cfaf8 in softdep_sync_metadata (ap=0xc72a1b6c) at ../../ufs/ffs/ffs_softdep.c:3934 ---Type to continue, or q to quit--- #12 0xc01d3a6c in ffs_fsync (ap=0xc72a1b6c) at ../../ufs/ffs/ffs_vnops.c:249 #13 0xc01cab08 in ffs_truncate (vp=0xc7391ea0, length=1024, flags=4, cred=0xc1006400, p=0xc6d6e100) at vnode_if.h:537 #14 0xc01d6277 in ufs_direnter (dvp=0xc7391ea0, tvp=0xc7378180, dirp=0xc72a1cb8, cnp=0xc72a1f04, newdirbp=0x0) at ../../ufs/ufs/ufs_lookup.c:842 #15 0xc01da137 in ufs_makeinode (mode=33188, dvp=0xc7391ea0, vpp=0xc72a1ef0, cnp=0xc72a1f04) at ../../ufs/ufs/ufs_vnops.c:2159 #16 0xc01d7994 in ufs_create (ap=0xc72a1e10) at ../../ufs/ufs/ufs_vnops.c:183 #17 0xc01da1c1 in ufs_vnoperate (ap=0xc72a1e10) at ../../ufs/ufs/ufs_vnops.c:2283 #18 0xc0166b1c in vn_open (ndp=0xc72a1edc, fmode=1538, cmode=420) at vnode_if.h:106 #19 0xc0162de1 in open (p=0xc6d6e100, uap=0xc72a1f80) at ../../kern/vfs_syscalls.c:994 #20 0xc0222956 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 1, tf_esi = 135000800, tf_ebp = -1077939148, tf_isp = -953540652, tf_ebx = -1, tf_edx = 134975904, tf_ecx = -1077939096, tf_eax = 5, tf_trapno = 12, tf_err = 2, tf_eip = 134692812, tf_cs = 31, tf_eflags = 663, tf_esp = -1077939192, tf_ss = 47}) at ../../i386/i386/trap.c:1055 #21 0xc0216f56 in Xint0x80_syscall () #22 0x8056afd in ?? () #23 0x804b9e5 in ?? () ---Type to continue, or q to quit--- #24 0x804a94c in ?? () #25 0x804a785 in ?? () #26 0x804a8a2 in ?? () #27 0x8051ac6 in ?? () #28 0x8051a32 in ?? () #29 0x80480f9 in ?? () (kgdb) root@pluto:~# Script done on Wed Jan 12 12:25:56 2000 ----- 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-current" in the body of the message From owner-freebsd-current Wed Jan 12 9:49:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 059D81564B for ; Wed, 12 Jan 2000 09:49:32 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 12 Jan 2000 17:49:29 +0000 (GMT) To: "Rodney W. Grimes" Cc: mb@imp.ch, dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: move portmap(8) from /usr/sbin to /sbin In-reply-to: Your message of "Wed, 12 Jan 2000 09:24:21 PST." <200001121724.JAA28817@gndrsh.dnsmgr.net> X-Request-Do: Date: Wed, 12 Jan 2000 17:49:29 +0000 From: David Malone Message-ID: <200001121749.aa63208@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If your talking about dead lock caused by mutual cross mounting > between 2 systems via NFS the NFS rule book says ``don't do that, > it hurts''. > > Independent of order of export/mounting the dead lock occurs. Cross > mounting via NFS is a verbotten thing in the sysadmin world of production > systems. :-) I have had to fix it at several sites admin'd by newbies... Strange - it's worked fine for years here, as long as you fix rc stuff ;-) Infact, it works OK if you don't fix rc stuff, as long as you make all the mounts backgroundable. (We've used NFS heavily for years, and never had enough cash to be able to group machines into NFS servers and NFS clients. If you want all your machines to be available to all your users, and you share home directories then to avoid cycles in your NFS graph you have to have one NFS server). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 10: 1:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id BFE2514A2F for ; Wed, 12 Jan 2000 10:01:36 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 128S5J-000N1p-00 for current@FreeBSD.ORG; Wed, 12 Jan 2000 20:01:29 +0200 From: Sheldon Hearn To: current@FreeBSD.ORG Subject: Re: Additional option to ls -l for large files In-reply-to: Your message of "Wed, 12 Jan 2000 10:33:27 MST." <200001121733.KAA15017@harmony.village.org> Date: Wed, 12 Jan 2000 20:01:29 +0200 Message-ID: <88524.947700089@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, this is getting a little silly. Can't we cut all the esoteric mumbo-jumbo and agree to do it the same way that gnuls and our own existing df do it? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 11:17: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id B9C411565F for ; Wed, 12 Jan 2000 11:16:52 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 7817 invoked by uid 1001); 12 Jan 2000 19:16:38 -0000 Date: Wed, 12 Jan 2000 11:16:38 -0800 From: Jason Evans To: Pascal Hofstee Cc: freebsd-current@freebsd.org Subject: Re: Buildworld Breakage Message-ID: <20000112111638.N302@sturm.canonware.com> References: <20000112145741.A95155@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000112145741.A95155@shadowmere.student.utwente.nl>; from daeron@shadowmere.student.utwente.nl on Wed, Jan 12, 2000 at 02:57:41PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 02:57:41PM +0100, Pascal Hofstee wrote: > With my CURRENT-tre updated within an hour ago ... Buildworld is broken. > > cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H > -DDEFAULT_TARGET_VERSION=\ "2.95.2\" > -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" > -DPREFIX=\"/usr/obj/usr/src/i386/usr\" > -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_tools > -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools > -I/usr/src/gnu/usr.bin/cc/cpp/../../ ../../contrib/gcc > -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/config > -I/usr/obj/usr/src/i386/usr/include -o cpp gcc.o cppspec.o > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choose-te > mp.o): In function `choose_temp_base': > choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; > consider using mkstemp() > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp. > o): In function `mktemp': > mktemp.o(.text+0x1e1): undefined reference to `_libc_open' > *** Error code 1 > Stop in /usr/src/gnu/usr.bin/cc/cpp. > *** Error code 1 > Stop in /usr/src/gnu/usr.bin/cc. > *** Error code 1 This looks like possible breakage related to the changes to libc that I committed early this morning. The thing is, I successfully built the world with those changes in place. It may be that you got a partial update of the ~150 files that the changes touched in libc and libc_r. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 11:27: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 55B4C14A24 for ; Wed, 12 Jan 2000 11:27:02 -0800 (PST) (envelope-from daeron@wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 8C8481F19; Wed, 12 Jan 2000 20:27:00 +0100 (CET) Date: Wed, 12 Jan 2000 20:27:00 +0100 From: Pascal Hofstee To: Jason Evans Cc: freebsd-current@freebsd.org Subject: Re: Buildworld Breakage Message-ID: <20000112202659.A89546@shadowmere.student.utwente.nl> References: <20000112145741.A95155@shadowmere.student.utwente.nl> <20000112111638.N302@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000112111638.N302@sturm.canonware.com>; from jasone@canonware.com on Wed, Jan 12, 2000 at 11:16:38AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 11:16:38AM -0800, Jason Evans wrote: > On Wed, Jan 12, 2000 at 02:57:41PM +0100, Pascal Hofstee wrote: > > With my CURRENT-tre updated within an hour ago ... Buildworld is broken. > > > > cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H > > -DDEFAULT_TARGET_VERSION=\ "2.95.2\" > > -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" > > -DPREFIX=\"/usr/obj/usr/src/i386/usr\" > > -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_tools > > -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools > > -I/usr/src/gnu/usr.bin/cc/cpp/../../ ../../contrib/gcc > > -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/config > > -I/usr/obj/usr/src/i386/usr/include -o cpp gcc.o cppspec.o > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choose-te > > mp.o): In function `choose_temp_base': > > choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; > > consider using mkstemp() > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp. > > o): In function `mktemp': > > mktemp.o(.text+0x1e1): undefined reference to `_libc_open' > > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/cc/cpp. > > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/cc. > > *** Error code 1 > > This looks like possible breakage related to the changes to libc that I > committed early this morning. The thing is, I successfully built the world > with those changes in place. It may be that you got a partial update of > the ~150 files that the changes touched in libc and libc_r. This breakage has occurred for 3 consecutive buildworlds now with several Hours between each build. I doubt this is a "halfway through a commit" bustage. -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 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+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 11:51:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C666114F21 for ; Wed, 12 Jan 2000 11:51:10 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA74033; Wed, 12 Jan 2000 11:51:09 -0800 (PST) (envelope-from dillon) Date: Wed, 12 Jan 2000 11:51:09 -0800 (PST) From: Matthew Dillon Message-Id: <200001121951.LAA74033@apollo.backplane.com> To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: softdep: panic: flush_pagedep_deps: flush 3 failed References: <20000112035947.T9397@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I've reproduced your 'flush 3 failed' softupdates panic! I have a core dump that kirk can look at. -Matt Matthew Dillon : :This can be reproduced by doing a cvsup to get a new repo, not an update :but a clean checkout, twice in the same spot. :... :-- :-Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] :Wintelcom systems administrator and programmer : - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 11:56:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id E9AC314C4A; Wed, 12 Jan 2000 11:56:26 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id e0CJuNw65075; Wed, 12 Jan 2000 21:56:23 +0200 (SAST) Message-Id: <200001121956.e0CJuNw65075@gratis.grondar.za> To: obrien@freebsd.org Cc: current@freebsd.org Subject: Make world breakage... Date: Wed, 12 Jan 2000 21:56:22 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Anyone else seeing this? cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/config-I/usr/obj/usr/src/i386/usr/include -o cpp gcc.o cppspec.o /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choose-temp.o): In function `choose_temp_base': choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp. o): In function `mktemp': mktemp.o(.text+0x1e1): undefined reference to `_libc_open' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cpp. *** Error code 1 M To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 11:58:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 635DB14EEA for ; Wed, 12 Jan 2000 11:58:34 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA74096; Wed, 12 Jan 2000 11:58:34 -0800 (PST) (envelope-from dillon) Date: Wed, 12 Jan 2000 11:58:34 -0800 (PST) From: Matthew Dillon Message-Id: <200001121958.LAA74096@apollo.backplane.com> To: current@FreeBSD.ORG Subject: R/W mount of / denied, filesystem not clean (after fsck) References: <200001121956.e0CJuNw65075@gratis.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm. I was under the impression that this problem was fixed, but I am getting it again. When I have a crash and reboot fsck runs through all the filesystems but then mount refuses to mount / thinking that it's dirty when it isn't. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 11:59: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 9A182150BC for ; Wed, 12 Jan 2000 11:59:03 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 7953 invoked by uid 1001); 12 Jan 2000 19:58:49 -0000 Date: Wed, 12 Jan 2000 11:58:49 -0800 From: Jason Evans To: Mark Murray Cc: obrien@freebsd.org, current@freebsd.org Subject: Re: Make world breakage... Message-ID: <20000112115849.O302@sturm.canonware.com> References: <200001121956.e0CJuNw65075@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001121956.e0CJuNw65075@gratis.grondar.za>; from mark@grondar.za on Wed, Jan 12, 2000 at 09:56:22PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote: > Hi > > Anyone else seeing this? > > cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/config-I/usr/obj/usr/src/i386/usr/include -o cpp gcc.o cppspec.o /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choose-temp.o): In function `choose_temp_base': > choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp. > o): In function `mktemp': > mktemp.o(.text+0x1e1): undefined reference to `_libc_open' > *** Error code 1 > Stop in /usr/src/gnu/usr.bin/cc/cpp. > *** Error code 1 Yes, three others have reported it as well. On the surface, it looks like my fault, but I'm still in the process of trying to reproduce it (my most recent buildworld went off without a hitch). Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 12: 3:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 19B9B14FE4 for ; Wed, 12 Jan 2000 12:03:38 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA05772 for freebsd-current@freebsd.org; Wed, 12 Jan 2000 20:57:16 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA01903 for freebsd-current@freebsd.org; Wed, 12 Jan 2000 21:00:06 +0100 (CET) (envelope-from wilko) Date: Wed, 12 Jan 2000 21:00:06 +0100 From: Wilko Bulte To: "FreeBSD_current, mailing list" Subject: mkdep error in sio.c on Alpha? Message-ID: <20000112210005.A1850@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -current supped 10 minutes ago gives during make depend: c ../../isa/vga_isa.c ../../kern/subr_diskmbr.c ../../libkern/bcmp.c ../../libkern/ffs.c ioconf.c param.c vnode_if.c config.c ../../alpha/alpha/genassym.c ../../isa/sio.c:2926: macro `CONS_DRIVER' used with only 7 args mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/compile/MIATA. miata# -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 12:26:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 7ED1814DFD for ; Wed, 12 Jan 2000 12:26:10 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id VAA50497; Wed, 12 Jan 2000 21:26:09 +0100 (CET) (envelope-from olli) Date: Wed, 12 Jan 2000 21:26:09 +0100 (CET) Message-Id: <200001122026.VAA50497@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: Additional option to ls -l for large files X-Newsgroups: list.freebsd-current In-Reply-To: <85g9n7$2ql7$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Personally, I'd much prefer to simply use separator characters like this: -rw------- 1 olli olli 211,602,776 Nov 28 23:09 S1E1.mpg This makes it very easy to recognize the size, and you still have the exact number of bytes, not rounded. It's even possible to to respect the locale setting (LC_NUMERIC) and use the appropriate character as separator. Just my 0.02 Euro. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 12:32:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id AE15214E6B for ; Wed, 12 Jan 2000 12:32:07 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B58A01CD7; Thu, 13 Jan 2000 04:32:05 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Rodney W. Grimes" Cc: mb@imp.ch (Martin Blapp), current@FreeBSD.ORG Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: Message from "Rodney W. Grimes" of "Wed, 12 Jan 2000 09:27:00 PST." <200001121727.JAA28834@gndrsh.dnsmgr.net> Date: Thu, 13 Jan 2000 04:32:05 +0800 From: Peter Wemm Message-Id: <20000112203205.B58A01CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" wrote: > > "Rodney W. Grimes" wrote: > > [..] > > > So no disk, so just what is it that you are exporting??? > > > > Just a comment: > > > > I've seen scenarios where a local disk is attached holding a kernel, > > bootblocks loader etc, but otherwise booting from a server over NFS. And > > it exported the rest of it's disk for general use... It's easier than > > netbooting, allows each machine to contribute disk space to the cluster in > > addition to compute cycles, keyboard, screen etc. > > See other mail about the evilness of cross mounting NFS, this especially > applies in a cluster! You can't bloody cold start the beast easily. Yes you can.. I didn't say the boxes depended on each other to boot. They had a NFS server for the OS for /, /usr etc. They cross mounted the exported space between the boxes via 'amd' which happens much later (and is in /usr). The seperate server depended on nothing. > One way I have seen it worked around is to flag the NFS mounts -background > so that they don't hang the boot process. Still evil lurks in these > corners of the world... Or don't mount it early in the boot. I'm not suggesting moving portmap BTW, I'm just saying that there are other ways of doing it. Yes, having cross mounting required to *boot* is evil, but when it's not active until somebody logs in it's mostly harmless. On an unrelated note, I remember the cold-start nightmare scenario well. One of the local universities had a cluster of SGI IRIS boxes, way back when they were new and had tiny disks. There was a power out and the cross mounting in order to preserve every scrap of space caused quite a lot of excitement. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 13:10:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from tower.ti.com (tower.ti.com [192.94.94.5]) by hub.freebsd.org (Postfix) with ESMTP id EC65B14C45 for ; Wed, 12 Jan 2000 13:10:51 -0800 (PST) (envelope-from ntakpe@ffab.tide.ti.com) Received: from dlep8.itg.ti.com ([157.170.134.88]) by tower.ti.com (8.9.3/8.9.3) with ESMTP id PAA29705; Wed, 12 Jan 2000 15:10:12 -0600 (CST) Received: from dlep8.itg.ti.com (localhost [127.0.0.1]) by dlep8.itg.ti.com (8.9.3/8.9.3) with ESMTP id PAA17753; Wed, 12 Jan 2000 15:09:49 -0600 (CST) Received: from wrks2host.ffab.tide.ti.com (wrks2host.ffab.tide.ti.com [137.167.200.37]) by dlep8.itg.ti.com (8.9.3/8.9.3) with ESMTP id PAA17727; Wed, 12 Jan 2000 15:09:48 -0600 (CST) Received: from ishtar.ffab.tide.ti.com (ishtar.ffab.tide.ti.com [137.167.200.61]) by wrks2host.ffab.tide.ti.com (8.8.8+Sun/8.8.8) with ESMTP id WAA06886; Wed, 12 Jan 2000 22:10:08 +0100 (MET) Received: from ishtar.ffab.tide.ti.com (IDENT:ntakpe@ishtar.ffab.tide.ti.com [137.167.200.61]) by ishtar.ffab.tide.ti.com (8.9.3/8.9.3) with ESMTP id WAA21643; Wed, 12 Jan 2000 22:10:07 +0100 Message-ID: <387CEDAF.B8BCEFFB@ishtar.ffab.tide.ti.com> Date: Wed, 12 Jan 2000 22:10:07 +0100 From: Jean Louis Ntakpe Organization: TI Freising - Automation Group X-Sender: "Jean Louis Ntakpe" <@ishtar.ffab.tide.ti.com> (Unverified) X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i586) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: NTP4 manual pages committed References: <80216.947688328@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Could somebody help me setting up my ntp server with a DCF receiver. Since I updated to ntp4, ntpd does not like my old ntp.conf any more. Here is my old ntp.conf. my ntpd daemon was doing just fine and now :^( # ------------------------------------------------------ # XNTP configuration file (/etc/ntp.conf) # # # Server is a Boeder DCF77 receiver # # Use: # 127.127.8.40 for /dev/refclock-0 (/dev/ttyd0) # 127.127.8.41 for /dev/refclock-1 (/dev/ttyd1) # 127.127.8.42 for /dev/refclock-2 (/dev/ttyd2) # 127.127.8.43 for /dev/refclock-3 (/dev/ttyd3) # server 127.127.8.41 # # drift file # driftfile /etc/ntp.drift # ------------------ end of ntp.conf ------------------- Thanks, -- Jean Louis Ntakpe Texas Instruments - Freising Wafer Fab Automation Group Haggerty Str. 1 85350 Freising Telefon +49 (8161) 80-3816 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 13:18:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 46C1014E2F; Wed, 12 Jan 2000 13:18:53 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA08832; Wed, 12 Jan 2000 22:05:41 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA02959; Wed, 12 Jan 2000 22:07:25 +0100 (CET) (envelope-from wilko) Date: Wed, 12 Jan 2000 22:07:25 +0100 From: Wilko Bulte To: Mark Murray Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Make world breakage... Message-ID: <20000112220725.A2942@yedi.iaf.nl> References: <200001121956.e0CJuNw65075@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001121956.e0CJuNw65075@gratis.grondar.za>; from mark@grondar.za on Wed, Jan 12, 2000 at 09:56:22PM +0200 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote: > Hi > > Anyone else seeing this? > > cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/config-I/usr/obj/usr/src/i386/usr/include -o cpp gcc.o cppspec.o /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choose-temp.o): In function `choose_temp_base': > choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp. > o): In function `mktemp': > mktemp.o(.text+0x1e1): undefined reference to `_libc_open' > *** Error code 1 > Stop in /usr/src/gnu/usr.bin/cc/cpp. > *** Error code 1 > Yep. Also on Alpha: /usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choose-temp.o): In function `choose_temp_base': choose-temp.c(.text+0x218): warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o): In function `_gettemp': mktemp.c(.text+0x3f0): undefined reference to `_libc_open' mktemp.c(.text+0x3f4): undefined reference to `_libc_open' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cpp. *** Error code 1 -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 13:19:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 0E63F15547 for ; Wed, 12 Jan 2000 13:19:55 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 8269 invoked by uid 1001); 12 Jan 2000 21:19:40 -0000 Date: Wed, 12 Jan 2000 13:19:40 -0800 From: Jason Evans To: Jason Evans Cc: Pascal Hofstee , freebsd-current@freebsd.org Subject: Re: Buildworld Breakage Message-ID: <20000112131939.S302@sturm.canonware.com> References: <20000112145741.A95155@shadowmere.student.utwente.nl> <20000112111638.N302@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000112111638.N302@sturm.canonware.com>; from jasone@canonware.com on Wed, Jan 12, 2000 at 11:16:38AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 11:16:38AM -0800, Jason Evans wrote: > On Wed, Jan 12, 2000 at 02:57:41PM +0100, Pascal Hofstee wrote: > > With my CURRENT-tre updated within an hour ago ... Buildworld is broken. > > > > cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H > > -DDEFAULT_TARGET_VERSION=\ "2.95.2\" > > -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" > > -DPREFIX=\"/usr/obj/usr/src/i386/usr\" > > -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_tools > > -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools > > -I/usr/src/gnu/usr.bin/cc/cpp/../../ ../../contrib/gcc > > -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/config > > -I/usr/obj/usr/src/i386/usr/include -o cpp gcc.o cppspec.o > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choose-te > > mp.o): In function `choose_temp_base': > > choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; > > consider using mkstemp() > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp. > > o): In function `mktemp': > > mktemp.o(.text+0x1e1): undefined reference to `_libc_open' > > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/cc/cpp. > > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/cc. > > *** Error code 1 > > This looks like possible breakage related to the changes to libc that I > committed early this morning. The thing is, I successfully built the world > with those changes in place. It may be that you got a partial update of > the ~150 files that the changes touched in libc and libc_r. Okay, this is a bootstrapping issue. I didn't run into it because I manually installed libc during testing, before doing a buildworld. Doing the following before a buildworld should allow the buildworld to complete: cd /usr/src/lib/libc make make install Then buildworld. I'm not very well versed in the buildworld bootstrapping, so any help in fixing this the right way would be appreciated. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 13:20:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 0734A15244 for ; Wed, 12 Jan 2000 13:20:46 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA39524; Wed, 12 Jan 2000 16:20:42 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200001120201.SAA26378@gndrsh.dnsmgr.net> References: <200001120201.SAA26378@gndrsh.dnsmgr.net> Date: Wed, 12 Jan 2000 16:21:05 -0500 To: "Rodney W. Grimes" From: Garance A Drosihn Subject: Re: Additional option to ls -l for large files Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:01 PM -0800 1/11/00, Rodney W. Grimes wrote: >Garance wrote: > > personally, I'd just as soon use K, M, and G and have it mean > > the base-10 values. If I'm looking at a decimal number for one > > file (because it's small enough), I don't want a base-2 version > > of the similar number for some other (larger) file in the same > > listing. > > > > (ie, whatever letters you use, please just divide the values > > by 1000 instead of 1024). > >Please don't, there is already far to much precedence in both the >computing world and other commands (df -k and du -k come to mind >right off the top of my head, sysinstall uses them in the disklabel >and partition editor, etc) > >df man page: > -k Use 1024-byte (1-Kbyte) blocks rather than the default. > Note that this overrides the BLOCKSIZE specification > from the environment. >du man page: > -k Display block counts in 1024-byte (1-Kbyte) blocks. Note that these commands are talking about block-sizes. Ie, you are getting a BLOCK count, where the BLOCKSIZE is either 512 (the default value) or some other number (frequently 1024). If you do choose a blocksize of 1024, then the number you get happens to be "kilobytes", but both commands are still talking about a BLOCK count. In 'ls' we are not talking about a block count, we are talking about a byte-count. In the past I have written things which do about what we're talking about here. In the current 'ls', when you see a list of files as: -rw-r--r-- 1 gad staff 19672 Dec 11 03:39 HISTORY -rw-r--r-- 1 gad staff 411 Dec 11 03:47 Makefile.am -rw-r--r-- 1 gad staff 11492 Dec 12 23:57 Makefile.in -rw-r--r-- 1 gad staff 2585 Dec 11 03:39 README-bpe -rw-r--r-- 1 gad staff 1549 Dec 12 23:55 acconfig.h -rw-r--r-- 1 gad staff 4396 Dec 12 23:57 aclocal.m4 -rw-r--r-- 1 gad staff 2706 Dec 11 03:39 asciiedit.c -rw-r--r-- 1 gad staff 2046 Dec 11 03:39 asciisrch.c -rw-r--r-- 1 gad staff 5755 Dec 11 03:39 backup.c -rw-r--r-- 1 gad staff 35071 Dec 11 03:38 bpe.1 do you really sit there and think "Let's see, that bpe.1 file is (35071/1024) kilobytes"? Being a slave to the decimal system, I just read the numbers. The original message proposed: a new flag to ls which will together with option -l change the unit to kilobytes for files larger than one megabyte, to megabytes for files larger than one gigabyte and gigabytes for files larger than one terabyte. In the past, I have done similar things to this, exactly as the person suggested. If you do not stick to the "10's-based" numbers for this, things get confusing. Note that you don't switch to kilobytes until the file is over a megabyte. You end up dealing with "10's based" values *all* the time, and "2's based" values some of the time. Ie, consider files: -rw-r--r-- 1 gad staff 1998246 Dec 11 03:39 asciiedit.c -rw-r--r-- 1 gad staff 999123 Dec 11 03:39 asciisrch.c The first one changes because it's over 1 megabyte, but the second one does not change. So you get: -rw-r--r-- 1 gad staff 1951k Dec 11 03:39 asciiedit.c -rw-r--r-- 1 gad staff 999123 Dec 11 03:39 asciisrch.c Okay now, how many people can look at those lines and immediately see that the first file is "about" twice the size of the second file? Probably nobody, not without pulling out a calculator. The "purity" of using 1024 as a divisor buys one nothing in situations like this. The problem is that you ARE using the 10's-based number (in your head) for the "999 thousand" value. And the 1,951K is a mixture of 10's-based ("1 thousand 951") and 2's-based ("K") values. Point number two: This option is to keep the number of columns of the byte-count-field "reasonable". 1 megabyte is 1024*1024. A 1-megabyte file is therefore 1048576 bytes. If you make the switch (to "k") at 1048576 bytes, you have used up an extra column for no good reason. So, it only makes sense to make the switch at 999,999 bytes. You'll get: -rw-r--r-- 1 gad staff 8064k Dec 11 03:39 asciiedit.c -rw-r--r-- 1 gad staff 999999 Dec 11 03:39 asciisrch.c when the first file is one byte larger than the second file. Again, the "purity" of going with the "2's based" value is not worth the confusion caused by it. This is what my experience has been when I've done similar things. I actually wrote at least one thing using the 1024 divisor, and later switched it to using 1000 because using 1024 was just too confusing. Thus, my suggestion that people should consider going with the base-10 values. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 13:22:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 36C2814ECF for ; Wed, 12 Jan 2000 13:22:40 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 8293 invoked by uid 1001); 12 Jan 2000 21:22:25 -0000 Date: Wed, 12 Jan 2000 13:22:25 -0800 From: Jason Evans To: Wilko Bulte Cc: Mark Murray , obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Make world breakage... Message-ID: <20000112132225.T302@sturm.canonware.com> References: <200001121956.e0CJuNw65075@gratis.grondar.za> <20000112220725.A2942@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000112220725.A2942@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Wed, Jan 12, 2000 at 10:07:25PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote: > On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote: > > Hi > > > > Anyone else seeing this? > > > > cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/gcc/config-I/usr/obj/usr/src/i386/usr/include -o cpp gcc.o cppspec.o /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choose-temp.o): In function `choose_temp_base': > > choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp. > > o): In function `mktemp': > > mktemp.o(.text+0x1e1): undefined reference to `_libc_open' > > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/cc/cpp. > > *** Error code 1 > > > > Yep. Also on Alpha: > > /usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choose-temp.o): > In function `choose_temp_base': > choose-temp.c(.text+0x218): warning: mktemp() possibly used unsafely; > consider using mkstemp() > /usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o): > In function `_gettemp': > mktemp.c(.text+0x3f0): undefined reference to `_libc_open' > mktemp.c(.text+0x3f4): undefined reference to `_libc_open' > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/cc/cpp. > *** Error code 1 libc successfully builds on Alpha with the changes I committed, though the bootstrapping problem issue is the same. As noted in another email I just sent, do: cd /usr/src/lib/libc make make install before doing a buildworld. This probably isn't the correct way of resolving such bootstrapping issues, but it works. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 13:22:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D492315563 for ; Wed, 12 Jan 2000 13:22:48 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id IAA06448; Thu, 13 Jan 2000 08:21:57 +1100 Date: Thu, 13 Jan 2000 08:21:54 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Wilko Bulte Cc: "FreeBSD_current, mailing list" Subject: Re: mkdep error in sio.c on Alpha? In-Reply-To: <20000112210005.A1850@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, Wilko Bulte wrote: > -current supped 10 minutes ago gives during make depend: > > c ../../isa/vga_isa.c ../../kern/subr_diskmbr.c ../../libkern/bcmp.c > ../../libkern/ffs.c ioconf.c param.c vnode_if.c config.c > ../../alpha/alpha/genassym.c > ../../isa/sio.c:2926: macro `CONS_DRIVER' used with only 7 args Oops. Add a NULL arg at the end for the __alpha__ case. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 13:30:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeep.ti.com (gatekeep.ti.com [192.94.94.61]) by hub.freebsd.org (Postfix) with ESMTP id A86491541A for ; Wed, 12 Jan 2000 13:30:48 -0800 (PST) (envelope-from ntakpe@ffab.tide.ti.com) Received: from dlep9.itg.ti.com ([157.170.135.38]) by gatekeep.ti.com (8.9.3/8.9.3) with ESMTP id PAA10685; Wed, 12 Jan 2000 15:28:53 -0600 (CST) Received: from dlep9.itg.ti.com (localhost [127.0.0.1]) by dlep9.itg.ti.com (8.9.3/8.9.3) with ESMTP id PAA02062; Wed, 12 Jan 2000 15:28:53 -0600 (CST) Received: from wrks2host.ffab.tide.ti.com (wrks2host.ffab.tide.ti.com [137.167.200.37]) by dlep9.itg.ti.com (8.9.3/8.9.3) with ESMTP id PAA02058; Wed, 12 Jan 2000 15:28:51 -0600 (CST) Received: from ishtar.ffab.tide.ti.com (ishtar.ffab.tide.ti.com [137.167.200.61]) by wrks2host.ffab.tide.ti.com (8.8.8+Sun/8.8.8) with ESMTP id WAA07144; Wed, 12 Jan 2000 22:28:49 +0100 (MET) Received: from ishtar.ffab.tide.ti.com (IDENT:ntakpe@ishtar.ffab.tide.ti.com [137.167.200.61]) by ishtar.ffab.tide.ti.com (8.9.3/8.9.3) with ESMTP id WAA21691; Wed, 12 Jan 2000 22:28:48 +0100 Message-ID: <387CF210.5AE18784@ishtar.ffab.tide.ti.com> Date: Wed, 12 Jan 2000 22:28:48 +0100 From: Jean Louis Ntakpe Organization: TI Freising - Automation Group X-Sender: "Jean Louis Ntakpe" <@ishtar.ffab.tide.ti.com> (Unverified) X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i586) X-Accept-Language: en MIME-Version: 1.0 To: "Rodney W. Grimes" Cc: David Malone , mb@imp.ch, dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: move portmap(8) from /usr/sbin to /sbin References: <200001121724.JAA28817@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" wrote: ... > > Independent of order of export/mounting the dead lock occurs. Cross > mounting via NFS is a verbotten thing in the sysadmin world of production > systems. :-) I have had to fix it at several sites admin'd by newbies... > I'm not sure you are really understanding the problem. We don't want to read RFCs or such professional sysadmin red books... Sometimes we just want to nfs-mount things on the same machine. One more example: I don't like /var/news so I mount locally /var/news to /archive/news on the same system instead of using symlinks. My rc.local manages it for me. But, is it really so difficult to move portmap to /sbin. Why? Linux have portmap in /sbin and it runs. regards, -- Jean Louis Ntakpe Texas Instruments - Freising Wafer Fab Automation Group Haggerty Str. 1 85350 Freising Telefon +49 (8161) 80-3816 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 13:51:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 14FD114D91 for ; Wed, 12 Jan 2000 13:51:49 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA75948; Wed, 12 Jan 2000 16:51:33 -0500 (EST) (envelope-from wollman) Date: Wed, 12 Jan 2000 16:51:33 -0500 (EST) From: Garrett Wollman Message-Id: <200001122151.QAA75948@khavrinen.lcs.mit.edu> To: Garance A Drosihn Cc: "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: Additional option to ls -l for large files In-Reply-To: References: <200001120201.SAA26378@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > In 'ls' we are not talking about a block count, we are talking about > a byte-count. ls -s -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 14:45:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 9EF351504E for ; Wed, 12 Jan 2000 14:45:52 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA70144; Wed, 12 Jan 2000 17:45:29 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200001122151.QAA75948@khavrinen.lcs.mit.edu> References: <200001120201.SAA26378@gndrsh.dnsmgr.net> <200001122151.QAA75948@khavrinen.lcs.mit.edu> Date: Wed, 12 Jan 2000 17:45:51 -0500 To: Garrett Wollman From: Garance A Drosihn Subject: Re: Additional option to ls -l for large files Cc: "Rodney W. Grimes" , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:51 PM -0500 1/12/00, Garrett Wollman wrote: >< said: > > > In 'ls' we are not talking about a block count, we are talking about > > a byte-count. > >ls -s Hmm, valid point. 'ls -l' is not using a block count though, and so all of my previous comments still make sense for 'ls -l' and the new option. 'ls -s' and the new option should follow a block count, but then 'ls -s' is showing a block count for ALL files that it lists. The examples I gave in my previous message don't end up as confusing for 'ls -s' as they do for 'ls -l'. Maybe the new option should not even apply to 'ls -s'? I have no preference for 'ls -s' behavior. In any case, I'm still saying that in practice, people will find it less confusing if 'ls -l' used 1000 as the divisor, not 1024. Or at least, I found it less confusing, when I have done this same thing. Yes, it may be "more pure" to use 1024 when comparing 'ls' listings to block counts, but it is less confusing WITHIN a single 'ls -l' listing if all the numbers are decimal, and not some combination of base-10 and base-2. 'ls -l' listings (without the -s...) are already a problem when comparing to 'du' or 'df' listings. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 14:51:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id ECF7C14D32 for ; Wed, 12 Jan 2000 14:51:50 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA64008; Wed, 12 Jan 2000 17:50:40 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Wed, 12 Jan 2000 17:51:01 -0500 To: Robert Watson From: Garance A Drosihn Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test Cc: Alfred Perlstein , Andre Albsmeier , Warner Losh , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Back on December 27, 1999, Garance A Drosihn wrote: >At 8:55 AM -0500 12/24/99, Robert Watson wrote: >>For example, imagine that the user has a >>number of hard links to the file in question. > > Okay, here's my newer version of the code, which takes > into account multiple hard links, and also makes it so > the spooled data file is owned by daemon instead of the > user. This works fine. Has anyone had a chance to look at this? It does work for me, and I think it addressed all security concerns, so if no one else has any comments I'll send it in as an update to the original PR. (I hate to resend the whole patch in a second message to this list, but if anyone missed my earlier message then let me know and I'll send the patch to you to review). --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 15: 0:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from xena.cs.waikato.ac.nz (xena.cs.waikato.ac.nz [130.217.241.20]) by hub.freebsd.org (Postfix) with ESMTP id BA03415542 for ; Wed, 12 Jan 2000 15:00:28 -0800 (PST) (envelope-from joerg@lucy.cs.waikato.ac.nz) Received: from lucy.cs.waikato.ac.nz (joerg@lucy.cs.waikato.ac.nz [130.217.241.12]) by xena.cs.waikato.ac.nz (8.9.3/8.9.3) with ESMTP id MAA02627; Thu, 13 Jan 2000 12:00:25 +1300 (NZDT) Received: (from joerg@localhost) by lucy.cs.waikato.ac.nz (8.9.3/8.9.0) id MAA27058; Thu, 13 Jan 2000 12:00:20 +1300 (NZDT) Date: Thu, 13 Jan 2000 12:00:18 +1300 From: Joerg Micheel To: Garance A Drosihn Cc: current@freebsd.org Subject: Re: Additional option to ls -l for large files Message-ID: <20000113120018.H5228@cs.waikato.ac.nz> References: <200001120201.SAA26378@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Garance A Drosihn on Wed, Jan 12, 2000 at 04:21:05PM -0500 Organization: SCMS, The University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... drained by Solaris 7 SPARC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 04:21:05PM -0500, Garance A Drosihn wrote: > > The first one changes because it's over 1 megabyte, but the second > one does not change. So you get: > > -rw-r--r-- 1 gad staff 1951k Dec 11 03:39 asciiedit.c > -rw-r--r-- 1 gad staff 999123 Dec 11 03:39 asciisrch.c > > Okay now, how many people can look at those lines and immediately > see that the first file is "about" twice the size of the second > file? Probably nobody, not without pulling out a calculator. The Point taken. What about: -rw-r--r-- 1 gad staff 1951k Dec 11 03:39 asciiedit.c -rw-r--r-- 1 gad staff 999123 Dec 11 03:39 asciisrch.c or: -rw-r--r-- 1 gad staff 1951k Dec 11 03:39 asciiedit.c -rw-r--r-- 1 gad staff 999123 Dec 11 03:39 asciisrch.c I can see Oliver's proposal making a lot of sense here, the more since we avoid the discussion about K/M/G/T being base 2 or 10. Joerg -- Joerg B. Micheel Email: Waikato Applied Network Dynamics Phone: +64 7 8384794 The University of Waikato, CompScience Fax: +64 7 8384155 Private Bag 3105 Pager: +64 868 38222 Hamilton, New Zealand Plan: TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 15:23:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id D0BEF150A0 for ; Wed, 12 Jan 2000 15:23:11 -0800 (PST) (envelope-from jstock@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 62E3136D4 for ; Wed, 12 Jan 2000 17:22:54 -0600 (CST) Received: from localhost (jstock@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id RAA17524 for ; Wed, 12 Jan 2000 17:22:54 -0600 (CST) X-Authentication-Warning: isis.visi.com: jstock owned process doing -bs Date: Wed, 12 Jan 2000 17:22:54 -0600 (CST) From: "Jeremy L. Stock" To: freebsd-current@FreeBSD.ORG Subject: ViBRA16X Problems again after a make world yesterday Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't seen any reports of this yet. After a make world yesterday, I hear stuttered sound from RealPlayer G2 and xmms won't play anything at all. I tried to figure out when it was broken but didn't have any luck. It worked fine after my last make world on December 27th. -- Jeremy L. Stock ICQ 46329337 Fax # 612-629-6540 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 15:32:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 6C20314EF1; Wed, 12 Jan 2000 15:32:00 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA14722; Thu, 13 Jan 2000 00:13:18 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA45138; Thu, 13 Jan 2000 00:16:31 +0100 (CET) (envelope-from wilko) Date: Thu, 13 Jan 2000 00:16:31 +0100 From: Wilko Bulte To: Jason Evans Cc: Mark Murray , obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Make world breakage... Message-ID: <20000113001631.C4148@yedi.iaf.nl> References: <200001121956.e0CJuNw65075@gratis.grondar.za> <20000112220725.A2942@yedi.iaf.nl> <20000112132225.T302@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000112132225.T302@sturm.canonware.com>; from jasone@canonware.com on Wed, Jan 12, 2000 at 01:22:25PM -0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 01:22:25PM -0800, Jason Evans wrote: > On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote: > > On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote: > > > Hi > > > > > > Anyone else seeing this? ... > > /usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o) > > In function `_gettemp': > > mktemp.c(.text+0x3f0): undefined reference to `_libc_open' > > mktemp.c(.text+0x3f4): undefined reference to `_libc_open' > > *** Error code 1 > > > > Stop in /usr/src/gnu/usr.bin/cc/cpp. > > *** Error code 1 > > libc successfully builds on Alpha with the changes I committed, though the > bootstrapping problem issue is the same. As noted in another email I just > sent, do: I had to add: cd /usr/src make includes before the following worked: > cd /usr/src/lib/libc > make make went OK. > make install make install did not work, maybe I should not do this multiuser? miata#make install install -c -o root -g wheel -m 444 libc.a /usr/lib install -c -o root -g wheel -m 444 libc_p.a /usr/lib install -c -s -o root -g wheel -m 444 libc.so.4 /usr/lib /usr/libexec/ld-elf.so.1: /usr/lib/libc.so.4: Undefined symbol "_libc_open" *** Error code 70 I copied libc.so.4 manually to /usr/lib but that is not sufficient. It looks like ld-elf sticks to libc.so.4 even if I move the symlink libc.so back from libc.so.4 to libc.so.3 > before doing a buildworld. This probably isn't the correct way of > resolving such bootstrapping issues, but it works. I'm no bootstrapping expert either, but I get the distinct feeling there should be an easier way :-( Help! For now I don't date reboot my Alpha W/ -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 15:34:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 24C0514EC5 for ; Wed, 12 Jan 2000 15:34:12 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 6506 invoked from network); 12 Jan 2000 23:34:07 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 12 Jan 2000 23:34:07 -0000 Message-ID: <387D0F51.12C8ADB9@cvzoom.net> Date: Wed, 12 Jan 2000 18:33:37 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jeremy L. Stock" Cc: freebsd-current@FreeBSD.ORG Subject: Re: ViBRA16X Problems again after a make world yesterday References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeremy L. Stock" wrote: > > I haven't seen any reports of this yet. After a make world yesterday, I hear > stuttered sound from RealPlayer G2 and xmms won't play anything at all. I > tried to figure out when it was broken but didn't have any luck. It worked > fine after my last make world on December 27th. Maybe try changing DSP_BUFFSIZE in /sys/dev/sound/pcm/sound.h. I had the same stuttering problem with my ESS 1868 when Cameron changed DSP_BUFFSIZE to 8k from 64k. Of course, it'd just be a temporary fix AND and shot in the dark, but you could try it. My ESS now works with a buffer size of 8k. What Cameron did to fix this, I don't know... -- - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 15:37:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id D1DD5150A0 for ; Wed, 12 Jan 2000 15:37:46 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40324>; Thu, 13 Jan 2000 10:29:49 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: Additional option to ls -l for large files In-reply-to: <20000113120018.H5228@cs.waikato.ac.nz>; from joerg@cs.waikato.ac.nz on Thu, Jan 13, 2000 at 09:54:17AM +1100 To: Joerg Micheel Cc: current@FreeBSD.ORG Message-Id: <00Jan13.102949est.40324@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200001120201.SAA26378@gndrsh.dnsmgr.net> <20000113120018.H5228@cs.waikato.ac.nz> Date: Thu, 13 Jan 2000 10:29:48 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Jan-13 09:54:17 +1100, Joerg Micheel wrote: >-rw-r--r-- 1 gad staff 1951k Dec 11 03:39 asciiedit.c >-rw-r--r-- 1 gad staff 999123 Dec 11 03:39 asciisrch.c You still need to mentally re-align the numbers before you can compare the sizes. >-rw-r--r-- 1 gad staff 1951k Dec 11 03:39 asciiedit.c >-rw-r--r-- 1 gad staff 999123 Dec 11 03:39 asciisrch.c This reduces the number of significant figures to a level which allows a quicker grasp of the size, but doesn't resolve the column- width problem. The other option would be to require a flag to ls to trigger the behaviour - in which case all the files use the same suffix: $ ls -l -rw-r--r-- 1 gad staff 1951456 Dec 11 03:39 asciiedit.c -rw-r--r-- 1 gad staff 999123 Dec 11 03:39 asciisrch.c $ ls -lK -rw-r--r-- 1 gad staff 1951k Dec 11 03:39 asciiedit.c -rw-r--r-- 1 gad staff 999k Dec 11 03:39 asciisrch.c $ ls -lM -rw-r--r-- 1 gad staff 2M Dec 11 03:39 asciiedit.c -rw-r--r-- 1 gad staff 1M Dec 11 03:39 asciisrch.c Conveniently, -K, -M and -G are still available. Unfortunately, -T and -P are taken (though -p isn't). I'll stay out of the 2^x vs 10^y debate. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 15:38:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 68E7314C9A for ; Wed, 12 Jan 2000 15:38:49 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 8707 invoked by uid 1001); 12 Jan 2000 23:38:31 -0000 Date: Wed, 12 Jan 2000 15:38:31 -0800 From: Jason Evans To: Wilko Bulte Cc: current@FreeBSD.ORG Subject: Re: Make world breakage... Message-ID: <20000112153831.W302@sturm.canonware.com> References: <200001121956.e0CJuNw65075@gratis.grondar.za> <20000112220725.A2942@yedi.iaf.nl> <20000112132225.T302@sturm.canonware.com> <20000113001631.C4148@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000113001631.C4148@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Thu, Jan 13, 2000 at 12:16:31AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote: > On Wed, Jan 12, 2000 at 01:22:25PM -0800, Jason Evans wrote: > > On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote: > > > On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote: > > > > Hi > > > > > > > > Anyone else seeing this? > > ... > > > > /usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o) > > > In function `_gettemp': > > > mktemp.c(.text+0x3f0): undefined reference to `_libc_open' > > > mktemp.c(.text+0x3f4): undefined reference to `_libc_open' > > > *** Error code 1 > > > > > > Stop in /usr/src/gnu/usr.bin/cc/cpp. > > > *** Error code 1 > > > > libc successfully builds on Alpha with the changes I committed, though the > > bootstrapping problem issue is the same. As noted in another email I just > > sent, do: > > I had to add: > > cd /usr/src > make includes What errors did you run into? > make install did not work, maybe I should not do this multiuser? > > miata#make install > install -c -o root -g wheel -m 444 libc.a /usr/lib > install -c -o root -g wheel -m 444 libc_p.a /usr/lib > install -c -s -o root -g wheel -m 444 libc.so.4 /usr/lib > /usr/libexec/ld-elf.so.1: /usr/lib/libc.so.4: Undefined symbol "_libc_open" > *** Error code 70 > > I copied libc.so.4 manually to /usr/lib but that is not sufficient. > It looks like ld-elf sticks to libc.so.4 even if I move the symlink > libc.so back from libc.so.4 to libc.so.3 > > > before doing a buildworld. This probably isn't the correct way of > > resolving such bootstrapping issues, but it works. > > I'm no bootstrapping expert either, but I get the distinct feeling there > should be an easier way :-( > > Help! For now I don't date reboot my Alpha Oh, that looks bad. =( I got myself into a similar fix yesterday and had to install FreeBSD on another partition to put a working libc.so.4 back in place. Keeping a spare copy of one that is known to work is a good idea. This advice comes a wee bit late... =( Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 16:23:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id BE16415035 for ; Wed, 12 Jan 2000 16:23:22 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id KAA01462; Thu, 13 Jan 2000 10:52:14 +1030 (CST) (envelope-from newton) Date: Thu, 13 Jan 2000 10:52:14 +1030 From: Mark Newton To: Tom Embt Cc: Christian Carstensen , Donn Miller , current@FreeBSD.ORG Subject: Re: why is my current so .... stable? Message-ID: <20000113105214.D1094@internode.com.au> References: <3.0.3.32.20000112082944.01636938@mail.embt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <3.0.3.32.20000112082944.01636938@mail.embt.com> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 08:29:44AM -0500, Tom Embt wrote: > >This would be great, but I wonder from what source we could take reliable > >data about -current's stability. > > How 'bout some sort of client program that is run via the rc.d and > rc.shutdown scripts? One of the more annoying aspects of IRIX in its default config is that whenever you do a halt or reboot it'd pop up a menu to ask why. That information, together with crash dump info and other data about system failures, can be funnelled into a mail filter which records historical reliability data; That data can (optionally) be sent back to SGI too. We could provide something like this, but (a) if it's on by default it'll suck rocks, and (b) if it's off by default nobody will bother turning it on. Hey ho! - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 16:27: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from castle.jp.freebsd.org (castle.jp.freebsd.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 9BF0614E09; Wed, 12 Jan 2000 16:27:02 -0800 (PST) (envelope-from matusita@jp.freebsd.org) Received: from localhost (localhost [127.0.0.1]) by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id JAA90355; Thu, 13 Jan 2000 09:26:56 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: obrien@FreeBSD.ORG In-Reply-To: <20000107082513.A96136@dragon.nuxi.com> References: <20000107082513.A96136@dragon.nuxi.com> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.1 XEmacs/21.2 (Toshima) X-SKK-Version: 10.52 X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) X-Fingerprint: 0C AC 93 FC E3 9D 9E 5B 3D B8 AC 5C 4A 79 D8 A6 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 991007(IM132) Lines: 18 From: Makoto MATSUSHITA To: current@freebsd.org Subject: Re: ** HEADS UP ** chown&chgrp moved again Date: Thu, 13 Jan 2000 09:26:52 +0900 Message-Id: <20000113092652F.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG obrien> A while back I moved the install location for chown and chgrp obrien> from /usr/sbin and /usr/bin to /sbin and /bin. This was obrien> because of MAKEDEV(8)'s dependence on them, and thus forced obrien> /usr to be mounted for correct operation of MAKEDEV(8). But MAKEDEV(8) still depends on mknod(8), so this change would be a "make release" breaker. In older environment, mknod(8) does not understand the new command-line syntax; it would be impossible to build today's -current in -stable or whatever version of -current before this change. Yes, it's easy to fix by "cd /usr/src/sbin/mknod; make; make install" before doing a release engineering, but it is too tricky, isn't it ? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 16:38:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 4F58A15099; Wed, 12 Jan 2000 16:38:22 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA01937; Wed, 12 Jan 2000 16:44:54 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001130044.QAA01937@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Makoto MATSUSHITA Cc: current@freebsd.org, obrien@freebsd.org Subject: Re: ** HEADS UP ** chown&chgrp moved again In-reply-to: Your message of "Thu, 13 Jan 2000 09:26:52 +0900." <20000113092652F.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 16:44:54 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > obrien> A while back I moved the install location for chown and chgrp > obrien> from /usr/sbin and /usr/bin to /sbin and /bin. This was > obrien> because of MAKEDEV(8)'s dependence on them, and thus forced > obrien> /usr to be mounted for correct operation of MAKEDEV(8). > > But MAKEDEV(8) still depends on mknod(8), so this change would be a > "make release" breaker. > > In older environment, mknod(8) does not understand the new > command-line syntax; it would be impossible to build today's -current > in -stable or whatever version of -current before this change. > > Yes, it's easy to fix by "cd /usr/src/sbin/mknod; make; make install" > before doing a release engineering, but it is too tricky, isn't it ? A release build requires a complete "make buildworld" of the relevant world to have been completed before starting. As long as 'make buildworld' for -current works on -stable, the release will work. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 16:45:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from castle.jp.freebsd.org (castle.jp.freebsd.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 9DE4F15186; Wed, 12 Jan 2000 16:45:14 -0800 (PST) (envelope-from matusita@jp.freebsd.org) Received: from localhost (localhost [127.0.0.1]) by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id JAA91262; Thu, 13 Jan 2000 09:45:12 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: matusita@jp.freebsd.org, current@freebsd.org, obrien@freebsd.org In-Reply-To: <200001130044.QAA01937@mass.cdrom.com> References: <20000113092652F.matusita@jp.FreeBSD.org> <200001130044.QAA01937@mass.cdrom.com> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.1 XEmacs/21.2 (Toshima) X-SKK-Version: 10.52 X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) X-Fingerprint: 0C AC 93 FC E3 9D 9E 5B 3D B8 AC 5C 4A 79 D8 A6 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 991007(IM132) Lines: 11 From: Makoto MATSUSHITA To: msmith@freebsd.org Subject: Re: ** HEADS UP ** chown&chgrp moved again Date: Thu, 13 Jan 2000 09:45:09 +0900 Message-Id: <20000113094509A.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG msmith> A release build requires a complete "make buildworld" of the msmith> relevant world to have been completed before starting. Not "make buildworld" but "make installworld" ? In anyway, "make distrib-dirs distribution" depends on some tools (not only mknod), and it's no way to install these tools before everything is going on, this assumption is quite reasonable. Sorry and thank you for the quick reply. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 16:51: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id ACDFF15557 for ; Wed, 12 Jan 2000 16:51:04 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id LAA01682; Thu, 13 Jan 2000 11:19:47 +1030 (CST) (envelope-from newton) Date: Thu, 13 Jan 2000 11:19:47 +1030 From: Mark Newton To: Glendon Gross Cc: freebsd-current@freebsd.org Subject: Re: newpcm Message-ID: <20000113111947.E1094@internode.com.au> References: <20000112103028.G2420@internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 10:08:17AM -0800, Glendon Gross wrote: > Are there any tricks to enabling Awe64 support? I initially removed my > Awe64 card from my first FreeBSD machine to avoid interrupt conflicts, and > now I would like to try to integrate it back again. Would you mind > sending me your /sys/i386/conf/GENERIC or correct kernel build file? > Thanks! --Glen Gross The relevent bit from my kernel config is: device pcm0 :-) Way back in the dim dark ages I used to use a boot.config command which set it to "os" configuration mode and explicity configured IRQ, DRQ's and port numbers to the same values I was using in my old "controller sbc0" configuration line, but I don't need to do that anymore. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 16:53: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 736E714D15; Wed, 12 Jan 2000 16:53:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA02157; Wed, 12 Jan 2000 16:59:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001130059.QAA02157@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Makoto MATSUSHITA Cc: msmith@freebsd.org, current@freebsd.org, obrien@freebsd.org Subject: Re: ** HEADS UP ** chown&chgrp moved again In-reply-to: Your message of "Thu, 13 Jan 2000 09:45:09 +0900." <20000113094509A.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 16:59:35 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > msmith> A release build requires a complete "make buildworld" of the > msmith> relevant world to have been completed before starting. > > Not "make buildworld" but "make installworld" ? No. I said "make buildworld". > In anyway, "make > distrib-dirs distribution" depends on some tools (not only mknod), and > it's no way to install these tools before everything is going on, this > assumption is quite reasonable. Sorry and thank you for the quick reply. The chroot area is populated via "make installworld" from the abovementioned buildworld. The mknod that is then used to build device nodes is the one inside the chroot area. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 16:59:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from castle.jp.freebsd.org (castle.jp.freebsd.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 5577F14D16; Wed, 12 Jan 2000 16:59:42 -0800 (PST) (envelope-from matusita@jp.freebsd.org) Received: from localhost (localhost [127.0.0.1]) by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id JAA91721; Thu, 13 Jan 2000 09:59:41 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: matusita@jp.freebsd.org, current@freebsd.org, obrien@freebsd.org In-Reply-To: <200001130059.QAA02157@mass.cdrom.com> References: <20000113094509A.matusita@jp.FreeBSD.org> <200001130059.QAA02157@mass.cdrom.com> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.1 XEmacs/21.2 (Toshima) X-SKK-Version: 10.52 X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) X-Fingerprint: 0C AC 93 FC E3 9D 9E 5B 3D B8 AC 5C 4A 79 D8 A6 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 991007(IM132) Lines: 13 From: Makoto MATSUSHITA To: msmith@freebsd.org Subject: Re: ** HEADS UP ** chown&chgrp moved again Date: Thu, 13 Jan 2000 09:59:37 +0900 Message-Id: <20000113095937N.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG msmith> No. I said "make buildworld". Ah, sorry, I must say "make installworld in the process of make release". msmith> The chroot area is populated via "make installworld" from the msmith> abovementioned buildworld. The mknod that is then used to msmith> build device nodes is the one inside the chroot area. Exactly. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 17: 3:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 41D6A14A1E for ; Wed, 12 Jan 2000 17:03:54 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 13 Jan 2000 01:03:53 +0000 (GMT) Date: Thu, 13 Jan 2000 01:03:52 +0000 From: David Malone To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: R/W mount of / denied, filesystem not clean (after fsck) Message-ID: <20000113010352.A63221@walton.maths.tcd.ie> References: <200001121956.e0CJuNw65075@gratis.grondar.za> <200001121958.LAA74096@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001121958.LAA74096@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Jan 12, 2000 at 11:58:34AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 11:58:34AM -0800, Matthew Dillon wrote: > Hmm. I was under the impression that this problem was fixed, but I am > getting it again. When I have a crash and reboot fsck runs through > all the filesystems but then mount refuses to mount / thinking that it's > dirty when it isn't. Looking at "ls -l /dev | grep ^b" was the most useful startpoing I got from the list last time it happened to me. (Mind you, the hotroot stuff in fsck seems to have changed since then). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 17: 5:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from grace.speakeasy.org (grace.speakeasy.org [216.254.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 54F4514D71; Wed, 12 Jan 2000 17:05:08 -0800 (PST) (envelope-from seanj@speakeasy.org) Received: from localhost (seanj@localhost) by grace.speakeasy.org (8.9.3/8.9.3) with ESMTP id RAA16477; Wed, 12 Jan 2000 17:04:52 -0800 Date: Wed, 12 Jan 2000 17:04:52 -0800 (PST) From: Sean Jensen-Grey To: Makoto MATSUSHITA Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: running MAKEDEV with only a / In-Reply-To: <20000113092652F.matusita@jp.FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I guess I forgot MKNOD from my list. I must have copied it to /bin so I have /usr/bin/chgrp /usr/lib/libc.so.3 /usr/libexec/ld-elf.so.1 /usr/sbin/chown /usr/sbin/chroot as being needed to run MAKEDEV in 3.4-RELEASE MAKDEV will complain while its running that it needs libgnuerex (can't remember exactly) but I was able to create a functioning /dev/wd0s1a-f with the above config without it. Can someone confirm what it takes to run MAKEDEV without a /usr on a CURRENT box? Mine is dead right now. On Thu, 13 Jan 2000, Makoto MATSUSHITA wrote: > > obrien> A while back I moved the install location for chown and chgrp > obrien> from /usr/sbin and /usr/bin to /sbin and /bin. This was > obrien> because of MAKEDEV(8)'s dependence on them, and thus forced > obrien> /usr to be mounted for correct operation of MAKEDEV(8). > > But MAKEDEV(8) still depends on mknod(8), so this change would be a > "make release" breaker. > > In older environment, mknod(8) does not understand the new > command-line syntax; it would be impossible to build today's -current > in -stable or whatever version of -current before this change. > > Yes, it's easy to fix by "cd /usr/src/sbin/mknod; make; make install" > before doing a release engineering, but it is too tricky, isn't it ? > > -- - > Makoto `MAR' MATSUSHITA > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 17: 6: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id BD8FD14DF9 for ; Wed, 12 Jan 2000 17:06:06 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 8993 invoked by uid 1001); 13 Jan 2000 01:05:49 -0000 Date: Wed, 12 Jan 2000 17:05:49 -0800 From: Jason Evans To: Wilko Bulte Cc: current@freebsd.org Subject: Re: Make world breakage... Message-ID: <20000112170549.Y302@sturm.canonware.com> References: <200001121956.e0CJuNw65075@gratis.grondar.za> <20000112220725.A2942@yedi.iaf.nl> <20000112132225.T302@sturm.canonware.com> <20000113001631.C4148@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000113001631.C4148@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Thu, Jan 13, 2000 at 12:16:31AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote: > On Wed, Jan 12, 2000 at 01:22:25PM -0800, Jason Evans wrote: > > On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote: > > > On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote: > > > > Hi > > > > > > > > Anyone else seeing this? > > ... > > > > /usr/obj/usr/src/alpha/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o) > > > In function `_gettemp': > > > mktemp.c(.text+0x3f0): undefined reference to `_libc_open' > > > mktemp.c(.text+0x3f4): undefined reference to `_libc_open' > > > *** Error code 1 > > > > > > Stop in /usr/src/gnu/usr.bin/cc/cpp. > > > *** Error code 1 > > > > libc successfully builds on Alpha with the changes I committed, though the > > bootstrapping problem issue is the same. On further inspection, though libc builds on the Alpha, I'm guessing that terrible breakage results if it is installed. The Alpha I was testing on isn't mine, and I was afraid to mess things up, so I tested the build of libc, but did all installation and program testing with libc_r. The problem is that SYS.h for the Alpha doesn't define the _libc_*() aliases for system calls, which libc now uses. I'll try to get this fixed today if possible. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 17:22:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 3580214D24 for ; Wed, 12 Jan 2000 17:22:32 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 9053 invoked by uid 1001); 13 Jan 2000 01:22:13 -0000 Date: Wed, 12 Jan 2000 17:22:13 -0800 From: Jason Evans To: current@freebsd.org Subject: RFC: buildworld breakage due to cross-tools/libc/mktemp. Message-ID: <20000112172213.Z302@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The buildworld problem that I introduced is due to cc_fbsd directly compiling and linking in src/lib/libc/stdio/mktemp.c. This is in my opinion a questionable practice, since it adds dependencies to the internals of the libc code, which has just been proven to bite. =) Aesthetics aside, I'm not sure what the best fix for the problem is. Options include: 1) Ignore the problem, since it only happens once, and has a work-around. This is probably not a good idea, since it makes the upgrade path bumpy. 2) Make a separate copy of mktemp.c to remove the internal dependency. I'm not familiar with the detailed semantics of mktemp() but this may be a problem if mktemp() is required to behave the same across all programs, and the two versions of mktemp.c diverge. 3) Add conditional compilation, such that the macro _libc_open=open is defined during the cross-tools stage. I tried this, but wasn't able to find an obvious way of inserting it into the build system. Besides, it's a bit of a hack, and doesn't address the core issue (dependency on libc internals). 4) Build a libc for the cross-tools stage that all the targets for that stage can be linked against. This looks cleanest to me, but adds substantially to build time and may be difficult to implement. Suggestions are welcome. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 17:25:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 93C8114C3C for ; Wed, 12 Jan 2000 17:25:26 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA23452; Wed, 12 Jan 2000 17:25:22 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA21665; Wed, 12 Jan 2000 17:25:22 -0800 (PST) (envelope-from obrien) Date: Wed, 12 Jan 2000 17:25:22 -0800 From: "David O'Brien" To: Wilko Bulte Cc: current@FreeBSD.ORG Subject: Re: Make world breakage... Message-ID: <20000112172522.A21639@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001121956.e0CJuNw65075@gratis.grondar.za> <20000112220725.A2942@yedi.iaf.nl> <20000112132225.T302@sturm.canonware.com> <20000113001631.C4148@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000113001631.C4148@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Thu, Jan 13, 2000 at 12:16:31AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote: > I copied libc.so.4 manually to /usr/lib but that is not sufficient. > It looks like ld-elf sticks to libc.so.4 even if I move the symlink > libc.so back from libc.so.4 to libc.so.3 Yes. Each shared library knows it's name when it was compiled (minor hand waving here). The linker then burns the shlib name (not file name, but shlib name gotten from a header in the shlib. You can change the shlib name by using a hex/binary editor on the shlib. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 19: 0:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7210C150AC for ; Wed, 12 Jan 2000 19:00:06 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA04987; Wed, 12 Jan 2000 19:00:02 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA74514; Wed, 12 Jan 2000 19:00:01 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 12 Jan 2000 19:00:01 -0800 (PST) Message-Id: <200001130300.TAA74514@vashon.polstra.com> To: jasone@canonware.com Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. In-Reply-To: <20000112172213.Z302@sturm.canonware.com> References: <20000112172213.Z302@sturm.canonware.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000112172213.Z302@sturm.canonware.com>, Jason Evans wrote: > The buildworld problem that I introduced is due to cc_fbsd directly > compiling and linking in src/lib/libc/stdio/mktemp.c. This is in my > opinion a questionable practice, since it adds dependencies to the > internals of the libc code, which has just been proven to bite. =) Yes, I agree. > Aesthetics aside, I'm not sure what the best fix for the problem is. > Options include: > > 1) Ignore the problem, since it only happens once, and has a work-around. > This is probably not a good idea, since it makes the upgrade path > bumpy. Yes, please avoid this if at all possible. We've had too many of these "one-time" special procedures in the past year. Committers haven't been trying hard enough to avoid them, IMHO. The trouble with special upgrade procedures is that they linger for a year beyond when the problem began, as different users try upgrading and run into trouble. Also, they're a big PITA for system admins who have many machines to upgrade. > 2) Make a separate copy of mktemp.c to remove the internal dependency. I think this is the best approach -- likewise for getobjformat.c, which is also used currently. I _really_ don't like it when a program reaches waaaaaaay over into an unrelated directory for its sources. This isn't the first time it has caused unexpected problems. If you change the internals of a self-contained subtree, you should reasonably be able to assume that it won't break something on the other side of the source tree. I'd rather have a few duplicated sources. > I'm not familiar with the detailed semantics of mktemp() but > this may be a problem if mktemp() is required to behave the same > across all programs, and the two versions of mktemp.c diverge. I'd still rather have a few duplicated sources. > > 3) Add conditional compilation, such that the macro _libc_open=open is > defined during the cross-tools stage. I tried this, but wasn't able to > find an obvious way of inserting it into the build system. Besides, > it's a bit of a hack, and doesn't address the core issue (dependency on > libc internals). Right. Ick. > 4) Build a libc for the cross-tools stage that all the targets for that > stage can be linked against. This looks cleanest to me, but adds > substantially to build time and may be difficult to implement. 5) Maintainers of the build tools should be very careful to ensure that their tools use only the minimum, universally-available functionality from libc. That means (ideally) only functions which appear in the ANSI/ISO C standard, or (tolerably) only functions which appear in ANSI/ISO C or POSIX. This means: if you need a FreeBSD-specific function such as getobjformat() then you write your own version of it, or copy the source and maintain it separately, or look for a different approach. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 19: 2:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 7E3E114E8E for ; Wed, 12 Jan 2000 19:02:12 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id WAA76792; Wed, 12 Jan 2000 22:01:57 -0500 (EST) (envelope-from wollman) Date: Wed, 12 Jan 2000 22:01:57 -0500 (EST) From: Garrett Wollman Message-Id: <200001130301.WAA76792@khavrinen.lcs.mit.edu> To: Garance A Drosihn Cc: Garrett Wollman , "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: Additional option to ls -l for large files In-Reply-To: References: <200001120201.SAA26378@gndrsh.dnsmgr.net> <200001122151.QAA75948@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Yes, it may be "more pure" to use 1024 when comparing 'ls' listings > to block counts, but it is less confusing WITHIN a single 'ls -l' > listing if all the numbers are decimal, and not some combination of > base-10 and base-2. OK, let's try again. BLOCKSIZE=1000 ls -s Actually, this doesn't quite do what one would want, either -- the remainder is always rounded up, so a file which takes 1024 bytes even shows up as two 1000-blocks. However, it does do the right thing for large block sizes: wollman@khavrinen$ BLOCKSIZE=1M df / Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/wd0s1a 93 28 56 34% / wollman@khavrinen$ BLOCKSIZE=1000000 df / Filesystem 1000000-blocks Used Avail Capacity Mounted on /dev/wd0s1a 97 30 59 34% / -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 21:16:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7A32814E20 for ; Wed, 12 Jan 2000 21:16:27 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id VAA24638; Wed, 12 Jan 2000 21:16:25 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id VAA22974; Wed, 12 Jan 2000 21:16:25 -0800 (PST) (envelope-from obrien) Date: Wed, 12 Jan 2000 21:16:25 -0800 From: "David O'Brien" To: jasone@canonware.com, current@freebsd.org Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. Message-ID: <20000112211625.A21988@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000112172213.Z302@sturm.canonware.com> <200001130300.TAA74514@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001130300.TAA74514@vashon.polstra.com>; from jdp@polstra.com on Wed, Jan 12, 2000 at 07:00:01PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 07:00:01PM -0800, John Polstra wrote: > > The buildworld problem that I introduced is due to cc_fbsd directly > > compiling and linking in src/lib/libc/stdio/mktemp.c. This is in my > > opinion a questionable practice, since it adds dependencies to the > > internals of the libc code, which has just been proven to bite. =) > > Yes, I agree. I disagree. :-) I don't see why a plain function like mkstemp() should be written so specially. Couldn't all the hiding/changing done for threads be done w/in open() itself? Neither HP-UX 10.30 (which has kernel threads), nor Solaris 7 needs such open() hackery in mkstemp(). > I _really_ don't like it when a program reaches waaaaaaay over into an > unrelated directory for its sources. We already do that all over the place. :-) > I'd rather have a few duplicated sources. I dissagree. Then we have the problem of fixing a PR/bug in one source but not the other. The use/making of temperary files is already a security issue. I can just see it happen that someone fixes a problem with one copy of the source and then we find we still have some vulerabiltity because the second copy wasn't known/found/fixed. > 5) Maintainers of the build tools should be very careful to ensure > that their tools use only the minimum, universally-available > functionality from libc. GNU provides a copy of mkstemps() in libiberty. It looks like I should reconsider importing it *again*. The problem is there is no one true "libiberty". Rather than being an offical library maintained as itself, "libiberty" is what any GNU program calls the libarary of "compatibility"/portability functions needs. Thus libiberty in binutils is a totally different beast than the GCC 2.95 libiberty, than the .... [oh how I wish the GNU organization would put its head on straight sometimes] -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 21:18:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from testbed.baileylink.net (testbed.baileylink.net [63.71.213.24]) by hub.freebsd.org (Postfix) with ESMTP id F066A15285 for ; Wed, 12 Jan 2000 21:17:46 -0800 (PST) (envelope-from brad@testbed.baileylink.net) Received: (from brad@localhost) by testbed.baileylink.net (8.9.3/8.9.3) id XAA87115 for freebsd-current@freebsd.org; Wed, 12 Jan 2000 23:17:47 -0600 (CST) (envelope-from brad) Date: Wed, 12 Jan 2000 23:17:47 -0600 From: Brad Guillory To: freebsd-current@freebsd.org Subject: Re: kernel panics when initializing aic7895 controller at startup. Message-ID: <20000112231746.A86402@baileylink.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cc@devcon.net on Mon, Jan 10, 2000 at 02:21:54AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a similar problem, in kernels build Monday and yesterday. I get a kernel panic when while booting, I don't know how to capture the boot messages to a file (do you) so I can not post them but this is the line that it dies on: panic: ahc0: brkadrint, scratch or SCB Memory Parity Error at seqaddr=0x0 my machine initializes ahc0 with this line earlier in the boot: ahc0 port 0xe800-0xe8ff mem 0xfebce000-0xfebcefff irq 10 @ device 15.0 on pci0 there is a similar line for ahc1. My kernel from 12/12/99 reports this: ahc0: irq 10 at device 15.0 on pci0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 255 SCBs ahc1: irq 11 at device 15.1 on pci0 ahc1: aic7895 Wide Channel B, SCSI Id=7, 255 SCBs Does anyone have a workaround? BMG On Mon, Jan 10, 2000 at 02:21:54AM +0100, Christian Carstensen wrote: > > hi, > > with the latest changes to src/sys/pci/pci_ahc.c (partity error handling), > i'm unable to boot a current kernel, because of panic during system boot. > > i've attached dmesg from a working kernel version (2000/01/06) to this > mail. marked with (***) you'll find the line, where (with the new kernel) > the error message > "ahc0: brkadrintr, Data-path Parity Error at seqaddr = 0x14e" > occurs. > > any ideas, that could help? > > -- > Christian > > ... > ahc0: irq 16 at device 18.0 on pci0 > ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc1: irq 16 at device 18.1 on pci0 > ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs > ... > Waiting 5 seconds for SCSI devices to settle > SMP: AP CPU #1 Launched! > da1 at ahc0 bus 0 target 2 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.000MB/s transfers (10.000MHz, offset 8) > da1: 1042MB (2134305 512 byte sectors: 64H 32S/T 1042C) > Mounting root from ufs:/dev/da0a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da0: 1003MB (2055035 512 byte sectors: 64H 32S/T 1003C) > cd0 at ahc0 bus 0 target 4 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 8.333MB/s transfers (8.333MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed > da2 at ahc1 bus 0 target 0 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > da2: 4134MB (8467200 512 byte sectors: 64H 32S/T 4134C) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 21:42: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 9654714E20 for ; Wed, 12 Jan 2000 21:42:02 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA31067; Wed, 12 Jan 2000 21:41:47 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001130541.VAA31067@gndrsh.dnsmgr.net> Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: <387CF210.5AE18784@ishtar.ffab.tide.ti.com> from Jean Louis Ntakpe at "Jan 12, 2000 10:28:48 pm" To: ntakpe@ffab.tide.ti.com (Jean Louis Ntakpe) Date: Wed, 12 Jan 2000 21:41:47 -0800 (PST) Cc: dwmalone@maths.tcd.ie (David Malone), mb@imp.ch, dillon@apollo.backplane.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Rodney W. Grimes" wrote: > ... > > > > Independent of order of export/mounting the dead lock occurs. Cross > > mounting via NFS is a verbotten thing in the sysadmin world of production > > systems. :-) I have had to fix it at several sites admin'd by newbies... > > > > I'm not sure you are really understanding the problem. We > don't want > to read RFCs or such professional sysadmin red books... But a lot of us around here do just that, don't expect us to make changes just because it suites _your_ needs as that change may very well not suite the _other_ 95% of the users. > > Sometimes we just want to nfs-mount things on the same > machine. Sick, poor in performance and the wrong tool for the job. See mount_null(8) for more details on how to do it right. > > One more example: I don't like /var/news so I mount locally > /var/news > to /archive/news on the same system instead of using > symlinks. > My rc.local manages it for me. Sick. See above. > > But, is it really so difficult to move portmap to /sbin. It is not difficult to move the binary. The difficulty is in changing the sequence of events that control when the binary is run. No one here has objected to moving the binary that I have seen, it has been changing when things occur. > Why? portmap/mountd are heavy users of syslog, you _should_ have syslogd running before portmap/mountd. syslogd is started between network_pass1 and network_pass2. > Linux have portmap in /sbin and it runs. That argument holds 0 ground here. And it's not the objection to your change we raised. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 21:53: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 437A414D67 for ; Wed, 12 Jan 2000 21:52:58 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA31097; Wed, 12 Jan 2000 21:52:51 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001130552.VAA31097@gndrsh.dnsmgr.net> Subject: Re: Additional option to ls -l for large files In-Reply-To: <8070C3A4E99ED211A63200105A19B99B3174AA@mail.edifecs.com> from Michael VanLoon at "Jan 12, 2000 03:20:39 pm" To: MichaelV@EDIFECS.COM (Michael VanLoon) Date: Wed, 12 Jan 2000 21:52:50 -0800 (PST) Cc: drosih@rpi.edu ('Garance A Drosihn'), wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Charset iso-8859-1 unsupported, filtering to ASCII...] > I'm sorry but I would find it non-obvious and more confusing. When ls or a > similar disk/memory utility tells me xxxK or xxxM, I would expect it to be > in 2^10 or 2^20 units. To appear otherwise would surprise me. I guess you get suprised a lot then. The only folks that I know of who regulary use K and M as base 10 when talking about disk and memory are the disk drive manufactures. Does you machine have 128MB or 134MB. You must have missed this earlier in the thread.... All of the boot time reporting is in 2^20 MB: ad0: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S Due the math if you doubt me, oh, and Quantum calls this a 3.2G disk drive :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 21:54:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from swan.en-bio.com.au (swan.en-bio.com.au [203.35.254.3]) by hub.freebsd.org (Postfix) with ESMTP id 65442152B4 for ; Wed, 12 Jan 2000 21:54:48 -0800 (PST) (envelope-from Tony.Maher@eBioinformatics.com) Received: from shad.internal.en-bio (www-cache.en-bio.com.au [203.35.254.2]) by swan.en-bio.com.au (8.9.1a/8.9.1) with ESMTP id QAA10776; Thu, 13 Jan 2000 16:54:38 +1100 Received: (from tonym@localhost) by shad.internal.en-bio (8.9.1b+Sun/8.9.1) id QAA11037; Thu, 13 Jan 2000 16:54:21 +1100 (EST) Date: Thu, 13 Jan 2000 16:54:21 +1100 (EST) From: Tony Maher Message-Id: <200001130554.QAA11037@shad.internal.en-bio> To: freebsd@gndrsh.dnsmgr.net Cc: current@FreeBSD.ORG Subject: Re: move portmap(8) from /usr/sbin to /sbin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sick, poor in performance and the wrong tool for the job. > See mount_null(8) for more details on how to do it right. Yes its perfect for the job apart from: man mount_null THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET. This code also needs an owner in order to be less dangerous - serious hackers can apply by sending mail to hackers@freebsd.org and announcing their intent to take it over. I actually tried it a few weeks ago and yes it did screw up files :-( (that was on stable - my current box is broken but checking CVS man page it looks like the warning still applies) But I'd be happy to hear it works on current! tonym To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 22:58:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A68E415291 for ; Wed, 12 Jan 2000 22:58:07 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 128eCk-000OQY-00; Thu, 13 Jan 2000 08:57:58 +0200 From: Sheldon Hearn To: Jean Louis Ntakpe Cc: current@FreeBSD.ORG Subject: Re: NTP4 manual pages committed In-reply-to: Your message of "Wed, 12 Jan 2000 22:10:07 +0100." <387CEDAF.B8BCEFFB@ishtar.ffab.tide.ti.com> Date: Thu, 13 Jan 2000 08:57:58 +0200 Message-ID: <93901.947746678@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000 22:10:07 +0100, Jean Louis Ntakpe wrote: > # Server is a Boeder DCF77 receiver > server 127.127.8.41 Does your server look like any of those listed in reflock.htm? Most of the documentation for your application has not been transcribed into manual page format. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 12 23:34:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 9BD2B15570; Wed, 12 Jan 2000 23:34:06 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id IAA32031; Thu, 13 Jan 2000 08:31:45 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id IAA50203; Thu, 13 Jan 2000 08:30:24 +0100 (CET) (envelope-from wilko) Date: Thu, 13 Jan 2000 08:30:24 +0100 From: Wilko Bulte To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: Make world breakage... Message-ID: <20000113083024.A50096@yedi.iaf.nl> References: <200001121956.e0CJuNw65075@gratis.grondar.za> <20000112220725.A2942@yedi.iaf.nl> <20000112132225.T302@sturm.canonware.com> <20000113001631.C4148@yedi.iaf.nl> <20000112172522.A21639@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000112172522.A21639@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Wed, Jan 12, 2000 at 05:25:22PM -0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 05:25:22PM -0800, David O'Brien wrote: > On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote: > > I copied libc.so.4 manually to /usr/lib but that is not sufficient. > > It looks like ld-elf sticks to libc.so.4 even if I move the symlink > > libc.so back from libc.so.4 to libc.so.3 > > Yes. Each shared library knows it's name when it was compiled (minor > hand waving here). The linker then burns the shlib name (not file name, > but shlib name gotten from a header in the shlib. The linker burns the shlib name into the executable it links, right? Then why don't my executables linked end of december with libc.so.3 work anymore? Essentially everything linked shared is now broken. And I have only built/installed libc.so.4 (I did not get any further :/) and not any executables. So, why are the 'old' executablas no longer working happily with libc.so.3 they are linked to? Wilko ('puzzled') -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 0:59:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 3706C14D67 for ; Thu, 13 Jan 2000 00:59:43 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id AAA31395; Thu, 13 Jan 2000 00:59:36 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001130859.AAA31395@gndrsh.dnsmgr.net> Subject: Re: Additional option to ls -l for large files In-Reply-To: <8070C3A4E99ED211A63200105A19B99B3174B1@mail.edifecs.com> from Michael VanLoon at "Jan 13, 2000 00:14:02 am" To: MichaelV@EDIFECS.COM (Michael VanLoon) Date: Thu, 13 Jan 2000 00:59:35 -0800 (PST) Cc: drosih@rpi.edu, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I will slow down my reading and stop flipping 2^10 into 10^3. > From: Rodney W. Grimes [mailto:freebsd@gndrsh.dnsmgr.net] > Sent: Wednesday, January 12, 2000 9:53 PM > > > [in regards to a previous post preferring base-10 for K and M units...] > >> I'm sorry but I would find it non-obvious and more confusing. When ls or > a > >> similar disk/memory utility tells me xxxK or xxxM, I would expect it to > be > >> in 2^10 or 2^20 units. To appear otherwise would surprise me. > > >I guess you get suprised a lot then. The only folks that I know of who > >regulary use K and M as base 10 when talking about disk and memory are > >the disk drive manufactures. > > > >Does you machine have 128MB or 134MB. You must have missed this earlier > >in the thread.... > > > >All of the boot time reporting is in 2^20 MB: > >ad0: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S > > > >Due the math if you doubt me, oh, and Quantum calls this a 3.2G disk > >drive :-) > > I think if you re-read my post you'll find that we are in vehement > agreement. I have doned the cap <|:-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 3:53:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 9E8C215090; Thu, 13 Jan 2000 03:53:29 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id GAA02549; Thu, 13 Jan 2000 06:53:25 -0500 (EST) Date: Thu, 13 Jan 2000 06:53:25 -0500 (EST) From: Daniel Eischen To: "David O'Brien" Cc: jasone@canonware.com, current@FreeBSD.ORG Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. In-Reply-To: <20000112211625.A21988@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, David O'Brien wrote: > On Wed, Jan 12, 2000 at 07:00:01PM -0800, John Polstra wrote: > > > The buildworld problem that I introduced is due to cc_fbsd directly > > > compiling and linking in src/lib/libc/stdio/mktemp.c. This is in my > > > opinion a questionable practice, since it adds dependencies to the > > > internals of the libc code, which has just been proven to bite. =) > > > > Yes, I agree. > > I disagree. :-) > I don't see why a plain function like mkstemp() should be written so > specially. Couldn't all the hiding/changing done for threads be done > w/in open() itself? Neither HP-UX 10.30 (which has kernel threads), nor > Solaris 7 needs such open() hackery in mkstemp(). Given where we want to go with pthreads, and the proposed architecture, I'm not sure why we need to have open -> _libc_open -> __open (or whatever it is). Why isn't using _open internally in libc sufficient? open is a weak symbol for _open, and libpthread can override the open (weak symbol). Trying to make a libpthread out of libc_r which is hopefully near its end of life, doesn't seem worth the effort, IMHO. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 3:56:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 5D11914A26; Thu, 13 Jan 2000 03:56:22 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca44-58.ix.netcom.com [209.111.212.186]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id DAA53788; Thu, 13 Jan 2000 03:55:59 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id DAA19829; Thu, 13 Jan 2000 03:55:52 -0800 (PST) To: Jason Evans Cc: Wilko Bulte , Mark Murray , obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Make world breakage... References: <200001121956.e0CJuNw65075@gratis.grondar.za> <20000112220725.A2942@yedi.iaf.nl> <20000112132225.T302@sturm.canonware.com> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 13 Jan 2000 03:55:49 -0800 In-Reply-To: Jason Evans's message of "Wed, 12 Jan 2000 13:22:25 -0800" Message-ID: Lines: 42 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Jason Evans * > In function `_gettemp': * > mktemp.c(.text+0x3f0): undefined reference to `_libc_open' * > mktemp.c(.text+0x3f4): undefined reference to `_libc_open' * libc successfully builds on Alpha with the changes I committed, though the * bootstrapping problem issue is the same. As noted in another email I just * sent, do: * * cd /usr/src/lib/libc * make * make install * * before doing a buildworld. This probably isn't the correct way of * resolving such bootstrapping issues, but it works. Thanks, it's getting a little further with that workaround but now I get: ======= : ln -sf libutil.so.2 /usr/obj/usr/src/i386/usr/lib/libutil.so cd /usr/src/lib; make depend; make all; make install ===> csu/i386-elf ===> libcom_err ===> libcom_err/doc ===> msun ===> libmd ===> libcrypt ===> ../secure/lib/libcrypt make: don't know how to make crypt-shs.c. Stop *** Error code 2 Stop in /usr/src/lib. *** Error code 1 : ======= (I know it's probably not your fault.) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 3:57:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 3D09214F0E for ; Thu, 13 Jan 2000 03:57:49 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca44-58.ix.netcom.com [209.111.212.186]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id DAA53949; Thu, 13 Jan 2000 03:57:47 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id DAA19838; Thu, 13 Jan 2000 03:57:43 -0800 (PST) To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: crashes References: <200001120008.QAA89430@silvia.hip.berkeley.edu> <200001120234.SAA66268@apollo.backplane.com> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 13 Jan 2000 03:57:40 -0800 In-Reply-To: Matthew Dillon's message of "Tue, 11 Jan 2000 18:34:50 -0800 (PST)" Message-ID: Lines: 33 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Matthew Dillon * I have occassionally seen this failure when setting vfs.vmiodirenable * to 1. I have not seen it otherwise. * * Please upgrade your system to the latest ffs_softdep.c, vers 1.47. This * will fix a number of other problems but may not fix this one. * * If you can reproduce this bug reliably w/ the latest ffs_softdep.c then * we may have a chance of finding it. Ok, will do. * I don't know about this one. * This is new to me too. * * Any chance you can get a kernel core dump on these machines instead * of just rebooting? And have a debug kernel for them? These are from kernel core dumps. Yes, I can compile a debug kernel. * Yes, the fsck thingy happens to me too though if this is a Dec 26 * kernel you should definitely update it -- I seem to recall something * related to fsck being fixed around that time frame and there was a * softupdates fix after that time frame for a bug occuring before the * time frame committed as well (separate from the current spate of * softupdates issues). I'm trying to do that for the last few days but "make world" never completes.... :< Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 4: 9:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id BB018150E0; Thu, 13 Jan 2000 04:09:31 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id D03951CA0; Thu, 13 Jan 2000 20:09:28 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Cc: Jason Evans , Wilko Bulte , Mark Murray , obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Make world breakage... In-Reply-To: Message from asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) of "13 Jan 2000 03:55:49 PST." Date: Thu, 13 Jan 2000 20:09:28 +0800 From: Peter Wemm Message-Id: <20000113120928.D03951CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Satoshi - Ports Wraith - Asami wrote: > * From: Jason Evans > > * > In function `_gettemp': > * > mktemp.c(.text+0x3f0): undefined reference to `_libc_open' > * > mktemp.c(.text+0x3f4): undefined reference to `_libc_open' > > * libc successfully builds on Alpha with the changes I committed, though the > * bootstrapping problem issue is the same. As noted in another email I just > * sent, do: > * > * cd /usr/src/lib/libc > * make > * make install > * > * before doing a buildworld. This probably isn't the correct way of > * resolving such bootstrapping issues, but it works. > > Thanks, it's getting a little further with that workaround but now I > get: > > ======= > : > ln -sf libutil.so.2 /usr/obj/usr/src/i386/usr/lib/libutil.so > cd /usr/src/lib; make depend; make all; make install > ===> csu/i386-elf > ===> libcom_err > ===> libcom_err/doc > ===> msun > ===> libmd > ===> libcrypt > ===> ../secure/lib/libcrypt > make: don't know how to make crypt-shs.c. Stop This is because of stale .depend files. I got into the habbit of doing a rm -rf /usr/obj/* after Marcel's changes as earlier on it seemed to be leaving stale ones behind. I don't know if this is still the case but it looks a bit like it. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 5:22: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 5A6FB14E9E for ; Thu, 13 Jan 2000 05:22:01 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id CA4461E3A; Thu, 13 Jan 2000 14:22:01 +0100 (CET) Date: Thu, 13 Jan 2000 14:22:01 +0100 From: "Dave J. Boers" To: Matthew Dillon Cc: rcarter@pinyon.org, daeron@shadowmere.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: Still system hangs, but different Message-ID: <20000113142201.C1408@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000111131010.A317@relativity.student.utwente.nl> <20000111172846.A361@relativity.student.utwente.nl> <200001111821.KAA39855@apollo.backplane.com> <20000111224639.B720@relativity.student.utwente.nl> <200001120354.TAA66873@apollo.backplane.com> <20000112160744.A693@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000112160744.A693@relativity.student.utwente.nl>; from djb@relativity.student.utwente.nl on Wed, Jan 12, 2000 at 04:07:44PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Dave J. Boers had the guts to say: > I'll leave the system running for a few more hours and then I will enable > softupdates again to try if I can reproduce the problems and take a look > with DDB. The system has been running with softupdates enabled and DDB in the kernel for 18 hours now without a single problem. I'm sorry to say that no matter how hard I try, I can't seem to reproduce the hang (make -j 30 buildworlds while doing du -ks / on 16 Gb of files work flawlessly). Pascal Hofstee informed me that he is also unable to reproduce the hang since he put DDB in his kernel (he had one occurence of the hang the day before yesterday). Since version 1.49 of ffs_softdep.c has been committed, I will move on to that and leave DDB in my kernel just in case. I guess this ends the thread. Regards, Dave Boers. -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 5:58:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 059D414FDA; Thu, 13 Jan 2000 05:58:50 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca44-58.ix.netcom.com [209.111.212.186]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id FAA59018; Thu, 13 Jan 2000 05:58:25 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id FAA20412; Thu, 13 Jan 2000 05:58:17 -0800 (PST) To: Peter Wemm Cc: Jason Evans , Wilko Bulte , Mark Murray , obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Make world breakage... References: <20000113120928.D03951CA0@overcee.netplex.com.au> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 13 Jan 2000 05:58:14 -0800 In-Reply-To: Peter Wemm's message of "Thu, 13 Jan 2000 20:09:28 +0800" Message-ID: Lines: 23 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Peter Wemm * > ======= * > : * > ln -sf libutil.so.2 /usr/obj/usr/src/i386/usr/lib/libutil.so * > cd /usr/src/lib; make depend; make all; make install * > ===> csu/i386-elf * > ===> libcom_err * > ===> libcom_err/doc * > ===> msun * > ===> libmd * > ===> libcrypt * > ===> ../secure/lib/libcrypt * > make: don't know how to make crypt-shs.c. Stop * * This is because of stale .depend files. I got into the habbit of doing a * rm -rf /usr/obj/* after Marcel's changes as earlier on it seemed to be * leaving stale ones behind. I don't know if this is still the case but it * looks a bit like it. I blew away /usr/obj but still get the same error. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 6:20:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as3-053.rp-plus.de [149.221.238.245]) by hub.freebsd.org (Postfix) with ESMTP id 5376B155F9 for ; Thu, 13 Jan 2000 06:20:37 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 9D6D1AB92 for ; Thu, 13 Jan 2000 14:40:02 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id OAA04374 for current@FreeBSD.ORG; Thu, 13 Jan 2000 14:39:35 +0100 (CET) (envelope-from alex) Date: Thu, 13 Jan 2000 14:39:35 +0100 From: Alexander Langer To: current@FreeBSD.ORG Subject: Re: building GNATS with recent current Message-ID: <20000113143935.A3519@cichlids.cichlids.com> Mail-Followup-To: current@FreeBSD.ORG References: <20000112175542.A414@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000112175542.A414@cichlids.cichlids.com>; from alex@big.endian.de on Wed, Jan 12, 2000 at 05:55:42PM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stuff seems to compile now without problems (updated kernel) Strange. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 6:36:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 99D6A14FE1 for ; Thu, 13 Jan 2000 06:36:26 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 3B4E51CD4 for ; Thu, 13 Jan 2000 22:36:20 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: softupdates still broken! Date: Thu, 13 Jan 2000 22:36:20 +0800 From: Peter Wemm Message-Id: <20000113143620.3B4E51CD4@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warning: softupdates is still falling over quite easily: (I run with INVARIANTS) initial pcb at 31f9e0 panicstr: softdep_lock: lock held by 412 panic messages: --- panic: softdep_disk_write_complete: lock is held syncing disks... panic: softdep_lock: lock held by 412 Uptime: 3m17s dumping to dev #da/0x20001, offset 128 dump 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 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 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 137 136 135 134 133 132 131 130 129 128 127 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 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 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 304 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 #1 0xc015bb0d in panic (fmt=0xc02c1da5 "softdep_lock: lock held by %d") at ../../kern/kern_shutdown.c:554 #2 0xc0220cbd in acquire_lock (lk=0xc02f1a9c) at ../../ufs/ffs/ffs_softdep.c:278 #3 0xc0224e12 in softdep_fsync_mountdev (vp=0xec062f20) at ../../ufs/ffs/ffs_softdep.c:3752 #4 0xc02290aa in ffs_fsync (ap=0xed484bc0) at ../../ufs/ffs/ffs_vnops.c:134 #5 0xc0227c9a in ffs_sync (mp=0xc1030400, waitfor=2, cred=0xc0a6c880, p=0xc0338e20) at vnode_if.h:537 #6 0xc0187fab in sync (p=0xc0338e20, uap=0x0) at ../../kern/vfs_syscalls.c:549 #7 0xc015b543 in boot (howto=256) at ../../kern/kern_shutdown.c:226 #8 0xc015bb0d in panic (fmt=0xc02c2c40 "softdep_disk_write_complete: lock is held") at ../../kern/kern_shutdown.c:554 #9 0xc0223f24 in softdep_disk_write_complete (bp=0xc636c3e8) at ../../ufs/ffs/ffs_softdep.c:2993 #10 0xc017dbf2 in vfs_backgroundwritedone (bp=0xc636c3e8) at ../../kern/vfs_bio.c:706 #11 0xc0180117 in biodone (bp=0xc636c3e8) at ../../kern/vfs_bio.c:2708 #12 0xc012c0ad in dadone (periph=0xc1028580, done_ccb=0xc10ee400) at ../../cam/scsi/scsi_da.c:1219 #13 0xc01280a7 in camisr (queue=0xc031c094) at ../../cam/cam_xpt.c:6228 #14 0xc0127ec1 in swi_cambio () at ../../cam/cam_xpt.c:6135 #15 0xc027dcc0 in splz_swi () #16 0xc015161a in statclock (frame=0xed484fa0) at ../../kern/kern_clock.c:456 #17 0xc028ab29 in rtcintr (frame={cf_vec = 0, cf_ppl = 0, cf_fs = 135135279, cf_es = 47, cf_ds = -1078001617, cf_edi = -1509044687, cf_esi = 912511959, cf_ebp = -1346824882, -314028076, cf_ebx = -293984672, cf_edx = 1373333791, cf_ecx = 95720741, cf_eax = -2138529413, 0, 0, cf_eip = 134738532, cf_cs = 31, cf_eflags = 646, cf_esp = -1077938764, cf_ss = 47}) at ../../i386/isa/clock.c:385 #18 0x807f264 in ?? () $FreeBSD: src/sys/contrib/softupdates/softdep.h,v 1.7 1999/08/28 02:16:29 peter Exp $ $FreeBSD: src/sys/contrib/softupdates/ffs_softdep.c,v 1.49 2000/01/13 07:20:01 mckusick Exp $ $FreeBSD: src/sys/ufs/ffs/README.softupdates,v 1.7 1999/12/03 00:40:31 billf Exp $ $FreeBSD: src/sys/ufs/ffs/ffs_alloc.c,v 1.64 2000/01/10 00:24:22 mckusick Exp $ $FreeBSD: src/sys/ufs/ffs/ffs_balloc.c,v 1.25 2000/01/11 08:27:00 mckusick Exp $ $FreeBSD: src/sys/ufs/ffs/ffs_extern.h,v 1.30 2000/01/09 22:40:02 mckusick Exp $ $FreeBSD: src/sys/ufs/ffs/ffs_inode.c,v 1.56 1999/08/28 00:52:21 peter Exp $ $FreeBSD: src/sys/ufs/ffs/ffs_softdep_stub.c,v 1.7 2000/01/10 00:24:22 mckusick Exp $ $FreeBSD: src/sys/ufs/ffs/ffs_subr.c,v 1.25 1999/12/29 04:55:04 peter Exp $ $FreeBSD: src/sys/ufs/ffs/ffs_tables.c,v 1.7 1999/08/28 00:52:22 peter Exp $ $FreeBSD: src/sys/ufs/ffs/ffs_vfsops.c,v 1.117 2000/01/10 12:04:25 phk Exp $ $FreeBSD: src/sys/ufs/ffs/ffs_vnops.c,v 1.64 2000/01/10 12:04:25 phk Exp $ $FreeBSD: src/sys/ufs/ffs/fs.h,v 1.14 1999/08/28 00:52:23 peter Exp $ Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 7: 0: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id D6719152C7 for ; Thu, 13 Jan 2000 06:59:53 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id JAA56454; Thu, 13 Jan 2000 09:59:47 -0500 (EST) Date: Thu, 13 Jan 2000 09:59:47 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Brad Guillory Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel panics when initializing aic7895 controller at startup. In-Reply-To: <20000112231746.A86402@baileylink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, Brad Guillory wrote: > > > I have a similar problem, in kernels build Monday and yesterday. I get > a kernel panic when while booting, I don't know how to capture the boot > messages to a file (do you) so I can not post them but this is the line > that it dies on: > See dmesg(8) or if that won't work for you (ie. you says it panics while booting) you'll need to investigate using a serial console. Good luck, Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 7: 5:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id C466C14FC2 for ; Thu, 13 Jan 2000 07:05:38 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id PAA41581 for current@FreeBSD.org; Thu, 13 Jan 2000 15:37:54 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 13 Jan 2000 15:18:39 +0100 From: Marcel Moolenaar Message-ID: <387DDEBF.8D6E855B@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: , <20000113120928.D03951CA0@overcee.netplex.com.au> Subject: Re: Make world breakage... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > Satoshi - Ports Wraith - Asami wrote: > > * From: Jason Evans > > > > * > In function `_gettemp': > > * > mktemp.c(.text+0x3f0): undefined reference to `_libc_open' > > * > mktemp.c(.text+0x3f4): undefined reference to `_libc_open' > > > > * libc successfully builds on Alpha with the changes I committed, though the > > * bootstrapping problem issue is the same. As noted in another email I just > > * sent, do: > > * > > * cd /usr/src/lib/libc > > * make > > * make install > > * > > * before doing a buildworld. This probably isn't the correct way of > > * resolving such bootstrapping issues, but it works. > > > > Thanks, it's getting a little further with that workaround but now I > > get: > > > > ======= > > : > > ln -sf libutil.so.2 /usr/obj/usr/src/i386/usr/lib/libutil.so > > cd /usr/src/lib; make depend; make all; make install > > ===> csu/i386-elf > > ===> libcom_err > > ===> libcom_err/doc > > ===> msun > > ===> libmd > > ===> libcrypt > > ===> ../secure/lib/libcrypt > > make: don't know how to make crypt-shs.c. Stop > > This is because of stale .depend files. I got into the habbit of doing a > rm -rf /usr/obj/* after Marcel's changes as earlier on it seemed to be > leaving stale ones behind. I don't know if this is still the case but it > looks a bit like it. There should be a dependency from ${.OBJDIR} to Makefile so that when Makefile is updated, ${.OBJDIR} is removed. Removing sources from makefiles is a good example of when stale data is left behind and I can remember that this is exactly what happened for libcrypt... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 7: 7:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 8C2881566B for ; Thu, 13 Jan 2000 07:07:45 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 002261CD4; Thu, 13 Jan 2000 23:07:39 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: mckusick@mckusick.org Cc: current@freebsd.org Subject: Re: softupdates still broken! In-Reply-To: Message from Peter Wemm of "Thu, 13 Jan 2000 22:36:20 +0800." <20000113143620.3B4E51CD4@overcee.netplex.com.au> Date: Thu, 13 Jan 2000 23:07:39 +0800 From: Peter Wemm Message-Id: <20000113150740.002261CD4@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: I should have added more info: [..] > #8 0xc015bb0d in panic (fmt=0xc02c2c40 "softdep_disk_write_complete: lock is held") > at ../../kern/kern_shutdown.c:554 > #9 0xc0223f24 in softdep_disk_write_complete (bp=0xc636c3e8) at ../../ufs/ff s/ffs_softdep.c:2993 > #10 0xc017dbf2 in vfs_backgroundwritedone (bp=0xc636c3e8) at ../../kern/vfs_b io.c:706 > #11 0xc0180117 in biodone (bp=0xc636c3e8) at ../../kern/vfs_bio.c:2708 > #12 0xc012c0ad in dadone (periph=0xc1028580, done_ccb=0xc10ee400) at ../../ca m/scsi/scsi_da.c:1219 [..] (kgdb) list 2988 struct inodedep *inodedep; 2989 struct bmsafemap *bmsafemap; 2990 2991 #ifdef DEBUG 2992 if (lk.lkt_held != -1) 2993 panic("softdep_disk_write_complete: lock is held"); 2994 lk.lkt_held = -2; 2995 #endif 2996 LIST_INIT(&reattach); 2997 while ((wk = LIST_FIRST(&bp->b_dep)) != NULL) { (kgdb) print lk $1 = {lkt_spl = 0, lkt_held = 412} (kgdb) proc 412 (kgdb) where #0 mi_switch () at ../../kern/kern_synch.c:828 #1 0xc015e8c5 in tsleep (ident=0xc635d5be, priority=16, wmesg=0xc02c34a0 "getbuf", timo=0) at ../../kern/kern_synch.c:437 #2 0xc0225f4b in getdirtybuf (bpp=0xed502e80, waitfor=1) at ../../ufs/ffs/ffs_softdep.c:4566 #3 0xc02255e1 in flush_inodedep_deps (fs=0xc1066000, ino=405404) at ../../ufs/ffs/ffs_softdep.c:4104 #4 0xc0224f73 in softdep_sync_metadata (ap=0xed502f28) at ../../ufs/ffs/ffs_softdep.c:3823 #5 0xc022933c in ffs_fsync (ap=0xed502f28) at ../../ufs/ffs/ffs_vnops.c:249 #6 0xc018a971 in fsync (p=0xed49e480, uap=0xed502f80) at vnode_if.h:537 #7 0xc02884be in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 152052608, tf_esi = 0, tf_ebp = -1077942672, tf_isp = -313511980, tf_ebx = 23, tf_edx = 23, tf_ecx = 3, tf_eax = 118, tf_trapno = 12, tf_err = 2, tf_eip = 684704813, tf_cs = 31, tf_eflags = 514, tf_esp = -1077942692, tf_ss = 47}) at ../../i386/i386/trap.c:1055 #8 0xc027c806 in Xint0x80_syscall () It would seem that getdirtybuf() is sleeping while holding the global softupdates 'lk' lock. This is in the new code Kirk added in rev 1.49. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 7:28:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 6820815587 for ; Thu, 13 Jan 2000 07:28:37 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 30EA01CA0 for ; Thu, 13 Jan 2000 23:28:35 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Re: softupdates still broken! In-reply-to: Your message of "Thu, 13 Jan 2000 23:07:39 +0800." <20000113150740.002261CD4@overcee.netplex.com.au> Date: Thu, 13 Jan 2000 23:28:35 +0800 From: Peter Wemm Message-Id: <20000113152835.30EA01CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: [..] > (kgdb) print lk > $1 = {lkt_spl = 0, lkt_held = 412} > (kgdb) proc 412 > > (kgdb) where > #0 mi_switch () at ../../kern/kern_synch.c:828 > #1 0xc015e8c5 in tsleep (ident=0xc635d5be, priority=16, wmesg=0xc02c34a0 "ge tbuf", timo=0) > at ../../kern/kern_synch.c:437 > #2 0xc0225f4b in getdirtybuf (bpp=0xed502e80, waitfor=1) at ../../ufs/ffs/ff s_softdep.c:4566 > #3 0xc02255e1 in flush_inodedep_deps (fs=0xc1066000, ino=405404) at ../../uf s/ffs/ffs_softdep.c:4104 > #4 0xc0224f73 in softdep_sync_metadata (ap=0xed502f28) at ../../ufs/ffs/ffs_ softdep.c:3823 > #5 0xc022933c in ffs_fsync (ap=0xed502f28) at ../../ufs/ffs/ffs_vnops.c:249 > #6 0xc018a971 in fsync (p=0xed49e480, uap=0xed502f80) at vnode_if.h:537 > #7 0xc02884be in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 152052608, tf_esi = 0, > tf_ebp = -1077942672, tf_isp = -313511980, tf_ebx = 23, tf_edx = 23, tf _ecx = 3, tf_eax = 118, > tf_trapno = 12, tf_err = 2, tf_eip = 684704813, tf_cs = 31, tf_eflags = 514, tf_esp = -1077942692, > tf_ss = 47}) at ../../i386/i386/trap.c:1055 > #8 0xc027c806 in Xint0x80_syscall () > > It would seem that getdirtybuf() is sleeping while holding the global > softupdates 'lk' lock. Your mileage may vary, but the following seems to work for me, for this part at least. Index: sys/contrib/softupdates/ffs_softdep.c =================================================================== RCS file: /home/ncvs/src/sys/contrib/softupdates/ffs_softdep.c,v retrieving revision 1.49 diff -u -r1.49 ffs_softdep.c --- sys/contrib/softupdates/ffs_softdep.c 2000/01/13 07:20:01 1.49 +++ sys/contrib/softupdates/ffs_softdep.c 2000/01/13 15:27:25 @@ -4563,7 +4563,9 @@ if (waitfor != MNT_WAIT) return (0); bp->b_xflags |= BX_BKGRDWAIT; + FREE_LOCK_INTERLOCKED(&lk); tsleep(&bp->b_xflags, PRIBIO, "getbuf", 0); + ACQUIRE_LOCK_INTERLOCKED(&lk); if (bp->b_xflags & BX_BKGRDINPROG) panic("getdirtybuf: still writing"); continue; Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 7:43:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id D1F1514BF2 for ; Thu, 13 Jan 2000 07:43:49 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id AAA26665; Fri, 14 Jan 2000 00:43:45 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp539.kt.rim.or.jp [202.247.140.189]) by mail1.rim.or.jp (3.7W/) id AAA04060; Fri, 14 Jan 2000 00:43:47 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id AAA27972; Fri, 14 Jan 2000 00:43:46 +0900 (JST) Date: Fri, 14 Jan 2000 00:43:44 +0900 Message-ID: <14461.62128.675464.13362J@localhost.sky.rim.or.jp> From: Jun Kuriyama To: wpaul@skynet.ctr.columbia.edu Cc: current@freebsd.org Subject: Re: panic in uipc_mbuf.c or if_aue.c In-Reply-To: In your message of "Wed, 12 Jan 2000 10:40:59 -0500 (EST)" <200001121541.KAA23708@skynet.ctr.columbia.edu> References: <14460.40191.708206.82051O@localhost.sky.rim.or.jp> <200001121541.KAA23708@skynet.ctr.columbia.edu> User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Bill Paul > We need version information! How recent is your version of -current! > What's the rcsid from if_aue.c! Details please! * $FreeBSD: src/sys/dev/usb/if_aue.c,v 1.5 2000/01/10 23:12:50 wpaul Exp $ > Print out the contents of the mbuf!! Show is what it thinks the real > length is! I replaced binary data to "...data..." which may confuse mail agent. I don't know this is enough or not. Please let me know if you want more information. I'll update if_aue.c to v1.6 and try without IPFW. (kgdb) up 11 #11 0xc021b7af in aue_encap (sc=0xc0828600, m=0xc05d4e00, idx=0) at ../../dev/usb/if_aue.c:1107 l1107 m_copydata(m, 0, m->m_pkthdr.len, c->aue_buf + 2); (kgdb) list 1102 1103 /* 1104 * Copy the mbuf data into a contiguous buffer, leaving two 1105 * bytes at the beginning to hold the frame length. 1106 */ 1107 m_copydata(m, 0, m->m_pkthdr.len, c->aue_buf + 2); 1108 c->aue_mbuf = m; 1109 1110 /* 1111 * XXX I don't understand why, but transfers that (kgdb) print *m $1 = {m_hdr = {mh_next = 0xc05ac100, mh_nextpkt = 0x0, mh_data = 0xc05d4e22 "", mh_len = 54, mh_type = 2, mh_flags = 2}, M_dat = { MH = {MH_pkthdr = {rcvif = 0x0, len = 1514, header = 0x280602bc "\""}, MH_dat = {MH_ext = { ext_buf = 0x30005000
, ext_free = 0x311a0043, ext_size = 1629896704, ext_ref = 0x8c710}, MH_databuf = "...data...", '\000' }}, M_databuf = "...data...", '\000' }} (kgdb) print *m->m_hdr.mh_next $2 = {m_hdr = {mh_next = 0x0, mh_nextpkt = 0x0, mh_data = 0xc05cd800 "...data..."..., mh_len = 284, mh_type = 1, mh_flags = 1}, M_dat = {MH = {MH_pkthdr = { rcvif = 0xc0828600, len = 60, header = 0x280602bc "\""}, MH_dat = { MH_ext = { ext_buf = 0xc05cd800 "...data..."..., ext_free = 0, ext_size = 2048, ext_ref = 0}, MH_databuf = "...data..."}}, M_databuf = "...data..."}} (kgdb) Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 8:19:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id BC070154AF; Thu, 13 Jan 2000 08:19:20 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA20070; Thu, 13 Jan 2000 17:19:19 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001131619.RAA20070@freebsd.dk> Subject: Re: ATA CDROM problems In-Reply-To: from Kris Kennaway at "Jan 11, 2000 00:54:46 am" To: kris@hub.freebsd.org (Kris Kennaway) Date: Thu, 13 Jan 2000 17:19:19 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kris Kennaway wrote: > > acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04 Sounds like the drive doesn't like this, it probably only supports PLAY_MSF.. > ata1-slave: piomode=3 dmamode=0 udmamode=-1 dmaflag=1 > ata1-slave: timeout waiting for command=ef s=00 e=00 > ata1-slave: failed setting up PIO3 mode on generic chip Now that points to a problem, the drive wont accept being put into PIO mode 3, despite it saying it supports it, hmm... > acd0: CDROM drive at ata1 as slave > acd0: read 171KB/s (689KB/s), 256KB buffer, ??? > acd0: Reads: CD-DA > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked, lock protected I have some mods to the driver that will be commit in a few days, that _might_ solve this problem... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 8:43: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 07983155BF; Thu, 13 Jan 2000 08:43:00 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id e0DGgvw69943; Thu, 13 Jan 2000 18:42:57 +0200 (SAST) Message-Id: <200001131642.e0DGgvw69943@gratis.grondar.za> To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Cc: current@FreeBSD.ORG Subject: Re: Make world breakage... References: In-Reply-To: ; from asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) "13 Jan 2000 05:58:14 PST." Date: Thu, 13 Jan 2000 18:42:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I blew away /usr/obj but still get the same error. ...then your source tree is not up to date. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 8:43:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 012F215672; Thu, 13 Jan 2000 08:43:39 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA20144; Thu, 13 Jan 2000 17:43:36 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001131643.RAA20144@freebsd.dk> Subject: Re: ATAPI broken, but why? In-Reply-To: from Brian Fundakowski Feldman at "Jan 10, 2000 10:34:25 pm" To: green@FreeBSD.ORG (Brian Fundakowski Feldman) Date: Thu, 13 Jan 2000 17:43:36 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Brian Fundakowski Feldman wrote: > I'm sure everyone's seen my e-mail and others' e-mail about ATAPI in the > ATA driver, at least, being broken (WRT CD-Rs). The question is, does > anyone have any idea at all why? I tried reverting to just before the > CDRIOC* changes, and that didn't help (using wormcontrol to test that). > If any of you have any hints at all, please let me know. Uhm, if reverting the driver to the state BEFORE the change doesn't help, you probably should look somewhere else, as you stated once that that used to work. Have you change other things in the system ? Overclocking ? checked the cables ? can you check the drive otherwise ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 9: 9:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from testbed.baileylink.net (testbed.baileylink.net [63.71.213.24]) by hub.freebsd.org (Postfix) with ESMTP id 273CA14ECB for ; Thu, 13 Jan 2000 09:09:06 -0800 (PST) (envelope-from brad@testbed.baileylink.net) Received: (from brad@localhost) by testbed.baileylink.net (8.9.3/8.9.3) id LAA40125 for freebsd-current@freebsd.org; Thu, 13 Jan 2000 11:09:09 -0600 (CST) (envelope-from brad) Date: Thu, 13 Jan 2000 11:09:08 -0600 From: Brad Guillory To: freebsd-current@freebsd.org Subject: Re: kernel panics when initializing aic7895 controller at startup. Message-ID: <20000113110908.G22936@baileylink.net> References: <20000112231746.A86402@baileylink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kbyanc@posi.net on Thu, Jan 13, 2000 at 09:59:47AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanx, I knew about dmesg, I just thought that there might be a boot loader option that would allow me to log the boot to a file (via bios calls). Thanx, BMG On Thu, Jan 13, 2000 at 09:59:47AM -0500, Kelly Yancey wrote: > On Wed, 12 Jan 2000, Brad Guillory wrote: > > > > > > > I have a similar problem, in kernels build Monday and yesterday. I get > > a kernel panic when while booting, I don't know how to capture the boot > > messages to a file (do you) so I can not post them but this is the line > > that it dies on: > > > > See dmesg(8) or if that won't work for you (ie. you says it panics while > booting) you'll need to investigate using a serial console. > > Good luck, > > Kelly > > -- > Kelly Yancey - kbyanc@posi.net - Richmond, VA > Analyst / E-business Development, Bell Industries http://www.bellind.com/ > Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ > Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 9:25:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id C464714EE9 for ; Thu, 13 Jan 2000 09:25:33 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id JAA60268 for ; Thu, 13 Jan 2000 09:22:25 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <387E09D1.616F09C8@MexComUSA.net> Date: Thu, 13 Jan 2000 09:22:25 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: No password needed. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was able to make world and new kernels early this morning for the first time since Sunday. I immediately rebooted my laptop, from behind the firewall, and got a softupdates panic while coming up. So, I rebooted with Sunday's kernel, also with softupdates, and it came up fine. The strange part is that a password is no longer needed to login in. I've never seen this before, except some time ago when a space before root would cause something similar, if I remember correctly. It is looking at the password file because it won't accept a user who isn't listed. Any ideas, what could have happened? Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 9:31:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 18C4F15117; Thu, 13 Jan 2000 09:31:28 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA08606; Thu, 13 Jan 2000 09:29:59 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA75664; Thu, 13 Jan 2000 09:29:59 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 13 Jan 2000 09:29:59 -0800 (PST) Message-Id: <200001131729.JAA75664@vashon.polstra.com> To: obrien@freebsd.org Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. In-Reply-To: <20000112211625.A21988@dragon.nuxi.com> References: <20000112172213.Z302@sturm.canonware.com> <200001130300.TAA74514@vashon.polstra.com> <20000112211625.A21988@dragon.nuxi.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000112211625.A21988@dragon.nuxi.com>, David O'Brien wrote: > On Wed, Jan 12, 2000 at 07:00:01PM -0800, John Polstra wrote: > > > I _really_ don't like it when a program reaches waaaaaaay over into an > > unrelated directory for its sources. > > We already do that all over the place. :-) We do it in a few places, but not many. That doesn't make it a good practice, anyway. Those few places where it is done have been responsible for more than their share of unpleasant surprises in the form of make world breakage. > > I'd rather have a few duplicated sources. > > I dissagree. Then we have the problem of fixing a PR/bug in one source > but not the other. Such duplicated routines should be few in number and simple in function. Compilers don't need much support from the underlying OS. All they do is read files, perform various transformations on them, and write out the results. You don't need anything beyond what ANSI/ISO C provides to accomplish that. It is not ideal to have some duplicated code, but the alternative is worse. > The use/making of temperary files is already a security issue. I > can just see it happen that someone fixes a problem with one copy of > the source and then we find we still have some vulerabiltity because > the second copy wasn't known/found/fixed. Come on, this is the compiler we're talking about. I seriously doubt there are any real-life security issues there. If there are, then you duplicate mkstemp. Surely it isn't such a complicated function that that can't be done reliably. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 10: 3:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 695BC14FFC for ; Thu, 13 Jan 2000 10:03:41 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id JAA47082 for current@FreeBSD.ORG; Thu, 13 Jan 2000 09:58:55 -0800 (PST) Date: Thu, 13 Jan 2000 09:58:55 -0800 (PST) From: David Wolfskill Message-Id: <200001131758.JAA47082@pau-amma.whistle.com> Subject: Re: move portmap(8) from /usr/sbin to /sbin Cc: current@FreeBSD.ORG In-Reply-To: <200001130554.QAA11037@shad.internal.en-bio> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Thu, 13 Jan 2000 16:54:21 +1100 (EST) >From: Tony Maher >> Sick, poor in performance and the wrong tool for the job. >> See mount_null(8) for more details on how to do it right. >Yes its perfect for the job apart from: >man mount_null > THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK) >.... Another way to accomplish a similar result -- especially if you're already using amd -- is to make use of the ability (within an amd map) to specify a "type" of "link" (vs. "nfs"). This (type=link) simulates a symlink, as opposed to simulating an NFS mount. I've been using it for >1.5 years here to avoid loopback NFS mounts. Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 10:19:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [212.84.196.35]) by hub.freebsd.org (Postfix) with ESMTP id 39B2314D53 for ; Thu, 13 Jan 2000 10:19:13 -0800 (PST) (envelope-from news-list.freebsd.current@innominate.de) Received: from mate.bln.innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (8.9.3/8.9.3) with ESMTP id TAA21154 for ; Thu, 13 Jan 2000 19:07:59 +0100 Received: by mate.bln.innominate.de (Postfix, from userid 9) id 78D922CA6C; Thu, 13 Jan 2000 18:49:54 +0100 (CET) From: news-list.freebsd.current@innominate.de (Thomas Graichen) Reply-To: Thomas Graichen X-Newsgroups: innominate.bln.list.freebsd.current Subject: Re: wdm not responding Date: 13 Jan 2000 17:49:53 GMT Organization: innominate AG, Berlin, Germany Lines: 50 Message-ID: References: <387B10D5.37E13989_nokia.com@ns.sol.net> <20000111034224.M9397_fw.wintelcom.net@ns.sol.net> <387B2D27.F23FCF49@nokia.com> Reply-To: graichen@innominate.de X-Trace: mate.bln.innominate.de 947785793 7389 10.0.0.213 (13 Jan 2000 17:49:53 GMT) X-Complaints-To: news@innominate.de User-Agent: tin/pre-1.4-19990805 ("Preacher Man") (UNIX) (FreeBSD/3.3-RELEASE (i386)) To: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the thing i found out with kdm was that it uses the wrong vty i think - adding at vt09 to the Xservers file X line solved it (i use x on console 9) t Marc Solsona wrote: > Both solutions seem to work with xdm, but not with wdm. It's not a big trauma > but may be I should contact the wdm mantainer. > Marc > Alfred Perlstein wrote: > * Edwin Mons [000111 03:37] wrote: >> > >> > Marc Solsona wrote: >> > > >> > > I'm using wdm o the 3-stable branch. Since I migrated to current wdm is >> > > >> > > not reponding to keyboard. Although when I start it manually it does. >> > > Any ideas? >> > > >> > > Thanks >> > > >> > > To Unsubscribe: send mail to majordomo@FreeBSD.org >> > > with "unsubscribe freebsd-current" in the body of the message >> > >> > I noticed this, too, with xdm. Putting a 'sleep 4' before starting xdm >> > (and thus starting it after getty ran and the system was ready to use) >> > fixed it for me.. Don't know the real cause, though. >> >> You ought to use the example in /etc/ttys to start it up. >> >> -Alfred >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 10:43:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id 3FE6015714 for ; Thu, 13 Jan 2000 10:41:35 -0800 (PST) (envelope-from tom@embt.com) Received: from PARANOR (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id MAA18477; Thu, 13 Jan 2000 12:49:10 -0600 (CST) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.20000113134109.01660298@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 13 Jan 2000 13:41:09 -0500 To: Mark Newton From: Tom Embt Subject: Re: why is my current so .... stable? Cc: current@FreeBSD.ORG In-Reply-To: <20000113105214.D1094@internode.com.au> References: <3.0.3.32.20000112082944.01636938@mail.embt.com> <3.0.3.32.20000112082944.01636938@mail.embt.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:52 01/13/2000 +1030, Mark Newton wrote: >On Wed, Jan 12, 2000 at 08:29:44AM -0500, Tom Embt wrote: > > > >This would be great, but I wonder from what source we could take reliable > > >data about -current's stability. > > > > How 'bout some sort of client program that is run via the rc.d and > > rc.shutdown scripts? > >One of the more annoying aspects of IRIX in its default config is >that whenever you do a halt or reboot it'd pop up a menu to ask why. >That information, together with crash dump info and other data about >system failures, can be funnelled into a mail filter which records >historical reliability data; That data can (optionally) be sent back >to SGI too. > >We could provide something like this, but (a) if it's on by default >it'll suck rocks, and (b) if it's off by default nobody will bother >turning it on. Hey ho! > > - mark > Hmm, well the menu thing would surely suck, but we wouldn't really need that info anyway. Perhaps if the startup/shutdown info was just written to /var/log/ and people could optionally enable (as in off by default) something in /etc/rc.conf to actually send the info back to a master server on a regular basis. Even if the info isn't sent to the master it could be parsed locally if so desired. Again, just ideas.. Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 10:52:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id C019D1529B for ; Thu, 13 Jan 2000 10:52:47 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id NAA02434 for ; Thu, 13 Jan 2000 13:52:50 -0500 (EST) Date: Thu, 13 Jan 2000 13:52:50 -0500 (EST) From: "Mr. K." To: current@freebsd.org Subject: lint not working on -current? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First of all, forgive me for being stupid, if that's what it turns out it was, but I can't seem to get lint to work on -current (though it works fine on -stable). > lint -V pvselect.c pvselect.c: /usr/libexec/cpp -lang-c -undef -$ -C -Wcomment -D__FreeBSD__=4 -Dlint -D__lint -D__lint__ -D__unix -D__unix__ -D__i386 -D__i386__ -Wtraditional -Di386 pvselect.c /tmp/lint0.UT6044 cpp: Invalid option `-undef' > uname -a FreeBSD [censored].com 4.0-20000110-CURRENT FreeBSD 4.0-20000110-CURRENT #0: Mon Jan 10 14:09:46 GMT 2000 root@usw2.freebsd.org:/usr/src/sys/compile/GENERIC i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 10:57:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 32E9715698 for ; Thu, 13 Jan 2000 10:57:37 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id TAA08703 for freebsd-current@FreeBSD.ORG; Thu, 13 Jan 2000 19:08:06 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 9DFBC8863; Thu, 13 Jan 2000 08:22:19 +0100 (CET) Date: Thu, 13 Jan 2000 08:22:19 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help Message-ID: <20000113082219.A63784@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <20000112232656W.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000112232656W.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Wed, Jan 12, 2000 at 11:26:56PM +0900 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Yoshinobu Inoue: > I recommend you to try libpcap-3.5 and tcpdump-3.5 obtained > from www.tcpdump.org. It would be nice to upgrade our tcpdump/libpcap to have these... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 11:29:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 15FC614DBD for ; Thu, 13 Jan 2000 11:29:38 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id EDD1E1E3A; Thu, 13 Jan 2000 20:29:35 +0100 (CET) Date: Thu, 13 Jan 2000 20:29:35 +0100 From: "Dave J. Boers" To: Peter Wemm Cc: current@freebsd.org Subject: Re: softupdates still broken! Message-ID: <20000113202935.A376@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000113143620.3B4E51CD4@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000113143620.3B4E51CD4@overcee.netplex.com.au>; from peter@netplex.com.au on Thu, Jan 13, 2000 at 10:36:20PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Peter Wemm had the courage to say: > Warning: softupdates is still falling over quite easily: > (I run with INVARIANTS) > > initial pcb at 31f9e0 > panicstr: softdep_lock: lock held by 412 > panic messages: > --- > panic: softdep_disk_write_complete: lock is held > > syncing disks... panic: softdep_lock: lock held by 412 > Uptime: 3m17s I second that. Same panic, system can't even stay alive for more than 3 minutes after booting. Same version of ffs_softdep.c: 1.49. Regards, Dave Boers. Backtrace is below. Can someone please confirm that I did this the right/wrong way? This _is_ a first time experience for me ;-) This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.1 (kgdb) core-file /var/crash/vmcore.1 SMP 2 cpus IdlePTD 3125248 initial pcb at 27ea80 panicstr: from debugger panic messages: --- panic: softdep_disk_write_complete: lock is held mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 panic: from debugger mp_lock = 01000002; cpuid = 1; lapic.id = 01000000 boot() called on cpu#1 Uptime: 2m1s dumping to dev #ad/0x20001, offset 786432 dump ata2: resetting devices .. done 128 127 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 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 boot (howto=260) at ../../kern/kern_shutdown.c:304 304 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 #1 0xc0150a01 in panic (fmt=0xc0225df4 "from debugger") at ../../kern/kern_shutdown.c:554 #2 0xc012e219 in db_panic (addr=-1071679891, have_addr=0, count=-1, modif=0xff80dd8c "") at ../../ddb/db_command.c:433 #3 0xc012e1b9 in db_command (last_cmdp=0xc025261c, cmd_table=0xc025247c, aux_cmd_tablep=0xc027abc8) at ../../ddb/db_command.c:333 #4 0xc012e27e in db_command_loop () at ../../ddb/db_command.c:455 #5 0xc0130307 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xc01f73b4 in kdb_trap (type=3, code=0, regs=0xff80de94) at ../../i386/i386/db_interface.c:158 #7 0xc0209c98 in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = -1019691216, tf_esi = 256, tf_ebp = -8331556, tf_isp = -8331584, tf_ebx = -1071415552, tf_edx = -1071028128, tf_ecx = 16777217, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1071679891, tf_cs = 8, tf_eflags = 582, tf_esp = -1071362429, tf_ss = -1071469038}) at ../../i386/i386/trap.c:531 #8 0xc01f766d in Debugger (msg=0xc022ae12 "panic") at machine/cpufunc.h:64 #9 0xc01509f8 in panic (fmt=0xc0237f00 "softdep_disk_write_complete: lock is held") at ../../kern/kern_shutdown.c:552 #10 0xc01b01d8 in softdep_disk_write_complete (bp=0xc338bf30) at ../../ufs/ffs/ffs_softdep.c:2993 #11 0xc0172776 in vfs_backgroundwritedone (bp=0xc338bf30) at ../../kern/vfs_bio.c:710 #12 0xc0174ba3 in biodone (bp=0xc338bf30) at ../../kern/vfs_bio.c:2712 #13 0xc01d8582 in ad_interrupt (request=0xc0b83900) at ../../dev/ata/ata-disk.c:624 #14 0xc01d590e in ataintr (data=0xc09ca100) at ../../dev/ata/ata-all.c:624 #15 0xc02127fd in intr_mux (arg=0xc07329c0) at ../../i386/isa/intr_machdep.c:569 -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 11:32:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 093EF14A06 for ; Thu, 13 Jan 2000 11:32:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA82477; Thu, 13 Jan 2000 11:32:27 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Jan 2000 11:32:27 -0800 (PST) From: Matthew Dillon Message-Id: <200001131932.LAA82477@apollo.backplane.com> To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Update to ffs_softdep.c 1.50 or better (was Re: softupdates still broken!) References: <20000113152835.30EA01CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Your mileage may vary, but the following seems to work for me, for this :part at least. : :Index: sys/contrib/softupdates/ffs_softdep.c :=================================================================== :RCS file: /home/ncvs/src/sys/contrib/softupdates/ffs_softdep.c,v :retrieving revision 1.49 :diff -u -r1.49 ffs_softdep.c :--- sys/contrib/softupdates/ffs_softdep.c 2000/01/13 07:20:01 1.49 :+++ sys/contrib/softupdates/ffs_softdep.c 2000/01/13 15:27:25 :@@ -4563,7 +4563,9 @@ : if (waitfor != MNT_WAIT) : return (0); : bp->b_xflags |= BX_BKGRDWAIT; :+ FREE_LOCK_INTERLOCKED(&lk); : tsleep(&bp->b_xflags, PRIBIO, "getbuf", 0); :+ ACQUIRE_LOCK_INTERLOCKED(&lk); : if (bp->b_xflags & BX_BKGRDINPROG) : panic("getdirtybuf: still writing"); : continue; : : :Cheers, :-Peter :-- :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au Kirk has committed this plus the fix to the 'flush 3' panic plus the fix to the 'update failed' panic. Everyone using softupdates should upgrade to sys/contrib/softupdates/ffs_softdep.c 1.50 or better. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 11:37: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id B46F214F10 for ; Thu, 13 Jan 2000 11:36:53 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id C380F1CA0; Fri, 14 Jan 2000 03:36:51 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: djb@relativity.student.utwente.nl Cc: current@freebsd.org Subject: Re: softupdates still broken! In-Reply-To: Message from "Dave J. Boers" of "Thu, 13 Jan 2000 20:29:35 +0100." <20000113202935.A376@relativity.student.utwente.nl> Date: Fri, 14 Jan 2000 03:36:51 +0800 From: Peter Wemm Message-Id: <20000113193651.C380F1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Dave J. Boers" wrote: > It is rumoured that Peter Wemm had the courage to say: > > Warning: softupdates is still falling over quite easily: > > (I run with INVARIANTS) > > > > initial pcb at 31f9e0 > > panicstr: softdep_lock: lock held by 412 > > panic messages: > > --- > > panic: softdep_disk_write_complete: lock is held > > > > syncing disks... panic: softdep_lock: lock held by 412 > > Uptime: 3m17s > > I second that. Same panic, system can't even stay alive for more than 3 > minutes after booting. Same version of ffs_softdep.c: 1.49. I have committed an unreviewed patch that fixes it for a number of folks. You might like to try this if you can't wait for cvsup. (boot single user and turn softupdates off until you recompile). Index: ffs_softdep.c =================================================================== RCS file: /home/ncvs/src/sys/contrib/softupdates/ffs_softdep.c,v retrieving revision 1.49 retrieving revision 1.50 diff -u -r1.49 -r1.50 --- ffs_softdep.c 2000/01/13 07:20:01 1.49 +++ ffs_softdep.c 2000/01/13 18:48:12 1.50 @@ -4563,7 +4563,9 @@ if (waitfor != MNT_WAIT) return (0); bp->b_xflags |= BX_BKGRDWAIT; + FREE_LOCK_INTERLOCKED(&lk); tsleep(&bp->b_xflags, PRIBIO, "getbuf", 0); + ACQUIRE_LOCK_INTERLOCKED(&lk); if (bp->b_xflags & BX_BKGRDINPROG) panic("getdirtybuf: still writing"); continue; Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 11:52: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AF5EC14D7E for ; Thu, 13 Jan 2000 11:52:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA82781; Thu, 13 Jan 2000 11:51:50 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Jan 2000 11:51:50 -0800 (PST) From: Matthew Dillon Message-Id: <200001131951.LAA82781@apollo.backplane.com> To: "Dave J. Boers" Cc: rcarter@pinyon.org, daeron@wit401305.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: Still system hangs, but different References: <20000111131010.A317@relativity.student.utwente.nl> <20000111172846.A361@relativity.student.utwente.nl> <200001111821.KAA39855@apollo.backplane.com> <20000111224639.B720@relativity.student.utwente.nl> <200001120354.TAA66873@apollo.backplane.com> <20000112160744.A693@relativity.student.utwente.nl> <20000113142201.C1408@relativity.student.utwente.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The system has been running with softupdates enabled and DDB in the kernel :for 18 hours now without a single problem. I'm sorry to say that no matter Don't be sorry, be happy! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 11:52:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id B788015568 for ; Thu, 13 Jan 2000 11:52:35 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id EAA18313; Fri, 14 Jan 2000 04:52:21 +0900 (JST) To: Yoshinobu Inoue Cc: tcrimi+@andrew.cmu.edu, freebsd-current@FreeBSD.ORG In-reply-to: shin's message of Wed, 12 Jan 2000 23:26:56 JST. <20000112232656W.shin@nd.net.fujitsu.co.jp> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: IPv6 testing...willing to help From: itojun@iijlab.net Date: Fri, 14 Jan 2000 04:52:21 +0900 Message-ID: <18311.947793141@coconut.itojun.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I suppose something going wrong when multiple mbuf cluster is >used for encrypted TCP connection. >Because as I tried to cat several different sized files, >catting files bigger than around >2048(mbuf cluster size) minus protocol header size >seems to cause the problem. > >Because mbuf cluster could be shared by multiple outstanding >packets, it might be encrypted by multiple times. >I'll investigate this further. I think we have already fixed this in the past, by deep-copying cluster mbufs... ipsec_copypkt() in sys/netinet6/ipsec.c. i'm running telnet chargen all the time between kame/bsdi3 and kame/netbsd and having no problem. note that there are differences among *BSD for checking for shared clusters. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 11:56:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 3060914D7E; Thu, 13 Jan 2000 11:56:43 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA04218; Thu, 13 Jan 2000 20:33:40 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01564; Thu, 13 Jan 2000 20:35:16 +0100 (CET) (envelope-from wilko) Date: Thu, 13 Jan 2000 20:35:16 +0100 From: Wilko Bulte To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: Make world breakage... Message-ID: <20000113203515.A1321@yedi.iaf.nl> References: <200001121956.e0CJuNw65075@gratis.grondar.za> <20000112220725.A2942@yedi.iaf.nl> <20000112132225.T302@sturm.canonware.com> <20000113001631.C4148@yedi.iaf.nl> <20000112172522.A21639@dragon.nuxi.com> <20000113083024.A50096@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000113083024.A50096@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Thu, Jan 13, 2000 at 08:30:24AM +0100 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 08:30:24AM +0100, Wilko Bulte wrote: > On Wed, Jan 12, 2000 at 05:25:22PM -0800, David O'Brien wrote: > > On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote: > > > I copied libc.so.4 manually to /usr/lib but that is not sufficient. > > > It looks like ld-elf sticks to libc.so.4 even if I move the symlink > > > libc.so back from libc.so.4 to libc.so.3 > > > > Yes. Each shared library knows it's name when it was compiled (minor > > hand waving here). The linker then burns the shlib name (not file name, > > but shlib name gotten from a header in the shlib. > > The linker burns the shlib name into the executable it links, right? > Then why don't my executables linked end of december with libc.so.3 > work anymore? > > Essentially everything linked shared is now broken. And I have only > built/installed libc.so.4 (I did not get any further :/) and not any > executables. > > So, why are the 'old' executablas no longer working happily with libc.so.3 > they are linked to? Thanks to Marcel for flipping my misconception: I was under impression that libc.so.4 was a *new* libc.so, in other words that my freshly generated .4 was the first .4 ever. That was wrong, there has been a .4 before so the December executables also had internal references to the .4 version. I resurrected things by grabbing an 'old' .4 library from another Alpha. Now things work again. Wilko -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 12: 0:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4E36214E42 for ; Thu, 13 Jan 2000 12:00:27 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA82890; Thu, 13 Jan 2000 12:00:22 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Jan 2000 12:00:22 -0800 (PST) From: Matthew Dillon Message-Id: <200001132000.MAA82890@apollo.backplane.com> To: "Rodney W. Grimes" Cc: ntakpe@ffab.tide.ti.com (Jean Louis Ntakpe), dwmalone@maths.tcd.ie (David Malone), mb@imp.ch, current@FreeBSD.ORG Subject: Re: move portmap(8) from /usr/sbin to /sbin References: <200001130541.VAA31067@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Sometimes we just want to nfs-mount things on the same :> machine. : :Sick, poor in performance and the wrong tool for the job. :See mount_null(8) for more details on how to do it right. : :> :> One more example: I don't like /var/news so I mount locally :> /var/news :> to /archive/news on the same system instead of using :> symlinks. :> My rc.local manages it for me. : :Sick. See above. I gotta agree, this is sick. But to put the icing on the cake: LOCAL NFS MOUNTS CAN LEAD TO LOW-MEMORY DEADLOCKS. Even with my recent fixes to -current there is still a non-zero chance of this happening. The best way to handle a mutual-export/import situation is to physically mount your disks in this type of directory structure: machine A: 'lander' machine B: 'apollo' /lander/u1 /lander/u2 /lander/u3 /apollo/u1 /apollo/u2 /apollo/u3 On lander the local partitions u1, u2, and u3's mount points are hard mounted on /lander/u{1,2,3} and apollo's local disks are NFS mounted on lander in /apollo/u{1,2,3}. On apollo the /lander partition contains NFS mounts from lander's u{1,2,3} and apollo's local drives are hard mounted directoy onto /apollo/u{1,2,3}. It couldn't be simpler. If you want standard system places to point to some of these partitions, you simply make the standard system places softlinks to the appropriate /host/partition directory. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 12: 1:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 96AF1156CF for ; Thu, 13 Jan 2000 12:01:10 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id FAA07014; Fri, 14 Jan 2000 05:00:56 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id FAA21448; Fri, 14 Jan 2000 05:00:55 +0900 (JST) Received: from localhost ([192.168.245.64]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id FAA20634; Fri, 14 Jan 2000 05:00:54 +0900 (JST) To: itojun@iijlab.net Cc: tcrimi+@andrew.cmu.edu, freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help In-Reply-To: <18311.947793141@coconut.itojun.org> References: <20000112232656W.shin@nd.net.fujitsu.co.jp> <18311.947793141@coconut.itojun.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000114050127E.shin@nd.net.fujitsu.co.jp> Date: Fri, 14 Jan 2000 05:01:27 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 15 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think we have already fixed this in the past, by deep-copying cluster > mbufs... ipsec_copypkt() in sys/netinet6/ipsec.c. > i'm running telnet chargen all the time between kame/bsdi3 and > kame/netbsd and having no problem. > > note that there are differences among *BSD for checking for shared > clusters. Yes, I checked that the problem don't happen on kame/freebsd3.x which is the base of freebsd-current merging. So I suspect I might missed something in merging process. I'll check it, but maybe after 4.0 feature freeze.(15th) Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 12:10:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id CC15A14FC3 for ; Thu, 13 Jan 2000 12:10:26 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id FAA20170 for ; Fri, 14 Jan 2000 05:10:26 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id FAA22379; Fri, 14 Jan 2000 05:10:25 +0900 (JST) Received: from localhost ([192.168.245.90]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id FAA20782; Fri, 14 Jan 2000 05:10:24 +0900 (JST) To: freebsd-current@FreeBSD.ORG Subject: Re: [solicite review and confirmation of tcp for IPv6 patches] In-Reply-To: <20000110042221K.shin@nd.net.fujitsu.co.jp> References: <20000103012633S.shin@nd.net.fujitsu.co.jp> <20000107123727P.shin@nd.net.fujitsu.co.jp> <20000110042221K.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000114051038P.shin@nd.net.fujitsu.co.jp> Date: Fri, 14 Jan 2000 05:10:38 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 21 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I prepared some IPv6 tcp related apps and libs patches. Anyone interested, please try them. (Each of following 2 url has the same patches.) http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/tcp-apps.20000114 http://www.FreeBSD.org/~shin/tcp-apps.20000114 They includes, -inetd -libutil -rlogin -rlogind -rshd -telnetd As far as I checked, those apps seems to be working over both IPv4 and IPv6. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 12:25:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 40B7915170 for ; Thu, 13 Jan 2000 12:25:49 -0800 (PST) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id PAA94904 for freebsd-current@freebsd.org; Thu, 13 Jan 2000 15:27:34 -0500 (EST) From: Brian Hechinger Message-Id: <200001132027.PAA94904@entropy.tmok.com> Subject: make buildworld fails (yet another failure) To: freebsd-current@freebsd.org Date: Thu, 13 Jan 2000 15:27:34 -0500 (EST) Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i've read all the 'make buildworld fails' e=7Fmessages on this list, but no= ne of them have helped me. i tried the 'make b=7F-m /usr/src/share/mk buildwo= rld' and that fixes some problems, but i'm still getting hung up on this one. i'm upgrading from 3.4-stable to 4.0-current (in a vain attempt to get the coldfusion server to run under FreeBSD so we can get rid of Linux, which can do 5 requests a second single CPU but only 4 requests a second with two CPU= s) here is the output from make where it dies, if you need the whole output i can send that, but it must be asked for. i haven't built a new kernel yet since config complains, so i'm assuming i needed to rebuild world before trying to build a new kernel. if i must have a new kernel FIRST let me know and i'll grab a GENERIC-current kernel. thanks, -brian -- Included Text Follows: =3D=3D=3D> libkadm ln -sf /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/include/p= rotos.H protos.h rm -f .depend mkdep -f .depend -a -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/ke= rberosIV/include -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include -I= /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/krb -I/usr/s= rc/kerberosIV/lib/libkadm/../= ../../crypto/kerberosIV/lib/kdb -I/usr/src/kerberosIV/lib/libkadm/../../../= crypto/kerberosIV/lib/kadm -I/usr/src/kerberosIV/lib/libkadm/../../../crypt= o/kerberosIV/lib/roken -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/= libkrb -I/usr/obj/usr/src/ker= berosIV/lib/libkadm/../../lib/libkadm -I/usr/obj/usr/src/kerberosIV/lib/lib= kadm -I/usr/src/kerberosIV/lib/libkadm/../../include -DHAVE_CONFIG_H -I/usr= /obj/usr/src/kerberosIV/lib/libkadm/../../include -DBINDIR=3D\"/usr/bin\" -= DSBINDIR=3D\"/usr/sbin\" -I/usr/o= bj/usr/src/i386/usr/include /usr/src/kerberosIV/lib/libkadm/../../../crypt= o/kerberosIV/lib/kadm/kadm_cli_wrap.c /usr/src/kerberosIV/lib/libkadm/../..= /../crypto/kerberosIV/lib/kadm/kadm_stream.c /usr/src/kerberosIV/lib/libkad= m/../../../crypto/kerberosIV/= lib/kadm/kadm_supp.c /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libk= adm/kadm_err.c /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/l= ib/kadm/check_password.c In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_locl.h:74, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_cli_wrap.c:30: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: inva= lid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_locl.h:77, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_cli_wrap.c:30: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: wa= rning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warn= ing: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: in= valid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_locl.h:74, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_stream.c:38: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: inva= lid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_locl.h:77, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_stream.c:38: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: wa= rning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warn= ing: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: in= valid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_locl.h:74, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_supp.c:36: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: inva= lid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_locl.h:77, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_supp.c:36: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: wa= rning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warn= ing: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: in= valid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_locl.h:74, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/check_password.c:34: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: inva= lid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/kadm_locl.h:77, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe= rosIV/lib/kadm/check_password.c:34: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: wa= rning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warn= ing: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: in= valid macro name mkdep: compile failed *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. root@wintermute#=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 12:42:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from karma.afterthought.org (karma.afterthought.org [208.11.244.6]) by hub.freebsd.org (Postfix) with ESMTP id 558251529B for ; Thu, 13 Jan 2000 12:42:50 -0800 (PST) (envelope-from chenresig@karma.afterthought.org) Received: (from chenresig@localhost) by karma.afterthought.org (8.9.3/8.9.3) id PAA67876; Thu, 13 Jan 2000 15:42:29 -0500 (EST) (envelope-from chenresig) Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001132000.MAA82890@apollo.backplane.com> Date: Thu, 13 Jan 2000 15:42:29 -0500 (EST) Organization: Research Triangle Commerce, Inc. From: Thomas Stromberg To: Matthew Dillon , current@freebsd.org Subject: Re: mount_null, local nfs, and jail.. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Jan-2000 Matthew Dillon wrote: >:> Sometimes we just want to nfs-mount things on the same >:> machine. >: >:Sick, poor in performance and the wrong tool for the job. >:See mount_null(8) for more details on how to do it right. >: Unfortunately, you still end up needing to do this for some tasks like cfs: localhost:/ /crypt nfs rw,port=3049,intr,nfsv2,noauto 0 0 Granted, cfs can be rewritten to do it otherwise, but the nfs filter is about the only way to reliably make it cross platform.. However, thanks for the pointer on nullfs.. does this work with jail(8)? Or will it not cross the filesystem boundary.. ============================================================================ Thomas R. Stromberg Asst. IS Manager / Systems Guru FreeBSD Contrib, BeOS Dev, Security Geek Research Triangle Commerce, Inc. http://www.afterthought.org/ http://www.rtci.com/ thomas@stromberg.org tstromberg@rtci.com ======================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 12:56:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 43EEC151CC for ; Thu, 13 Jan 2000 12:56:45 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id MAA33573; Thu, 13 Jan 2000 12:56:17 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001132056.MAA33573@gndrsh.dnsmgr.net> Subject: Re: move portmap(8) from /usr/sbin to /sbin In-Reply-To: <200001132000.MAA82890@apollo.backplane.com> from Matthew Dillon at "Jan 13, 2000 12:00:22 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 13 Jan 2000 12:56:17 -0800 (PST) Cc: ntakpe@ffab.tide.ti.com (Jean Louis Ntakpe), dwmalone@maths.tcd.ie (David Malone), mb@imp.ch, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> Sometimes we just want to nfs-mount things on the same > :> machine. > : > :Sick, poor in performance and the wrong tool for the job. > :See mount_null(8) for more details on how to do it right. > : > :> > :> One more example: I don't like /var/news so I mount locally > :> /var/news > :> to /archive/news on the same system instead of using > :> symlinks. > :> My rc.local manages it for me. > : > :Sick. See above. > > I gotta agree, this is sick. But to put the icing on the cake: LOCAL > NFS MOUNTS CAN LEAD TO LOW-MEMORY DEADLOCKS. Even with my recent fixes > to -current there is still a non-zero chance of this happening. This use to be documented some place, but I can't find it :-(. [Good example of how to do things deleted] -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 13: 2:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 27DC91555D for ; Thu, 13 Jan 2000 13:02:30 -0800 (PST) (envelope-from dervish@goku.cl.msu.edu) Received: (from dervish@localhost) by goku.cl.msu.edu (8.9.3/8.9.3) id QAA97873 for freebsd-current@FreeBSD.ORG; Thu, 13 Jan 2000 16:08:19 -0500 (EST) (envelope-from dervish) Date: Thu, 13 Jan 2000 16:08:18 -0500 From: Bush Doctor To: freebsd-current@FreeBSD.ORG Subject: Re: make buildworld fails (yet another failure) Message-ID: <20000113160818.C21935@goku.cl.msu.edu> References: <200001132027.PAA94904@entropy.tmok.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 1.0i In-Reply-To: <200001132027.PAA94904@entropy.tmok.com>; from wonko@users.tmok.com on Thu, Jan 13, 2000 at 03:27:34PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Brian Hechinger aka (wonko@users.tmok.com) said: > i've read all the 'make buildworld fails' e=7Fmessages on this list, but = none > of them have helped me. i tried the 'make b=7F-m /usr/src/share/mk build= world' > and that fixes some problems, but i'm still getting hung up on this one. >=20 > i'm upgrading from 3.4-stable to 4.0-current (in a vain attempt to get the > coldfusion server to run under FreeBSD so we can get rid of Linux, which = can > do 5 requests a second single CPU but only 4 requests a second with two C= PUs) >=20 > here is the output from make where it dies, if you need the whole output i > can send that, but it must be asked for. i haven't built a new kernel yet > since config complains, so i'm assuming i needed to rebuild world before > trying to build a new kernel. if i must have a new kernel FIRST let me k= now > and i'll grab a GENERIC-current kernel. First you must build a new "config". Then config, build and install a new k= ernel. I had the same problem, after a disk crash and having to install anew. My = quick and dirty work around was to comment out "MAKE_KERBEROS4=3D yes" in /etc/ma= ke.conf, delete "/usr/src/kerberosIV", resup and "make {build,install}world. Afterw= ards I enabled kerberos and rebuilt the world. I'm curious as to what is the re= al fix. >=20 > thanks, >=20 > -brian > -- > Included Text Follows: > =3D=3D=3D> libkadm > ln -sf /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/include= /protos.H protos.h > rm -f .depend > mkdep -f .depend -a -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/= kerberosIV/include -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include = -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/krb -I/usr= /src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kdb -I/usr/src/k= erberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm -I/usr/src/kerber= osIV/lib/libkadm/../../../crypto/kerberosIV/lib/roken -I/usr/obj/usr/src/ke= rberosIV/lib/libkadm/../../lib/libkrb -I/usr/obj/usr/src/kerberosIV/lib/lib= kadm/../../lib/libkadm -I/usr/obj/usr/src/kerberosIV/lib/libkadm -I/usr/src= /kerberosIV/lib/libkadm/../../include -DHAVE_CONFIG_H -I/usr/obj/usr/src/ke= rberosIV/lib/libkadm/../../include -DBINDIR=3D\"/usr/bin\" -DSBINDIR=3D\"/u= sr/sbin\" -I/usr/obj/usr/src/i386/usr/include /usr/src/kerberosIV/lib/libk= adm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c /usr/src/kerberosIV= /lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c /usr/src/ker= berosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_supp.c /usr/ob= j/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.c /usr/src/kerb= erosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_locl.h:74, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_cli_wrap.c:30: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: in= valid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_locl.h:77, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_cli_wrap.c:30: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: = warning: `ERROR_TABLE_BASE_' redefined > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: wa= rning: this is the location of the previous definition > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: = invalid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_locl.h:74, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_stream.c:38: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: in= valid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_locl.h:77, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_stream.c:38: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: = warning: `ERROR_TABLE_BASE_' redefined > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: wa= rning: this is the location of the previous definition > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: = invalid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_locl.h:74, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_supp.c:36: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: in= valid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_locl.h:77, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_supp.c:36: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: = warning: `ERROR_TABLE_BASE_' redefined > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: wa= rning: this is the location of the previous definition > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: = invalid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_locl.h:74, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/check_password.c:34: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: in= valid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_locl.h:77, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/check_password.c:34: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: = warning: `ERROR_TABLE_BASE_' redefined > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: wa= rning: this is the location of the previous definition > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: = invalid macro name > mkdep: compile failed > *** Error code 1 >=20 > Stop. > *** Error code 1 >=20 > Stop. > *** Error code 1 >=20 > Stop. > *** Error code 1 >=20 > Stop. > *** Error code 1 >=20 > Stop. > root@wintermute#=20 >=20 >=20 #:^) --=20 f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 13:43:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 2D4F514E6D for ; Thu, 13 Jan 2000 13:42:58 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Fri, 14 Jan 2000 08:34:45 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: Additional option to ls -l for large files In-reply-to: <200001130552.VAA31097@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Thu, Jan 13, 2000 at 04:45:45PM +1100 To: "Rodney W. Grimes" Cc: current@FreeBSD.ORG Message-Id: <00Jan14.083445est.40323@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <8070C3A4E99ED211A63200105A19B99B3174AA@mail.edifecs.com> <200001130552.VAA31097@gndrsh.dnsmgr.net> Date: Fri, 14 Jan 2000 08:34:44 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Jan-13 16:45:45 +1100, "Rodney W. Grimes" wrote: >All of the boot time reporting is in 2^20 MB: >ad0: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S > >Due the math if you doubt me, oh, and Quantum calls this a 3.2G disk >drive :-) 6256*16*63*512 = 3,228,696,576 ~= 3.2*10^9 or 3079.1*2^20 or 3.007*2^30 Some manufacturers note that `1GB = 10^9 bytes' in the fine print. Quantum can also state (correctly) that they are complying with the SI standard. This is still an improvement on the old approach of quoting _unformatted_ capacity (which is ~50% more). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 14: 0:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id EAF09155F3 for ; Thu, 13 Jan 2000 14:00:38 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 13428 invoked by uid 1001); 13 Jan 2000 22:00:14 -0000 Date: Thu, 13 Jan 2000 14:00:14 -0800 From: Jason Evans To: Wilko Bulte Cc: current@FreeBSD.ORG Subject: Re: Make world breakage... Message-ID: <20000113140014.M302@sturm.canonware.com> References: <200001121956.e0CJuNw65075@gratis.grondar.za> <20000112220725.A2942@yedi.iaf.nl> <20000112132225.T302@sturm.canonware.com> <20000113001631.C4148@yedi.iaf.nl> <20000112172522.A21639@dragon.nuxi.com> <20000113083024.A50096@yedi.iaf.nl> <20000113203515.A1321@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000113203515.A1321@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Thu, Jan 13, 2000 at 08:35:16PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 08:35:16PM +0100, Wilko Bulte wrote: > I resurrected things by grabbing an 'old' .4 library from another Alpha. > Now things work again. In case you missed it, I checked in a probable fix for the bug that got you last time around. You might try again now. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 14:26:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust85.tnt2.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 29286152CE; Thu, 13 Jan 2000 14:26:53 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Thu, 13 Jan 2000 17:26:50 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: ATAPI broken, but why? In-Reply-To: <200001131643.RAA20144@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 Jan 2000, Soren Schmidt wrote: > It seems Brian Fundakowski Feldman wrote: > > I'm sure everyone's seen my e-mail and others' e-mail about ATAPI in the > > ATA driver, at least, being broken (WRT CD-Rs). The question is, does > > anyone have any idea at all why? I tried reverting to just before the > > CDRIOC* changes, and that didn't help (using wormcontrol to test that). > > If any of you have any hints at all, please let me know. > > Uhm, if reverting the driver to the state BEFORE the change doesn't > help, you probably should look somewhere else, as you stated once > that that used to work. Have you change other things in the system ? > Overclocking ? checked the cables ? can you check the drive otherwise ? I was trying to rule out the CDRIO* changes themselves being at fault. It seems they're not, but another person also share's my experiences with no longer being able to write CDs now. How about this: I'll find out when it broke, and perhaps we can work from there? > > -Søren > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 15:40:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 4863615072; Thu, 13 Jan 2000 15:40:31 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id PAA10564; Thu, 13 Jan 2000 15:40:30 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA78907; Thu, 13 Jan 2000 15:40:29 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 13 Jan 2000 15:40:29 -0800 (PST) Message-Id: <200001132340.PAA78907@vashon.polstra.com> To: obrien@freebsd.org Subject: Re: C++ exceptions doesn't work in shared libraries In-Reply-To: <20000112080010.A87827@dragon.nuxi.com> References: <387B1603.E353CD09@altavista.net> <387C34E5.9E9840AF@altavista.net> <20000112080010.A87827@dragon.nuxi.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000112080010.A87827@dragon.nuxi.com>, David O'Brien wrote: > On Wed, Jan 12, 2000 at 10:01:42AM +0200, Maxim Sobolev wrote: > > Is there are any compiler guys to address my question or not? > > There is, I'm the one. But there are a few things ahead in the queue. > Of course a patch would make things go much faster. The problem is caused by the fact that we are still using our own home-grown versions of crtbegin.o and crtend.o (from "src/lib/csu"). We need to use the ones built from crtstuff.c in "src/contrib/gcc". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 15:42: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id F166D15585 for ; Thu, 13 Jan 2000 15:42:04 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca44-58.ix.netcom.com [209.111.212.186]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id PAA88584; Thu, 13 Jan 2000 15:42:03 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id PAA33306; Thu, 13 Jan 2000 15:41:57 -0800 (PST) To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: Make world breakage... References: <200001131642.e0DGgvw69943@gratis.grondar.za> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 13 Jan 2000 15:41:53 -0800 In-Reply-To: Mark Murray's message of "Thu, 13 Jan 2000 18:42:56 +0200" Message-ID: Lines: 12 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Mark Murray * ...then your source tree is not up to date. It seems the crypto part of the tree was not updated. Probably from the time I was juggling cvsupfiles around trying to figure out the "can't build in US" problem. I'll let you know if I have any more problems. BTW, we can soon stop worrying about the crypto stuff, right? :) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 15:45:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 05E5B14C3C; Thu, 13 Jan 2000 15:45:34 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id SAA13451; Thu, 13 Jan 2000 18:45:39 -0500 (EST) Date: Thu, 13 Jan 2000 18:45:39 -0500 (EST) From: "Mr. K." To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: process hung in ttywri Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I figured out how to reproduce the ttywri hang at will (I'm sure there are other ways, but this works for me 100%): 1) using SecureCRT and ssh2, ssh into your machine 2) run "find /" 3) click your mouse in the window and hold down. the scrolling will stop. hold this down for a few seconds. 4) let go of the mouse button, the buffer will flush and then the process will hang in ttywri: 2847 anthony 4 0 936K 620K ttywri 0:00 0.00% 0.00% find Since I can reproduce this at will, on both stable and current, if anyone wants me to reproduce it and give the results of something, let me know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 16:34:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [216.99.193.36]) by hub.freebsd.org (Postfix) with ESMTP id 17E17155BC; Thu, 13 Jan 2000 16:34:13 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id QAA28716; Thu, 13 Jan 2000 16:34:11 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id QAA21010; Thu, 13 Jan 2000 16:34:57 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Thu, 13 Jan 2000 16:34:57 -0800 (PST) From: Brian Beattie To: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: UDF Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been looking at UDF ( the filesystem used on CD-RW and DVD's ). I was wondering if anybody was working on it. I'm thinking about trying to implement it for CD-RW's and would like to avoid duplication of effort and the anoyance of getting half way through the effort and having somebody else show up with a completed implementation. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 19:20: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from msk1.mail.ru (mx1.mail.ru [194.67.23.32]) by hub.freebsd.org (Postfix) with ESMTP id 1353614CAC; Thu, 13 Jan 2000 19:20:03 -0800 (PST) (envelope-from kabaev@mail.ru) Received: from h0050da20495b.ne.mediaone.net ([24.147.104.88] helo=kan.ne.mediaone.net) by msk1.mail.ru with esmtp (Exim 3.02 #116) id 128xOg-000OXu-00; Fri, 14 Jan 2000 06:27:34 +0300 Received: (from kan@localhost) by kan.ne.mediaone.net (8.9.3/8.9.3) id WAA06887; Thu, 13 Jan 2000 22:19:57 -0500 (EST) (envelope-from kan) 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: <387CAD7B.678B03E3@altavista.net> Date: Thu, 13 Jan 2000 22:19:57 -0500 (EST) From: "Alexander N. Kabaev" To: Maxim Sobolev Subject: Re: C++ exceptions doesn't work in shared libraries Cc: current@FreeBSD.ORG, obrien@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I tried to investigate this problem and the following is what I've found so far: It looks like we are dealing with gcc -O code generation bug. I recompiled libgcc and libgcc_r without -O flag and everything works just fine, including the sample from PR3441. Unfortunately, I was unable to locate exact place where it blows yet, although _builtin_setjmp seems to be very suspicious. I will post the result of my 'investigation' if something interesting will come out of it :) On 12-Jan-00 Maxim Sobolev wrote: > David O'Brien wrote: > >> On Wed, Jan 12, 2000 at 10:01:42AM +0200, Maxim Sobolev wrote: >> > Is there are any compiler guys to address my question or not? >> >> There is, I'm the one. But there are a few things ahead in the queue. > > Please excuse me if I've offended you, but I just doubted that no one has > read > my message, so I've tried to check for sure ;). Hovewer it seems that I've > selected wrong way to do it, so I'll try to be more patient in the future. > >> Of course a patch would make things go much faster. > > Unfortunately, I'm not one of the "compiler gurus", so it would be almost > impossible for me to fix this problem. > > -Maxim > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: Alexander N. Kabaev Date: 13-Jan-00 Time: 22:06:51 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 19:40: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from msk2.mail.ru (mx2.mail.ru [194.67.23.33]) by hub.freebsd.org (Postfix) with ESMTP id A566B1504B; Thu, 13 Jan 2000 19:40:00 -0800 (PST) (envelope-from kabaev@mail.ru) Received: from h0050da20495b.ne.mediaone.net ([24.147.104.88] helo=kan.ne.mediaone.net) by msk2.mail.ru with esmtp (Exim 3.02 #116) id 128xfN-000PAr-00; Fri, 14 Jan 2000 06:44:50 +0300 Received: (from kan@localhost) by kan.ne.mediaone.net (8.9.3/8.9.3) id WAA09316; Thu, 13 Jan 2000 22:39:53 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 13 Jan 2000 22:39:53 -0500 (EST) From: "Alexander N. Kabaev" To: "Alexander N. Kabaev" Subject: Re: C++ exceptions doesn't work in shared libraries Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG, Maxim Sobolev Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am sorry, my previous letter was incorrect. Compiling libgcc{_r}.a without optimisation stopped _my_ test program and the program from PR from crashing, but any attempt to rethrow the exception from the catch block in Foo() results in signal 11 crash. ---------------------------------- E-Mail: Alexander N. Kabaev Date: 13-Jan-00 Time: 22:35:50 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 21:53:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 5EF5C14D34; Thu, 13 Jan 2000 21:53:05 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id e0E5r2w74025; Fri, 14 Jan 2000 07:53:02 +0200 (SAST) Message-Id: <200001140553.e0E5r2w74025@gratis.grondar.za> To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Cc: current@FreeBSD.ORG Subject: Re: Make world breakage... References: In-Reply-To: ; from asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) "13 Jan 2000 15:41:53 PST." Date: Fri, 14 Jan 2000 07:53:02 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > BTW, we can soon stop worrying about the crypto stuff, right? :) It sure seems so! :-) RSA will be the only problem for USA, and IDEA will be aproblem in Europe. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 22:38:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id DDAE1155F3 for ; Thu, 13 Jan 2000 22:38:53 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu (root@rac4.wam.umd.edu [128.8.10.144]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA04164 for ; Fri, 14 Jan 2000 01:38:43 -0500 (EST) Received: from rac4.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id BAA00367 for ; Fri, 14 Jan 2000 01:38:47 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA00363 for ; Fri, 14 Jan 2000 01:38:47 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Fri, 14 Jan 2000 01:38:47 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: latest ppbus changes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The latest ppbus changes seem to have made some things break. My dmesg no longer shows lpt0 or vpo0 as being detected ( even though they are defined in the kernel conf file, and are being compiled into the kernel) which means I can't print anything or use my parallel port zip drive. (yes I have scbus0 and da0 defined in the kernel also.) Just thought I'd let someone know. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 23:23:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id 11A7B14DCD for ; Thu, 13 Jan 2000 23:23:12 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas5-23-24.dial.proxad.net [213.228.23.24]) by postfix2.free.fr (Postfix) with ESMTP id 524027403F; Fri, 14 Jan 2000 08:23:10 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id IAA00471; Fri, 14 Jan 2000 08:26:54 +0100 (CET) (envelope-from nsouch) Message-ID: <20000114082654.11981@armor.free.fr> Date: Fri, 14 Jan 2000 08:26:54 +0100 From: Nicolas Souchu To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: latest ppbus changes References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Kenneth Wayne Culver on Fri, Jan 14, 2000 at 01:38:47AM -0500 X-Operating-System: FreeBSD armor 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 14, 2000 at 01:38:47AM -0500, Kenneth Wayne Culver wrote: > >The latest ppbus changes seem to have made some things break. My dmesg no >longer shows lpt0 or vpo0 as being detected ( even though they are defined >in the kernel conf file, and are being compiled into the kernel) which >means I can't print anything or use my parallel port zip drive. (yes I >have scbus0 and da0 defined in the kernel also.) Just thought I'd let >someone know. Would you mind checking your ioconf.c file and send it to me eventually. In principle, ppbus now relies on it to attach/probe devices. Otherwise, the rest of ppbus (ppc/ppbus and maybe plip/ppi) are probed and attached? > > >================================================================= >| Kenneth Culver | FreeBSD: The best OS around. | >| Unix Systems Administrator | ICQ #: 24767726 | >| and student at The | AIM: AgRSkaterq | >| The University of Maryland, | Website: (Under Construction) | >| College Park. | http://www.wam.umd.edu/~culverk/| >================================================================= > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 23:38:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from clavin.cluepon.com (clavin.cluepon.com [209.220.43.103]) by hub.freebsd.org (Postfix) with ESMTP id D74ED14E36 for ; Thu, 13 Jan 2000 23:38:16 -0800 (PST) (envelope-from lamont@cluepon.com) Received: from clavin.cluepon.com ([209.220.43.103]) by clavin.cluepon.com with esmtp (Exim 3.03 #1) id 1291JV-000NRB-00 for freebsd-current@freebsd.org; Thu, 13 Jan 2000 23:38:29 -0800 Date: Thu, 13 Jan 2000 23:38:29 -0800 (PST) From: Lamont Lucas To: freebsd-current@freebsd.org Subject: Problems attempting to upgrade from 3.4-stable to -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been trying unsuccessfully for two days to upgrade to -current on one of my machines at home, and was hoping there might be some suggestions from the group I could try. This is the consistant error off of today's -current tree: cc -O -pipe -elf -Wall -fkeep-inline-functions -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/csu/i386-elf/crt1.c -o crt1.o cc: Internal compiler error: program cc1 got fatal signal 12 *** Error code 1 I realize that the handbooks suggests this could be a hardware error, but I'm dubious since the problem occurs in this spot consistantly, both between re make buildworlds and after a make clean;make buildworld. Yesterday's problems were mostly due to what the mailing lists seems to describe as the bootstrapping problem with libc, although a make include and a (cd /usr/src/lib/libc; make install) failed to resolve the problem. Is there any other information that I could give that may help? The machine has been running -stable for a week or so with no problems, using ram I've had no problem with in other machines. Any suggestions or work arounds? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 23:45:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id ADED714DB4; Thu, 13 Jan 2000 23:45:54 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA29742; Fri, 14 Jan 2000 08:45:53 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001140745.IAA29742@freebsd.dk> Subject: Re: ATAPI broken, but why? In-Reply-To: from Brian Fundakowski Feldman at "Jan 13, 2000 05:26:50 pm" To: green@FreeBSD.org (Brian Fundakowski Feldman) Date: Fri, 14 Jan 2000 08:45:53 +0100 (CET) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Brian Fundakowski Feldman wrote: > > I was trying to rule out the CDRIO* changes themselves being at fault. > It seems they're not, but another person also share's my experiences > with no longer being able to write CDs now. How about this: I'll > find out when it broke, and perhaps we can work from there? Deal! :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 13 23:52: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id 266411517A for ; Thu, 13 Jan 2000 23:51:59 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas5-23-24.dial.proxad.net [213.228.23.24]) by postfix2.free.fr (Postfix) with ESMTP id 4AFB77403D; Fri, 14 Jan 2000 08:51:55 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id IAA01038; Fri, 14 Jan 2000 08:55:39 +0100 (CET) (envelope-from nsouch) Message-ID: <20000114085539.10099@armor.free.fr> Date: Fri, 14 Jan 2000 08:55:39 +0100 From: Nicolas Souchu To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: latest ppbus changes References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=zhXaljGHf11kAtnf X-Mailer: Mutt 0.81e In-Reply-To: ; from Kenneth Wayne Culver on Fri, Jan 14, 2000 at 01:38:47AM -0500 X-Operating-System: FreeBSD armor 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii On Fri, Jan 14, 2000 at 01:38:47AM -0500, Kenneth Wayne Culver wrote: No problem here, I attach you the MACHINE and dmesg. -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="coreff.dmesg" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Fri Jan 14 08:49:41 CET 2000 nsouch@armor:/usr/devel/current/src/sys/compile/COREFF Timecounter "i8254" frequency 1193182 Hz CPU: AMD Enhanced Am486DX4 Write-Through (486-class CPU) Origin = "AuthenticAMD" Id = 0x484 Stepping = 4 Features=0x1 real memory = 25165824 (24576K bytes) avail memory = 21917696 (21404K bytes) npx0: on motherboard npx0: INT 16 interface isa0: on motherboard devclass_alloc_unit: npx0 already exists, using next available unit number 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 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 flags 0xb0 on isa0 sio1: type 16550A, console sio2: not probed (disabled) sio3: not probed (disabled) pcf0: at port 0x320-0x321 irq 5 on isa0 iicbus0: on pcf0 addr 0xaa iicsmb0: on iicbus0 smbus0: on iicsmb0 smb0: on smbus0 iic0: on iicbus0 ppc0: at port 0x278-0x27f irq 7 on isa0 ppc0: SMC FDC37C666GT chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold ppbus0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: PRINTER HP ENHANCED PCL5,PJL pps0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ppi0: on ppbus0 vpo0: on ppbus0 vpo0: EPP 1.9 mode pca0 at port 0x40 on isa0 pca0: PC speaker audio driver ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 ed0: address 00:40:05:4a:29:02, type NE2000 (16 bit) ep0: not probed (disabled) da0 at vpo0 bus 0 target 6 lun 0 da0: Removable Direct Access SCSI-2 device da0: Attempt to query device size failed: NOT READY, Medium not present bootpc_init: wired to interface 'ed0' bootpc_init: using network interface 'ed0' Bootpc testing starting bootpc hw address is 0:40:5:4a:29:2 My ip address is 10.2.0.1 Server ip address is 10.2.0.2 Gateway ip address is 0.0.0.0 boot file is kernel.coreff Ignoring field type 54 Subnet mask is 255.255.0.0 rootfs is 10.2.0.2:/ Ignoring field type 28 swapfs is 10.2.0.2:/diskless/swapfs md_lookup_swap: Swap size is 16000 KB Mounting root from nfs: NFS ROOT: 10.2.0.2:/ NFS SWAP: 10.2.0.2:/diskless/swapfs --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=COREFF # # COREFF # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # machine "i386" cpu "I486_CPU" ident COREFF maxusers 32 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console # Kernel BOOTP support options BOOTP # Use BOOTP to obtain IP address/hostname options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info #options BOOTP_NFSV3 # Use NFS v3 to NFS mount root options BOOTP_COMPAT # Workaround for broken bootp daemons. options BOOTP_WIRED_TO=ed0 # Use interface fxp0 for BOOTP #options DDB # enable debugger #options GDB_REMOTE_CHAT #options PNPBIOS device isa0 device pci0 device fdc0 at isa? port "IO_FD1" irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 #device wdc0 at isa? port "IO_WD1" bio irq 14 #device wd0 at wdc0 drive 0 #device wd1 at wdc0 drive 1 #device wdc1 at isa? port "IO_WD2" bio irq 15 #device wd2 at wdc1 drive 0 #device wd3 at wdc1 drive 1 device ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives #device acd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. device ahc0 device scbus0 device da0 device pass0 # atkbdc0 controlls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at nexus? device sio0 at isa? port "IO_COM1" irq 4 device sio1 at isa? port "IO_COM2" flags 0xB0 irq 3 device sio2 at isa? disable port "IO_COM3" irq 5 device sio3 at isa? disable port "IO_COM4" irq 9 # I2Cbus device iicbus0 device iicbb0 # I2C to SMB bridge device iicsmb0 at iicbus? device iic0 at iicbus? # SMBus device smbus0 device smb0 at smbus? device pcf0 at isa? port 0x320 irq 5 # Parallel port options PPC_PROBE_CHIPSET device ppc0 at isa? port? irq 7 device ppbus0 device pps0 at ppbus? device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device lpbb0 at ppbus? # PPB to I2C bridge device vpo0 at ppbus? #device snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 #device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x0 device pca0 at isa? port IO_TIMER1 # # The following Ethernet NICs are all PCI devices. # # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device fxp0 device ed0 at isa? port 0x300 irq 10 iomem 0xd8000 device ep0 at isa? disable port 0x300 irq 10 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpf #Berkeley packet filter # USB support #device uhci0 #device ohci0 #device usb0 # # for the moment we have to specify the priorities of the device # drivers explicitly by the ordering in the list below. This will # be changed in the future. # #device ums0 #device ukbd0 #device ulpt0 #device ucom0 #device umodem0 #device uhid0 #device ugen0 # #options USB_DEBUG #options USBVERBOSE --zhXaljGHf11kAtnf-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 0:22:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id A709B1500D for ; Fri, 14 Jan 2000 00:22:10 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B32641CD4; Fri, 14 Jan 2000 16:22:05 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: latest ppbus changes In-Reply-To: Message from Kenneth Wayne Culver of "Fri, 14 Jan 2000 01:38:47 EST." Date: Fri, 14 Jan 2000 16:22:05 +0800 From: Peter Wemm Message-Id: <20000114082205.B32641CD4@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > The latest ppbus changes seem to have made some things break. My dmesg no > longer shows lpt0 or vpo0 as being detected ( even though they are defined > in the kernel conf file, and are being compiled into the kernel) which > means I can't print anything or use my parallel port zip drive. (yes I > have scbus0 and da0 defined in the kernel also.) Just thought I'd let > someone know. Add back the 'at ppbus?' at the end of vpo0 and lpt0 lines. That's how the driver locates it's children now. That text wasn't used before, but is now for the first time. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 0:30:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 429AA15182; Fri, 14 Jan 2000 00:30:05 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA40109; Fri, 14 Jan 2000 09:29:58 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001140829.JAA40109@freebsd.dk> Subject: Re: UDF In-Reply-To: from Brian Beattie at "Jan 13, 2000 04:34:57 pm" To: beattie@aracnet.com (Brian Beattie) Date: Fri, 14 Jan 2000 09:29:58 +0100 (CET) Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Brian Beattie wrote: > I have been looking at UDF ( the filesystem used on CD-RW and DVD's ). I > was wondering if anybody was working on it. I'm thinking about trying to > implement it for CD-RW's and would like to avoid duplication of effort and > the anoyance of getting half way through the effort and having somebody > else show up with a completed implementation. I have it on my TODO list, but I'm not started yet, and probably wont for some time to come. The reason I've put it on the backburner for now, is that DVD's can be read using the cd9660 filesystem, and that is sufficient for my needs for the time being. I have however started to implement the needed functionality in the ata driver, so we should probably coordinate that part of the matter.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 1:20:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 6EB3B14F8F for ; Fri, 14 Jan 2000 01:20:36 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 1292tj-0000CT-00; Fri, 14 Jan 2000 11:19:59 +0200 From: Sheldon Hearn To: "Mr. K." Cc: current@FreeBSD.ORG Subject: Re: lint not working on -current? In-reply-to: Your message of "Thu, 13 Jan 2000 13:52:50 EST." Date: Fri, 14 Jan 2000 11:19:59 +0200 Message-ID: <772.947841599@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 Jan 2000 13:52:50 EST, "Mr. K." wrote: > First of all, forgive me for being stupid, if that's what it turns out it > was, but I can't seem to get lint to work on -current (though it works > fine on -stable). > > > lint -V pvselect.c You'd want lint -i, since we don't install any .ln files into /usr/libdata/lint. But yes, lint is actually broken for the new cpp as well. I mailed publically a patch to fix this last week. Not a single follow-up since then, so I'll commit it now. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 1:43:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id DBA59150E4 for ; Fri, 14 Jan 2000 01:43:38 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Jan 2000 09:43:38 +0000 (GMT) Date: Fri, 14 Jan 2000 09:43:37 +0000 From: David Malone To: Lamont Lucas Cc: freebsd-current@freebsd.org Subject: Re: Problems attempting to upgrade from 3.4-stable to -current Message-ID: <20000114094337.B25259@walton.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from lamont@cluepon.com on Thu, Jan 13, 2000 at 11:38:29PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 11:38:29PM -0800, Lamont Lucas wrote: > This is the consistant error off of today's -current tree: > > cc -O -pipe -elf -Wall -fkeep-inline-functions > -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/csu/i386-elf/crt1.c -o > crt1.o > cc: Internal compiler error: program cc1 got fatal signal 12 > *** Error code 1 Have a look at /usr/src/UPDATING - the bit about signal changes - that was producing signal 12's on people. Now may be a bad time to try tu upgrade by building world though, as there are lots of changes to the tree going on. I think the plan is that it should work sometime soon though. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 1:51:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id CD52414D8B; Fri, 14 Jan 2000 01:51:36 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id LAA75735; Fri, 14 Jan 2000 11:55:56 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 14 Jan 2000 11:55:55 +0200 (EET) From: Adrian Penisoara To: Sheldon Hearn Cc: Trond Endrestol , FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <9039.947589746@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, 11 Jan 2000, Sheldon Hearn wrote: > Not until someone can explain how making /var/tmp a symlink to /tmp is > sensible, given that /var/tmp is documented as containing "temporary > files that are kept between system reboots" (see hier(7)). > > So basically, no. :-) Then let's get the other way around (change in /etc/rc): # Recover vi editor files. -find /var/tmp/vi.recover ! -type f -a ! -type d -delete +if [ -d /var/tmp/vi.recover ]; then + find /var/tmp/vi.recover ! -type f -a ! -type d -delete +fi vibackup=`echo /var/tmp/vi.recover/vi.*` if [ "$vibackup" != '/var/tmp/vi.recover/vi.*' ]; then echo 'Recovering vi editor sessions' And don't worry about loosing /var/tmp/vi.recover every time you reboot (unless you really care about loosing the abillity to recover vi edits between reboots) -- the first time you run vi it will recreate this directory. And let me notice that the original script assumes existence of this directory whereas if I don't run vi I won't get one... I use this small hack to get around the ugly error message I get every time I boot with MFS mounted /var/tmp -- suited me well until now. > > Ciao, > Sheldon. > Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 1:59:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 8CC041512A; Fri, 14 Jan 2000 01:59:29 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 1293VK-0000Om-00; Fri, 14 Jan 2000 11:58:50 +0200 From: Sheldon Hearn To: Adrian Penisoara Cc: Trond Endrestol , FreeBSD stable , FreeBSD current Reply-To: freebsd-chat@freebsd.org Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-reply-to: Your message of "Fri, 14 Jan 2000 11:55:55 +0200." Date: Fri, 14 Jan 2000 11:58:50 +0200 Message-ID: <1535.947843930@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Let's try not to cross-post this any more, eh? On Fri, 14 Jan 2000 11:55:55 +0200, Adrian Penisoara wrote: > Then let's get the other way around (change in /etc/rc): No, you're missing the point. /var/tmp is expected to survive reboots. That's its definition according to the hier(7) manual page. If you choose to break that functionality, don't expect anyone to make gratuitous changes to the FreeBSD startup scripts to support your oddball configuration. :-) > And let me notice that the original script assumes existence of this > directory whereas if I don't run vi I won't get one... It does so because of the definition of /var/tmp . > I use this small hack to get around the ugly error message I get every > time I boot with MFS mounted /var/tmp -- suited me well until now. You shouldn't be mounting /var/tmp in MFS, because a memory file system does not survive a reboot -- that's where you've gone wrong. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 1:59:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from lychee.itojun.org (ny-ppp015.iij-us.net [216.98.99.15]) by hub.freebsd.org (Postfix) with ESMTP id 0E9A0152D4 for ; Fri, 14 Jan 2000 01:59:42 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost [127.0.0.1]) by itojun.org (8.9.3+3.2W/3.7W) with ESMTP id BAA00581; Fri, 14 Jan 2000 01:58:56 -0800 (PST) Cc: Yoshinobu Inoue To: freebsd-current@freebsd.org In-reply-to: itojun's message of Fri, 14 Jan 2000 18:08:52 JST. <26427.947840932@coconut.itojun.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: [solicite review and confirmation of tcp for IPv6 patches] From: Jun-ichiro itojun Hagino Date: Fri, 14 Jan 2000 01:58:56 -0800 Message-ID: <579.947843936@lychee.itojun.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- >http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/tcp-apps.20000114 >http://www.FreeBSD.org/~shin/tcp-apps.20000114 > >They includes, > -inetd > -libutil > -rlogin > -rlogind > -rshd > -telnetd > >As far as I checked, those apps seems to be working over both >IPv4 and IPv6. Sorry for delayed response, and sorry for doing this here (I should have talked about this in KAME team earlier, I think I have noted about rcmd API issues already to shin, before freebsd IPv6 commits start) I suggest to defer committing rsh/rlogin related items, as there are reference to libc functions which we do not have consensus even among *BSD (not to mention linux camp, or any of vendor UN*X which may have those interfaces) IMHO committing them causes more confusion. We do not really use rlogin/rsh these days, we can just use ssh. For realhostname2() I have no opinion as is freebsd only API (as I heard from shin). rcmd and bindresvport items are already committed, I think they shouldn't have been committed.... (for openssh port you can include bindresvport_af in "patches" directory) I would propose to back these out, like iruserok_af and bindresvport_af from the library. Items that would be deferred are rsh and rlogin related items, and those only (I believe). most of other IPv6 services can be put and enabled. What I'm trying to say is that we need to get consensus on these API functions amoung at least *BSDs, and we should not be putting those before that. I'm soliciting comments on IETF ipngwg mailing list so that I can get more comments. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 2: 7:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by hub.freebsd.org (Postfix) with ESMTP id 44BEB14A13; Fri, 14 Jan 2000 02:07:36 -0800 (PST) (envelope-from trond@ramstind.gtf.ol.no) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id LAA20279; Fri, 14 Jan 2000 11:07:24 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Date: Fri, 14 Jan 2000 11:07:23 +0100 (CET) From: Trond Endrestol To: Sheldon Hearn Cc: FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Sheldon Hearn wrote: > Not until someone can explain how making /var/tmp a symlink to /tmp is > sensible, given that /var/tmp is documented as containing "temporary > files that are kept between system reboots" (see hier(7)). > > So basically, no. :-) I chose to use MFS for /tmp and symlinking /var/tmp and /usr/tmp to /tmp for sake of speed. No disk activity is involved when the temporary files on the MFS are in use. (This slightly false if the MFS is paged out or swapped out completely.) If I want something preserved between reboots, I'll use /var/otmp which is the original /var/tmp or my own ~/tmp directory. ---------------------------------------------------------------------- Trond Endrestøl | trond@gtf.ol.no Merkantilvegen 59HB7, | trond@ramstind.gtf.ol.no N-2815 GJØVIK, NORWAY |+47 61139424 || +47 63874242 Patron of The Art of Computer Programming| FreeBSD 3.4 & Pine 4.10 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 2:10:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 512C9155A4; Fri, 14 Jan 2000 02:10:14 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 1293g3-0000T7-00; Fri, 14 Jan 2000 12:09:55 +0200 From: Sheldon Hearn To: Trond Endrestol Cc: FreeBSD stable , FreeBSD current Reply-To: chat@FreeBSD.org Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-reply-to: Your message of "Fri, 14 Jan 2000 11:07:23 +0100." Date: Fri, 14 Jan 2000 12:09:55 +0200 Message-ID: <1804.947844595@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Jan 2000 11:07:23 +0100, Trond Endrestol wrote: > If I want something preserved between reboots, I'll use /var/otmp > which is the original /var/tmp or my own ~/tmp directory. Do whatever grooves your plumes, just don't expect the startup scripts to be hacked around to support your disregard for the hier(7) manual page. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 3:42:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from ds.express.ru (ds.express.ru [212.24.32.7]) by hub.freebsd.org (Postfix) with ESMTP id 8F33614D4E for ; Fri, 14 Jan 2000 03:42:25 -0800 (PST) (envelope-from vova@express.ru) Received: from lanturn.kmost.express.ru ([212.24.37.109]) by ds.express.ru with esmtp (Exim 2.12 #8) id 12957S-0003Yc-00 for current@freebsd.org; Fri, 14 Jan 2000 14:42:18 +0300 Date: Fri, 14 Jan 2000 14:42:20 +0300 (MSK) From: "Vladimir B. Grebeschikov" X-Sender: vova@lanturn.kmost.express.ru To: current@freebsd.org Subject: ATAPI CDROM trouble Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With new ATA driver I have big trouble - I can't use my CDROM while I am do 'mount_cd9660 /dev/acd0c /m/cd' system compleatly holds, no core, no panic - hold (may be deadloop in kernel mode ?) # dmesg .... ad0: ATA-4 disk at ata0 as master ad0: 8223MB (16841664 sectors), 16708 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad2: ATA-3 disk at ata1 as master ad2: 4125MB (8448300 sectors), 8940 cyls, 15 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 > there is pause about 5-10 sec acd0: atapi_timeout: cmd=MODE_SENSE_BIG - resetting ata1: resetting devices .. acd0: read data overrun 8/2 ata1-master: timeout waiting for command=ef s=08 e=68 done acd0: atapi_timeout: cmd=MODE_SENSE_BIG - resetting ata1: resetting devices .. acd0: read data overrun 8/0 acd0: read data overrun 20/0 done acd0: CDROM drive at ata1 as slave acd0: read 2755KB/s (5511KB/s), 240KB buffer, WDMA2 acd0: Reads: CD-R, CD-RW, CD-DA stream acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ... when I am booting without CD in drive pause still exists, but no messages about atapi_timount and resets can anybody help me ? may be I need to make kernel with DDB ? and make some diagnistic ? my kernel config about ata: controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives device atapist0 # ATAPI tape drives options ATA_STATIC_ID #Static dev number like old wd driver options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices /sys/i386/isa# cvs status ata* =================================================================== File: atapi-cd.c Status: Up-to-date Working revision: 1.27 Repository revision: 1.27 /home/ncvs/src/sys/i386/isa/atapi-cd.c,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) =================================================================== File: atapi-cd.h Status: Up-to-date Working revision: 1.6 Repository revision: 1.6 /home/ncvs/src/sys/i386/isa/atapi-cd.h,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) =================================================================== File: atapi.c Status: Up-to-date Working revision: 1.36 Repository revision: 1.36 /home/ncvs/src/sys/i386/isa/atapi.c,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) =================================================================== File: atapi.h Status: Up-to-date Working revision: 1.18 Repository revision: 1.18 /home/ncvs/src/sys/i386/isa/atapi.h,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 3:51:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E5EA214D3B for ; Fri, 14 Jan 2000 03:51:36 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA87144; Fri, 14 Jan 2000 12:50:19 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001141150.MAA87144@freebsd.dk> Subject: Re: ATAPI CDROM trouble In-Reply-To: from "Vladimir B. Grebeschikov" at "Jan 14, 2000 02:42:20 pm" To: vova@express.ru (Vladimir B. Grebeschikov) Date: Fri, 14 Jan 2000 12:50:19 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Vladimir B. Grebeschikov wrote: > > With new ATA driver I have big trouble > - I can't use my CDROM > > while I am do 'mount_cd9660 /dev/acd0c /m/cd' > system compleatly holds, no core, no panic - hold (may be deadloop in > kernel mode ?) > options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices Dont define this until you know the drive is functioning otherwise, LOTS and I mean LOTS of atapi devices dont do DMA even if advertised. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 4:59:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 9E60515036 for ; Fri, 14 Jan 2000 04:59:20 -0800 (PST) (envelope-from darius@dons.net.au) Received: from guppy.dons.net.au (darius@guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id XAA53049; Fri, 14 Jan 2000 23:28:54 +1030 (CST) (envelope-from darius@dons.net.au) 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: <200001141150.MAA87144@freebsd.dk> Date: Fri, 14 Jan 2000 23:28:54 +1030 (CST) From: "Daniel J. O'Connor" To: Soren Schmidt Subject: Re: ATAPI CDROM trouble Cc: current@FreeBSD.ORG, (Vladimir B. Grebeschikov) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Jan-00 Soren Schmidt wrote: > Dont define this until you know the drive is functioning otherwise, > LOTS and I mean LOTS of atapi devices dont do DMA even if advertised. Would it be possible to implement this as something like a 'quirk list'? ie list known good (or bad) drives and enable (or disable) DMA on them. --- 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-current" in the body of the message From owner-freebsd-current Fri Jan 14 5: 4: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7D394151C4 for ; Fri, 14 Jan 2000 05:04:01 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA04565; Fri, 14 Jan 2000 14:03:42 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001141303.OAA04565@freebsd.dk> Subject: Re: ATAPI CDROM trouble In-Reply-To: from "Daniel J. O'Connor" at "Jan 14, 2000 11:28:54 pm" To: darius@dons.net.au (Daniel J. O'Connor) Date: Fri, 14 Jan 2000 14:03:42 +0100 (CET) Cc: current@FreeBSD.ORG, vova@express.ru X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Daniel J. O'Connor wrote: > > On 14-Jan-00 Soren Schmidt wrote: > > Dont define this until you know the drive is functioning otherwise, > > LOTS and I mean LOTS of atapi devices dont do DMA even if advertised. > > Would it be possible to implement this as something like a 'quirk list'? > > ie list known good (or bad) drives and enable (or disable) DMA on them. It would have to be a list of known good drives on known working chipsets, in effect a list that would be next to impossible to maintain. If you have ATAPI hw that are more than 6-12month old, bets are it wont work, newer devices seems more capable, but still alot of them claim to support DMA, but fail utterly always or on some chipset combinations. The only way to know is to try it out and see for yourself, the ATAPI device manufactures should have thier fingers smacked, hard .... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 5:23: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from ds.express.ru (ds.express.ru [212.24.32.7]) by hub.freebsd.org (Postfix) with ESMTP id 44F471521E for ; Fri, 14 Jan 2000 05:22:37 -0800 (PST) (envelope-from vova@express.ru) Received: from lanturn.kmost.express.ru ([212.24.37.109]) by ds.express.ru with esmtp (Exim 2.12 #8) id 1296fh-0003Ga-00; Fri, 14 Jan 2000 16:21:45 +0300 Date: Fri, 14 Jan 2000 16:21:47 +0300 (MSK) From: "Vladimir B. Grebeschikov" X-Sender: vova@lanturn.kmost.express.ru To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: ATAPI CDROM trouble In-Reply-To: <200001141150.MAA87144@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=koi8-r Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Jan 2000, Soren Schmidt wrote: > > while I am do 'mount_cd9660 /dev/acd0c /m/cd' > > system compleatly holds, no core, no panic - hold (may be deadloop in > > kernel mode ?) > > > options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices > > Dont define this until you know the drive is functioning otherwise, > LOTS and I mean LOTS of atapi devices dont do DMA even if advertised. I've removed ATA_ENABLE_ATAPI_DMA option: nothing changed :( while boot diagnostic is: acd0: atapi_timeout: cmd=MODE_SENSE_BIG - resetting ata1: resetting devices .. acd0: read data overrun 8/2 ata1-master: timeout waiting for command=ef s=08 e=68 done acd0: atapi_timeout: cmd=MODE_SENSE_BIG - resetting ata1: resetting devices .. acd0: read data overrun 8/0 acd0: read data overrun 20/0 done acd0: CDROM drive at ata1 as slave acd0: read 2755KB/s (5511KB/s), 240KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked I've build kernel with DDB and call debuuger from "hold" state then call panic() from debugger (kgdb) bt #0 0xc015fb48 in boot () #1 0xc015fee5 in panic () #2 0xc013333d in db_fncall () #3 0xc0133169 in db_command () #4 0xc013322e in db_command_loop () #5 0xc01352bf in db_trap () #6 0xc026d43f in kdb_trap () #7 0xc0279e14 in trap () #8 0xc026d69b in Debugger () #9 0xc02698fa in scgetc () #10 0xc0265029 in sckbdevent () #11 0xc02597ab in atkbd_intr () #12 0xc0291398 in atkbd_isa_intr () #13 0xc027efc0 in getit () #14 0xc027f055 in DELAY () #15 0xc0251aa0 in atapi_wait () #16 0xc0251006 in atapi_interrupt () #17 0xc024d90e in ataintr () > -Søren > -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 6: 4:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from enterprise.sanyusan.se (enterprise.sanyusan.se [212.209.55.83]) by hub.freebsd.org (Postfix) with ESMTP id BFFC514EA0 for ; Fri, 14 Jan 2000 06:04:36 -0800 (PST) (envelope-from anders@enterprise.sanyusan.se) Received: (from anders@localhost) by enterprise.sanyusan.se (8.9.3/8.9.3) id PAA04594; Fri, 14 Jan 2000 15:03:48 +0100 (CET) (envelope-from anders) Date: Fri, 14 Jan 2000 15:03:48 +0100 From: Anders Andersson To: Soren Schmidt Cc: "Daniel J. O'Connor" , current@FreeBSD.ORG, vova@express.ru Subject: Re: ATAPI CDROM trouble Message-ID: <20000114150348.A4561@enterprise.sanyusan.se> References: <200001141303.OAA04565@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001141303.OAA04565@freebsd.dk>; from sos@freebsd.dk on Fre, Jan 14, 2000 at 02:03:42pm +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have another problem with CDROM and ata. ata doesnt find my CDROM at all. sos, do you want a verbose dmesg of a kernel with wd that finds the CDROM? Anders -- Anders Andersson anders@sanyusan.se Sanyusan International AB http://www.sanyusan.se/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 6: 9:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from void.dynip.com (hobax1-247.dialup.optusnet.com.au [198.142.190.247]) by hub.freebsd.org (Postfix) with ESMTP id B043E14CE3 for ; Fri, 14 Jan 2000 06:09:06 -0800 (PST) (envelope-from death@southcom.com.au) Received: from windows (windows.void.net [192.168.1.2]) by void.dynip.com (Postfix) with ESMTP id 4D1F755BA; Sat, 15 Jan 2000 01:08:52 +1100 (EST) Message-Id: <4.2.2.20000115010409.01b82260@mail.southcom.com.au> X-Sender: death@mail.southcom.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 15 Jan 2000 01:08:50 +1100 To: Lamont Lucas From: james Subject: Re: Problems attempting to upgrade from 3.4-stable to -current Cc: freebsd-current@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 23:38 13/1/2000 -0800, Lamont Lucas wrote: >Hi, I've been trying unsuccessfully for two days to upgrade to -current on >one of my machines at home, and was hoping there might be some suggestions >from the group I could try. > >This is the consistant error off of today's -current tree: > >cc -O -pipe -elf -Wall -fkeep-inline-functions >-I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/csu/i386-elf/crt1.c -o >crt1.o >cc: Internal compiler error: program cc1 got fatal signal 12 >*** Error code 1 >Any suggestions or work arounds? Hi, I had this same problem - although the signal 12 was coming during installworld when it was installing 'test' or something. My solution was to just download a snapshot of current, and use the 'upgrade' option on the install disks. Worked fine. I read on this list about the same time that there should be no problems at all upgrading from 3.4-STABLE to 4.0-CURRENT by make world'ing, and that signal 12 really does always mean a hardware failure - but this is garbage. Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 6:12:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id EEBA014FA5; Fri, 14 Jan 2000 06:12:43 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (hoefnix.ai [209.88.68.215]) by cypherpunks.ai (Postfix) with ESMTP id E432649; Fri, 14 Jan 2000 10:12:41 -0400 (AST) Message-ID: <387F2E7E.4391BBFF@vangelderen.org> Date: Fri, 14 Jan 2000 10:11:10 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray Cc: Satoshi - Ports Wraith - Asami , current@FreeBSD.ORG Subject: Re: Make world breakage... References: <200001140553.e0E5r2w74025@gratis.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > > BTW, we can soon stop worrying about the crypto stuff, right? :) > > It sure seems so! :-) > > RSA will be the only problem for USA, Only until 20 September 2000 IIRC. > and IDEA will be aproblem in Europe. And the rest of the world. It's patented in Japan and USA too, basically a useless algorithm as there are better free replacements available. (Especially by the time the patent expires.) Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 6:46:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id DCF3E14D4C; Fri, 14 Jan 2000 06:46:23 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id QAA81980; Fri, 14 Jan 2000 16:51:31 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 14 Jan 2000 16:51:31 +0200 (EET) From: Adrian Penisoara To: Trond Endrestol Cc: FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <1535.947843930@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, 14 Jan 2000, Sheldon Hearn wrote: > > > Let's try not to cross-post this any more, eh? I believe the suggested change interests both branches; -chat removed. > > On Fri, 14 Jan 2000 11:55:55 +0200, Adrian Penisoara wrote: > > > Then let's get the other way around (change in /etc/rc): > > No, you're missing the point. /var/tmp is expected to survive reboots. > That's its definition according to the hier(7) manual page. If you > choose to break that functionality, don't expect anyone to make > gratuitous changes to the FreeBSD startup scripts to support your > oddball configuration. :-) > > > And let me notice that the original script assumes existence of this > > directory whereas if I don't run vi I won't get one... > > It does so because of the definition of /var/tmp . > > > I use this small hack to get around the ugly error message I get every > > time I boot with MFS mounted /var/tmp -- suited me well until now. > > You shouldn't be mounting /var/tmp in MFS, because a memory file system > does not survive a reboot -- that's where you've gone wrong. I'm not discussing the definition of /var/tmp ! I just recognise that lots of people (including me) step over this rule (as they don't need those bits to survive reboots, for example) and they MFS mount /var/tmp (at least) for the sake of optimizing compile times (cc uses /var/tmp for temporary files). So that makes us otlaws but this doesn't change the facts... All I want is not to assume existence of /var/tmp/vi.recover in /etc/rc. Because this is a simple hack that by _no chance_ breakes any set rules I believe it to be very good commit candidate. Anyone care to do it ? > > Ciao, > Sheldon. > Thanks, Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 7: 2:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 39D6A14F6E; Fri, 14 Jan 2000 07:02:42 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id RAA82346; Fri, 14 Jan 2000 17:07:52 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 14 Jan 2000 17:07:51 +0200 (EET) From: Adrian Penisoara To: Trond Endrestol Cc: FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <1804.947844595@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, 14 Jan 2000, Sheldon Hearn wrote: > > > On Fri, 14 Jan 2000 11:07:23 +0100, Trond Endrestol wrote: > > > If I want something preserved between reboots, I'll use /var/otmp > > which is the original /var/tmp or my own ~/tmp directory. > > Do whatever grooves your plumes, just don't expect the startup scripts > to be hacked around to support your disregard for the hier(7) manual > page. :-) Like I said, my hack doesn't contradict what hier(7) sais. It's 100% compatible ;-) ! Seriously now, I don't see why you hate so much the ideea of making some (most ?) people's life easier without breaking what's already been set... If it would really break things up then I would agree with you (indeed, the inital proposed chage, symlinking /var/tmp, is just a dirty workaround). > > Ciao, > Sheldon. > Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 7:13: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 2AB1F14C40; Fri, 14 Jan 2000 07:12:59 -0800 (PST) (envelope-from khera@kciLink.com) Received: by kci.kciLink.com (Postfix, from userid 100) id 6F6D3E89D; Fri, 14 Jan 2000 10:12:54 -0500 (EST) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14463.15606.393166.953233@kci.kciLink.com> Date: Fri, 14 Jan 2000 10:12:54 -0500 (EST) To: Trond Endrestol Cc: Sheldon Hearn , FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: References: X-Mailer: VM 6.72 under 21.1 (patch 7) "Biscayne" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "TE" == Trond Endrestol writes: TE> I chose to use MFS for /tmp and symlinking /var/tmp and /usr/tmp to TE> /tmp for sake of speed. TE> No disk activity is involved when the temporary files on the MFS are TE> in use. (This slightly false if the MFS is paged out or swapped out TE> completely.) If vi.recover is not going to survive a reboot, why bother having it at all? That's is sole purpose for existing. If you don't like the warning, just delete the recovery procedure rather than creating the directory. It does no good for you to try to recover something that will never be there. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 7:20:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 2D5B614E30; Fri, 14 Jan 2000 07:20:09 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 1298VX-0001pa-00; Fri, 14 Jan 2000 17:19:23 +0200 From: Sheldon Hearn To: Vivek Khera Cc: Adrian Penisoara , Trond Endrestol , FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-reply-to: Your message of "Fri, 14 Jan 2000 10:12:54 EST." <14463.15606.393166.953233@kci.kciLink.com> Date: Fri, 14 Jan 2000 17:19:23 +0200 Message-ID: <7041.947863163@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Jan 2000 10:12:54 EST, Vivek Khera wrote: > If you don't like the warning, just delete the recovery procedure > rather than creating the directory. It does no good for you to try to > recover something that will never be there. Exactly. The only thing that comes out of this patch is we support an administrative mistake that leads naive users to believe that vi recovery on reboot is going to work as expected. This is a stupid idea. I wish the person who came up with it would just acknowledge that he's doing something inappropriate and move on, rather than insisting that the rest of us introduce a bad idea into our systems to support his bad practice. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 8: 3:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id DDCEB14E8C; Fri, 14 Jan 2000 08:03:30 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id LAA51996; Fri, 14 Jan 2000 11:02:58 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200001141602.LAA51996@blackhelicopters.org> Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <7041.947863163@axl.noc.iafrica.com> from Sheldon Hearn at "Jan 14, 2000 5:19:23 pm" To: sheldonh@uunet.co.za (Sheldon Hearn) Date: Fri, 14 Jan 2000 11:02:58 -0500 (EST) Cc: khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A *lot* of us have local administration procedures that are inappropriate elsewhere, but are proper in a local context (or are wrong, but they want or need to do anyway). My laptop, for example, has a lot of o+rw permissions in /dev, /mnt owned by mwlucas... you get the idea. I don't want to become root to mount a CD or hotsync my pilot, and my laptop isn't sitting behind a T1. Ditto for my desktop system. I'm not going to suggest to the Project that they run /dev/MAKEDEV with a nightmare umask just so I personally don't have to "chmod 666 /dev/cuaa0" after every make world. The point is that system administrators, whether on big-ass systems or little boxes, have to have local procedures to deal with local quirks. I have shell scripts to handle these changes for me. Simple shell scripts, easy-to-write shell scripts, that handle my localizations. FreeBSD's wdc driver does not support CD-Rom configured as a slave without a primary. This is because it is a violation of the IDE specs. This strikes me as more of the same. Now please, can we let this die? We all make suggestions that make people go "bleah". ==ml > On Fri, 14 Jan 2000 10:12:54 EST, Vivek Khera wrote: > > > If you don't like the warning, just delete the recovery procedure > > rather than creating the directory. It does no good for you to try to > > recover something that will never be there. > > Exactly. The only thing that comes out of this patch is we support > an administrative mistake that leads naive users to believe that vi > recovery on reboot is going to work as expected. > > This is a stupid idea. I wish the person who came up with it would just > acknowledge that he's doing something inappropriate and move on, rather > than insisting that the rest of us introduce a bad idea into our systems > to support his bad practice. > > Ciao, > Sheldon. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 8:23:27 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id EBF0115659; Fri, 14 Jan 2000 08:23:25 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id DF0A81CD5EA; Fri, 14 Jan 2000 08:23:25 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 14 Jan 2000 08:23:25 -0800 (PST) From: Kris Kennaway To: "Vladimir B. Grebeschikov" Cc: current@freebsd.org Subject: Re: ATAPI CDROM trouble In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Jan 2000, Vladimir B. Grebeschikov wrote: > while I am do 'mount_cd9660 /dev/acd0c /m/cd' > system compleatly holds, no core, no panic - hold (may be deadloop in > kernel mode ?) Does it freeze completely, or just for a long time? I see something very similar, but mine unwedges after about 1 1/2 - 2 minutes (it just seems to be spinning hard in the kernel). Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 8:44:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 6AFDD14CEE for ; Fri, 14 Jan 2000 08:44:40 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id BAA02744 for ; Sat, 15 Jan 2000 01:44:37 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp543.kt.rim.or.jp [202.247.140.193]) by mail1.rim.or.jp (3.7W/) id BAA00529 for ; Sat, 15 Jan 2000 01:44:38 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id BAA33608 for ; Sat, 15 Jan 2000 01:44:37 +0900 (JST) Date: Sat, 15 Jan 2000 01:44:37 +0900 Message-ID: <14463.21109.158402.47502X@localhost.sky.rim.or.jp> From: Jun Kuriyama To: current@FreeBSD.org Subject: NEC ohci User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My friend has Toshiba's notebook which has NEC ohci USB controller. He installed FreeBSD-current but it cannot recognize USB device attach/detach signal. If USB mouse was plugged in at boot time, ohci found ums0 device and we can use it. But after booting without plugged mouse, we have no message after plugging USB mouse. Is there people who can use USB device with this chip? ----- ohci0: irq 11 at device 11.0 on pci0 usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ----- Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 10:10:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B10E715891 for ; Fri, 14 Jan 2000 10:05:08 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id FAA06360; Sat, 15 Jan 2000 05:04:58 +1100 Date: Sat, 15 Jan 2000 05:04:53 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, John Polstra wrote: > Jason Evans wrote: > > > 2) Make a separate copy of mktemp.c to remove the internal dependency. > > I think this is the best approach -- likewise for getobjformat.c, I agree. egcs provided "mkstemp.c" to handle the problem, but this didn't work on Warner's system because he had mkstemps() in libc (mkstemp.c actually implements mkstemps()) and there is a linker bug that breaks elf static linkage (library functions can only be replaced by functions of the same size?). The "fix" was to add mkstemps() to the -current libc and not use the egcs version. Three or four subsequent "fixes" led to the current evil one. gcc has complicated things a little by moving mkstemp.c to a version of libiberty which we don't have. Reaching out to the libiberty tree is only slightly better than reaching out to the libc tree. Anyway, the main problem is yours to fix in ld :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 10:34:37 2000 Delivered-To: freebsd-current@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 91E4915B95; Fri, 14 Jan 2000 10:21:32 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id LAA09947; Fri, 14 Jan 2000 11:20:40 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001141820.LAA09947@freeway.dcfinc.com> Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: from Adrian Penisoara at "Jan 14, 0 04:51:31 pm" To: ady@warpnet.ro (Adrian Penisoara) Date: Fri, 14 Jan 2000 11:20:40 -0700 (MST) Cc: trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Adrian Penisoara wrote: > I'm not discussing the definition of /var/tmp! I just recognise that > lots of people (including me) step over this rule (as they don't need > those bits to survive reboots, for example) and they MFS mount > /var/tmp (at least) for the sake of optimizing compile times (cc uses > /var/tmp for temporary files). Use "-pipe" in your CFLAGS. You'll get even more speed than making /var/tmp a MFS. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 10:34:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 229EB15B7E; Fri, 14 Jan 2000 10:19:44 -0800 (PST) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id NAA04478; Fri, 14 Jan 2000 13:17:52 -0500 (EST) From: Brian Hechinger Message-Id: <200001141817.NAA04478@entropy.tmok.com> Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <200001141602.LAA51996@blackhelicopters.org> from Michael Lucas at "Jan 14, 2000 11: 2:58 am" To: mwlucas@blackhelicopters.org (Michael Lucas) Date: Fri, 14 Jan 2000 13:17:52 -0500 (EST) Cc: sheldonh@uunet.co.za, khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Lucas drunkenly mumbled... > A *lot* of us have local administration procedures that are > inappropriate elsewhere, but are proper in a local context (or are > wrong, but they want or need to do anyway). i'm sorry for not letting this die, however.... while it is true that a lot of people have a lot of administration procedures that exist solely for our local setup there are sometimes better solutions than the ones we are using. for example, we'll go with this current thread. /var/tmp on MFS makes cc go faster, but breaks vi.recovery so if we look at the problem we should not be trying to change the vi recovery system, but rather cc. if making a change for ANY reason breaks something else you shouldn't fix the thing you broke, but the thing you are changing. make /var/mfs_tmp and have cc use it for it's temporary storage. if cc doesn't support that then fix cc since being able to specify where your compiler stores it's temp files is a Good Idea(TM) now cc is faster and vi.recovery isn't broken. maybe we should spend less time discussing the technical merits of an action and rather spend our time look for better solutions. -brian -- Brian Hechinger UNIX System Administrator Half.com brian@half.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 10:58:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 1FA901577B for ; Fri, 14 Jan 2000 10:53:36 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id NAA22287 for ; Fri, 14 Jan 2000 13:53:30 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA07207; Fri, 14 Jan 2000 13:53:00 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.3/8.9.1) id NAA54577 for freebsd-current@freebsd.org; Fri, 14 Jan 2000 13:53:00 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <200001141853.NAA54577@bb01f39.unx.sas.com> Subject: rlogin exited on signal 6 To: freebsd-current@freebsd.org Date: Fri, 14 Jan 2000 13:53:00 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just installed 4.0-20000112-SNAP. Everything appears to be working fine so far (no softupdates), with the exception of one bug which I started to look at and posted about 2 months ago or so... Basically, rlogin randomly exits on signal 6. From messages: Jan 14 13:28:07 magenta /kernel: pid 282 (rlogin), uid 227: exited on signal 6 Jan 14 13:46:12 magenta /kernel: pid 321 (rlogin), uid 227: exited on signal 6 I have debugged it enough to say that the bug is not in the rlogin code, but in a library routine. If no-one has any clues concerning this I guess I'll start rebuilding the libraries until I can pin-point the failure. Thanks! John -- John W. De Boskey jwd@sasDOTcom Gates' Law : Every 18 months, the size of software doubles. Gates' Corollary: Every 18 months, the speed of software halves. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 11: 6:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id E243B156F8; Fri, 14 Jan 2000 11:01:32 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id LAA29741; Fri, 14 Jan 2000 11:00:08 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200001141900.LAA29741@troutmask.apl.washington.edu> Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <200001141817.NAA04478@entropy.tmok.com> from Brian Hechinger at "Jan 14, 2000 01:17:52 pm" To: wonko@entropy.tmok.com Date: Fri, 14 Jan 2000 11:00:07 -0800 (PST) Cc: Michael Lucas , sheldonh@uunet.co.za, khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Hechinger wrote: > > /var/tmp on MFS makes cc go faster, but breaks vi.recovery > so if we look at the problem we should not be trying to change the vi recovery > system, but rather cc. if making a change for ANY reason breaks something > else you shouldn't fix the thing you broke, but the thing you are changing. > > make /var/mfs_tmp and have cc use it for it's temporary storage. if cc doesn't > support that then fix cc since being able to specify where your compiler > stores it's temp files is a Good Idea(TM) > *sigh* man gcc Either use -pipe or set the environmental variable TMPDIR. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 11:24: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 7B96114F57; Fri, 14 Jan 2000 11:23:11 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 129BYJ-000GpM-00; Fri, 14 Jan 2000 18:34:27 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #1) id 129BYJ-00045l-00; Fri, 14 Jan 2000 18:34:27 +0000 Date: Fri, 14 Jan 2000 18:34:27 +0000 From: Ben Smithurst To: Adrian Penisoara Cc: Trond Endrestol , FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot Message-ID: <20000114183427.A15678@strontium.scientia.demon.co.uk> References: <1535.947843930@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adrian Penisoara wrote: > (cc uses /var/tmp for > temporary files) so do "TMPDIR=/tmp; export TMPDIR", problem solved. (Or just use -pipe when compiling.) -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 11:31:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id B0F43151A7 for ; Fri, 14 Jan 2000 11:31:39 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id UAA24471 for ; Fri, 14 Jan 2000 20:31:37 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma024469; Fri, 14 Jan 00 20:31:37 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id UAA10107 for ; Fri, 14 Jan 2000 20:31:35 +0100 (MET) Received: (qmail 2121 invoked by uid 666); 14 Jan 2000 19:32:40 -0000 Date: Fri, 14 Jan 2000 20:32:40 +0100 From: Jos Backus To: current@freebsd.org Subject: Possible IPv6-related problem Message-ID: <20000114203240.C1626@hal.mpn.cp.philips.com> Reply-To: Jos Backus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fyi: this afternoon, after a make world, kernel build and a reboot I was seeing the following in my mail log: 2000-01-14 17:09:09.846441500 new msg 15377 2000-01-14 17:09:09.846838500 info msg 15377: bytes 277 from qp 545 uid 666 2000-01-14 17:09:09.858416500 starting delivery 27: msg 15377 to remote jbackus@ plex .nl 2000-01-14 17:09:09.858685500 status: local 0/10 remote 1/20 2000-01-14 17:09:09.868815500 delivery 27: failure: Sorry,_I_couldn't_find_any_h ost_ named_??????????O?????????gif2?._(#5.1.2)/ 2000-01-14 17:09:09.870004500 status: local 0/10 remote 0/20 2000-01-14 17:09:09.977818500 bounce msg 15377 qp 547 2000-01-14 17:09:09.978254500 end msg 15377 2000-01-14 17:09:10.093495500 new msg 15657 2000-01-14 17:09:10.093829500 info msg 15657: bytes 871 from <> qp 547 uid 106 2000-01-14 17:09:10.104767500 starting delivery 28: msg 15657 to remote Jos.Back us@n l.origin-it.com 2000-01-14 17:09:10.105033500 status: local 0/10 remote 1/20 2000-01-14 17:09:10.114447500 delivery 28: failure: Sorry,_I_couldn't_find_any_h ost_ named_??????O?????????gif1?0??,._(#5.1.2)/ 2000-01-14 17:09:10.115695500 status: local 0/10 remote 0/20 2000-01-14 17:09:10.132110500 bounce msg 15657 qp 549 2000-01-14 17:09:10.132548500 end msg 15657 The strange hostname should have been the name of our local smarthost. After taking #options INET6 #IPv6 communications protocols #options IPSEC #IP security #options IPSEC_ESP #IP security (crypto; define w/ IPSEC) #options IPSEC_IPV6FWD #IP security tunnel for IPv6 #options IPSEC_DEBUG #debug for IP security out of the kernel, the problem went away. I'm assuming this is related to the IPv6 changes because I have these additional interfaces: gif0: flags=8010 mtu 1280 gif1: flags=8010 mtu 1280 and those interface names show up in the garbage. The library call involved seems to be res_query(). Thanks, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 12:43: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 49F0014CD0; Fri, 14 Jan 2000 12:42:53 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id VAA14696; Fri, 14 Jan 2000 21:42:34 +0100 (CET) Message-ID: <20000114214234.A14486@foobar.franken.de> Date: Fri, 14 Jan 2000 21:42:34 +0100 From: Harold Gutch To: Soren Schmidt , Brian Beattie Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: UDF References: <200001140829.JAA40109@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200001140829.JAA40109@freebsd.dk>; from Soren Schmidt on Fri, Jan 14, 2000 at 09:29:58AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 14, 2000 at 09:29:58AM +0100, Soren Schmidt wrote: > It seems Brian Beattie wrote: > > I have been looking at UDF ( the filesystem used on CD-RW and DVD's ). I > > was wondering if anybody was working on it. I'm thinking about trying to > > implement it for CD-RW's and would like to avoid duplication of effort and > > the anoyance of getting half way through the effort and having somebody > > else show up with a completed implementation. > > I have it on my TODO list, but I'm not started yet, and probably wont for > some time to come. > The reason I've put it on the backburner for now, is that DVD's can > be read using the cd9660 filesystem, and that is sufficient for my > needs for the time being. I was under the impression that this was only possible as long as the DVDs actually had an ISO9660 filesystem as well - which all of my DVDs have, but which still doesn't mean that there are no DVDs with only UDF, but no ISO9660 filesystem. bye, Harold -- Someone should do a study to find out how many human life spans have been lost waiting for NT to reboot. Ken Deboy on Dec 24 1999 in comp.unix.bsd.freebsd.misc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 13: 8:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from ds.express.ru (ds.express.ru [212.24.32.7]) by hub.freebsd.org (Postfix) with ESMTP id 8D869150D8; Fri, 14 Jan 2000 13:08:14 -0800 (PST) (envelope-from vova@express.ru) Received: from lanturn.kmost.express.ru ([212.24.37.109]) by ds.express.ru with esmtp (Exim 2.12 #8) id 129Dwu-000094-00; Sat, 15 Jan 2000 00:08:00 +0300 Date: Sat, 15 Jan 2000 00:08:06 +0300 (MSK) From: "Vladimir B. Grebeschikov" X-Sender: vova@lanturn.kmost.express.ru To: Kris Kennaway Cc: current@freebsd.org Subject: Re: ATAPI CDROM trouble In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Jan 2000, Kris Kennaway wrote: > > while I am do 'mount_cd9660 /dev/acd0c /m/cd' > > system compleatly holds, no core, no panic - hold (may be deadloop in > > kernel mode ?) > > Does it freeze completely, or just for a long time? I see something very > similar, but mine unwedges after about 1 1/2 - 2 minutes (it just seems to > be spinning hard in the kernel). Yes ! after long delay it begins response to keys and after more delay it mounts CD. reading does with delay too :( do you know how to fix it ? > Kris -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 14:21:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 3D7AB150F7; Fri, 14 Jan 2000 14:20:55 -0800 (PST) (envelope-from blk@skynet.be) Received: from [194.78.236.249] (dialup1679.brussels.skynet.be [194.78.234.143]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id XAA24237; Fri, 14 Jan 2000 23:19:34 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001141900.LAA29741@troutmask.apl.washington.edu> References: <200001141900.LAA29741@troutmask.apl.washington.edu> Date: Fri, 14 Jan 2000 22:57:52 +0100 To: Steve Kargl , wonko@entropy.tmok.com From: Brad Knowles Subject: Re: Making sure /var/tmp/vi.recover exists during reboot Cc: Michael Lucas , sheldonh@uunet.co.za, khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:00 AM -0800 2000/1/14, Steve Kargl wrote: > Either use -pipe or set the environmental variable TMPDIR. Thank you. I was wondering when someone was going to mention this. Double sigh..... -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 15:15:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from piston.ecp.fr (piston.ecp.fr [138.195.33.3]) by hub.freebsd.org (Postfix) with ESMTP id 6E70614FC1 for ; Fri, 14 Jan 2000 15:15:26 -0800 (PST) (envelope-from dae@via.ecp.fr) Received: from caracal.cti.ecp.fr (caracal.cti.ecp.fr [138.195.33.4]) by piston.ecp.fr (8.8.7/jtpda-5.3) with ESMTP id AAA02576 for ; Sat, 15 Jan 2000 00:15:23 +0100 (MET) Received: from via.ecp.fr (daette.via.ecp.fr [138.195.137.130]) by caracal.cti.ecp.fr (8.8.8/jtpda-5.2) with ESMTP id AAA24036 for ; Sat, 15 Jan 2000 00:15:23 +0100 (MET) Message-ID: <387FAFCF.D91C40DC@via.ecp.fr> Date: Sat, 15 Jan 2000 00:22:55 +0100 From: Andres X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: libGGI Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I apologize if this is not the right list to post to, but i didn't know where else to do it so here goes: is anyone interested/currently working on a libGGI port ? or currently using libGGI on FreeBSD ? -- Andres. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 15:18:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id D887E14EC9 for ; Fri, 14 Jan 2000 15:18:47 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA13863 for freebsd-current@freebsd.org; Sat, 15 Jan 2000 00:04:53 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA32886 for freebsd-current@freebsd.org; Sat, 15 Jan 2000 00:07:22 +0100 (CET) (envelope-from wilko) Date: Sat, 15 Jan 2000 00:07:22 +0100 From: Wilko Bulte To: "FreeBSD_current, mailing list" Subject: buildworld fails on Alpha Message-ID: <20000115000720.A28839@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a very freshly supped -current on Alpha: ===> sys/modules ===> sys/modules/aha rm -f aha.h setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o aha.ko aha.o aha_isa.o @ machine symb.tmp tmp.o opt_cam.h opt_scsi.h bus_if.h device_if.h isa_if.h rm -f .depend /usr/src/sys/modules/aha/GPATH /usr/src/sys/modules/aha/GRTAGS /usr/src/sys/modules/aha/GSYMS /usr/src/sys/modules/aha/GTAGS ===> sys/modules/amr rm -f setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o amr.ko amr.o amr_pci.o amr_disk.o @ machine symb.tmp tmp.o bus_if.h device_if.h pci_if.h rm -f .depend /usr/src/sys/modules/amr/GPATH /usr/src/sys/modules/amr/GRTAGS /usr/src/sys/modules/amr/GSYMS /usr/src/sys/modules/amr/GTAGS ===> sys/modules/an cd: can't cd to /usr/src/sys/modules/an *** Error code 2 Stop in /usr/src/sys/modules. *** Error code 1 -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 15:19:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 9B8981567B for ; Fri, 14 Jan 2000 15:19:04 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA13869; Sat, 15 Jan 2000 00:04:56 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA02498; Fri, 14 Jan 2000 23:31:23 +0100 (CET) (envelope-from wilko) Date: Fri, 14 Jan 2000 23:31:23 +0100 From: Wilko Bulte To: Jason Evans Cc: current@freebsd.org Subject: Re: Make world breakage... Message-ID: <20000114233123.A2475@yedi.iaf.nl> References: <200001121956.e0CJuNw65075@gratis.grondar.za> <20000112220725.A2942@yedi.iaf.nl> <20000112132225.T302@sturm.canonware.com> <20000113001631.C4148@yedi.iaf.nl> <20000112172522.A21639@dragon.nuxi.com> <20000113083024.A50096@yedi.iaf.nl> <20000113203515.A1321@yedi.iaf.nl> <20000113140014.M302@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000113140014.M302@sturm.canonware.com>; from jasone@canonware.com on Thu, Jan 13, 2000 at 02:00:14PM -0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 02:00:14PM -0800, Jason Evans wrote: > On Thu, Jan 13, 2000 at 08:35:16PM +0100, Wilko Bulte wrote: > > I resurrected things by grabbing an 'old' .4 library from another Alpha. > > Now things work again. > > In case you missed it, I checked in a probable fix for the bug that got you > last time around. You might try again now. Thanks, I just started a buildworld on the Alpha with the latest cvsupped bits. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 15:22:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 8631D15504 for ; Fri, 14 Jan 2000 15:22:31 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 0B1929B6A; Fri, 14 Jan 2000 18:22:21 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 02855BA0C; Fri, 14 Jan 2000 18:22:20 -0500 (EST) Date: Fri, 14 Jan 2000 18:22:20 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Andres Cc: current@freebsd.org Subject: Re: libGGI In-Reply-To: <387FAFCF.D91C40DC@via.ecp.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000, Andres wrote: > hi, > > I apologize if this is not the right list to post to, but i didn't know > where else to do it so here goes: > is anyone interested/currently working on a libGGI port ? or currently > using libGGI on FreeBSD ? > Actually the correct list would be freebsd-ports@FreeBSD.org since you are wanting to port an application...and see http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15938 for a recent port submission for libggi. ----- 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-current" in the body of the message From owner-freebsd-current Fri Jan 14 15:32:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from anaconda.lovett.com (anaconda.lovett.com [216.60.121.168]) by hub.freebsd.org (Postfix) with ESMTP id B688C14D30; Fri, 14 Jan 2000 15:32:08 -0800 (PST) (envelope-from ade@lovett.com) Received: from ade by anaconda.lovett.com with local (Exim 3.12 #1) id 129GBw-000OzL-00; Fri, 14 Jan 2000 17:31:40 -0600 Date: Fri, 14 Jan 2000 17:31:40 -0600 From: Ade Lovett To: Andres Cc: current@FreeBSD.org, ports@FreeBSD.org Subject: Re: libGGI Message-ID: <20000114173140.F28891@lovett.com> Reply-To: ports@FreeBSD.org References: <387FAFCF.D91C40DC@via.ecp.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <387FAFCF.D91C40DC@via.ecp.fr>; from dae@via.ecp.fr on Sat, Jan 15, 2000 at 12:22:55AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 15, 2000 at 12:22:55AM +0100, Andres wrote: > > I apologize if this is not the right list to post to, but i didn't know > where else to do it so here goes: ports@FreeBSD.org would be your best bet. Followups redirected. > is anyone interested/currently working on a libGGI port ? or currently > using libGGI on FreeBSD ? There's one in the queue at: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15936 (libgii) http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15938 (libggi) from the http://www.ggi-project.org/ people. Both of these will need a little tweaking before they get committed (they install .la libtool turds which can be got rid of easily enough) but may do what you want. Knowing absolutely nothing about GGI, I wouldn't presume to comment any further. -aDe -- Ade Lovett, Austin, TX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 15:35:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id F0FEB156F1; Fri, 14 Jan 2000 15:34:48 -0800 (PST) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id SAA07115; Fri, 14 Jan 2000 18:36:19 -0500 (EST) From: Brian Hechinger Message-Id: <200001142336.SAA07115@entropy.tmok.com> Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <200001141900.LAA29741@troutmask.apl.washington.edu> from Steve Kargl at "Jan 14, 2000 11: 0: 7 am" To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Fri, 14 Jan 2000 18:36:19 -0500 (EST) Cc: mwlucas@blackhelicopters.org, sheldonh@uunet.co.za, khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl drunkenly mumbled... > > *sigh* > > man gcc > > Either use -pipe or set the environmental variable TMPDIR. ok, maybe i didn't say that right. this i know, i was trying to use gcc and vi.recovery as examples. but then my question is... why didn't you speak up earlier and save us all from this thread? -me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 15:48:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id B964814D19 for ; Fri, 14 Jan 2000 15:48:36 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA28490; Fri, 14 Jan 2000 18:52:34 -0500 From: Bill Paul Message-Id: <200001142352.SAA28490@skynet.ctr.columbia.edu> Subject: Re: buildworld fails on Alpha To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Fri, 14 Jan 2000 18:52:33 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <20000115000720.A28839@yedi.iaf.nl> from "Wilko Bulte" at Jan 15, 2000 00:07:22 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1733 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Wilko Bulte had to walk into mine and say: > On a very freshly supped -current on Alpha: > > ===> sys/modules > ===> sys/modules/aha > rm -f aha.h setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o aha.ko aha.o > aha_isa.o @ machine symb.tmp tmp.o opt_cam.h opt_scsi.h bus_if.h device_if.h > isa_if.h > rm -f .depend /usr/src/sys/modules/aha/GPATH /usr/src/sys/modules/aha/GRTAGS > /usr/src/sys/modules/aha/GSYMS /usr/src/sys/modules/aha/GTAGS > ===> sys/modules/amr > rm -f setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o amr.ko amr.o > amr_pci.o amr_disk.o @ machine symb.tmp tmp.o bus_if.h device_if.h pci_if.h > rm -f .depend /usr/src/sys/modules/amr/GPATH /usr/src/sys/modules/amr/GRTAGS > /usr/src/sys/modules/amr/GSYMS /usr/src/sys/modules/amr/GTAGS > ===> sys/modules/an > cd: can't cd to /usr/src/sys/modules/an > *** Error code 2 > > Stop in /usr/src/sys/modules. > *** Error code 1 Roar. I swear I checked in this module Makefile. Honest and for true. Okay, I think I've really got it this time. Please try cvsupping again: you should get a src/sys/modules/an/Makefile for compiling the Aironet driver module. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 16:14:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id E31F014EA0 for ; Fri, 14 Jan 2000 16:14:44 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA02899; Fri, 14 Jan 2000 16:22:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001150022.QAA02899@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jun Kuriyama Cc: current@FreeBSD.org Subject: Re: NEC ohci In-reply-to: Your message of "Sat, 15 Jan 2000 01:44:37 +0900." <14463.21109.158402.47502X@localhost.sky.rim.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jan 2000 16:22:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You need usbd running; see /etc/rc.conf > My friend has Toshiba's notebook which has NEC ohci USB controller. > He installed FreeBSD-current but it cannot recognize USB device > attach/detach signal. > > If USB mouse was plugged in at boot time, ohci found ums0 device and > we can use it. But after booting without plugged mouse, we have no > message after plugging USB mouse. > > Is there people who can use USB device with this chip? > > ----- > ohci0: irq 11 at device 11.0 on pci0 > usb0: OHCI version 1.0 > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > ----- > > > Jun Kuriyama // kuriyama@sky.rim.or.jp > // kuriyama@FreeBSD.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 17:23:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from soolin.barclayscapital.com (avon2.barclayscapital.com [141.228.4.193]) by hub.freebsd.org (Postfix) with SMTP id AA1B714CA4 for ; Fri, 14 Jan 2000 17:23:24 -0800 (PST) (envelope-from Pierre.Dampure@barclayscapital.com) Received: from jfsebastian.ldn.bzwint.com by soolin.barclayscapital.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 15 Jan 2000 01:23:40 UT Received: from jfsebastian (localhost [127.0.0.1]) by jfsebastian.ldn.bzwint.com (8.9.3+Sun/8.9.3) with SMTP id BAA03509 for ; Sat, 15 Jan 2000 01:24:24 GMT From: "Pierre Y. Dampure" To: Subject: Changed cpp behaviour breaks lint Date: Sat, 15 Jan 2000 01:24:18 -0000 Message-ID: <01bf5ef7$3e9be380$c0a84202@jfsebastian.ldn.bzwint.com> 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 Unix 5.00.2013.1312 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2013.1312 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The build is currently broken is /usr/src/usr.bin/xlint/llib, becasue lint invokes ccp with the -undef option, which does not seem to be supported anymore... any clues? PYD@home To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 17:34:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id C962F14D9A for ; Fri, 14 Jan 2000 17:34:09 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id RAA15542; Fri, 14 Jan 2000 17:32:59 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id RAA29114; Fri, 14 Jan 2000 17:32:59 -0800 Received: from softweyr.com (dyn1.utah.xylan.com [198.206.184.237]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id RAA21522; Fri, 14 Jan 2000 17:31:41 -0800 (PST) Message-ID: <387FCF2D.94FF05CD@softweyr.com> Date: Fri, 14 Jan 2000 18:36:45 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Bill Paul Cc: Wilko Bulte , freebsd-current@freebsd.org Subject: Re: buildworld fails on Alpha References: <200001142352.SAA28490@skynet.ctr.columbia.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul testified after hours of torture: > > Of all the gin joints in all the towns in all the world, Wilko Bulte had > to walk into mine and say: > > > On a very freshly supped -current on Alpha: > > > > ===> sys/modules/an > > cd: can't cd to /usr/src/sys/modules/an > > *** Error code 2 > > > > Stop in /usr/src/sys/modules. > > *** Error code 1 > > Roar. I swear I checked in this module Makefile. Honest and for true. OK, who's running the "eat Bills commits" daemon this time? I thought we agreed we weren't going to start that back up until *after* 4.0 RELEASE? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 17:44:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from soolin.barclayscapital.com (avon2.barclayscapital.com [141.228.4.193]) by hub.freebsd.org (Postfix) with SMTP id 07C8B1516B for ; Fri, 14 Jan 2000 17:44:38 -0800 (PST) (envelope-from Pierre.Dampure@barclayscapital.com) Received: from jfsebastian.ldn.bzwint.com by soolin.barclayscapital.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 15 Jan 2000 01:44:52 UT Received: from jfsebastian (localhost [127.0.0.1]) by jfsebastian.ldn.bzwint.com (8.9.3+Sun/8.9.3) with SMTP id BAA03514 for ; Sat, 15 Jan 2000 01:45:42 GMT From: "Pierre Y. Dampure" To: Subject: make world breaks in /usr/src/usr.bin/xlint Date: Sat, 15 Jan 2000 01:45:37 -0000 Message-ID: <01bf5efa$385b3680$c0a84202@jfsebastian.ldn.bzwint.com> 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 Unix 5.00.2013.1312 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2013.1312 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if my previous message wasn't clear: the change of behaviour in cpp breaks lint, hence the build. FWIW, Mr. K posted a message on the 13th which already outlined the problem with lint -- no answers so far. -----Original Message----- From: Pierre Y. Dampure To: current@FreeBSD.ORG Date: Saturday, January 15, 2000 1:23 AM Subject: Changed cpp behaviour breaks lint >The build is currently broken is /usr/src/usr.bin/xlint/llib, becasue lint >invokes ccp with the -undef option, which does not seem to be supported >anymore... any clues? > >PYD@home > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 18:31:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id BED5914E9D for ; Fri, 14 Jan 2000 18:31:22 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA04852 for ; Fri, 14 Jan 2000 18:38:44 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001150238.SAA04852@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: New softupdates panic Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jan 2000 18:38:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Uniprocessor kernel, checking out /sys from an NFS-mounted repository, kernel built from sources current as of this afternoon. (apologies for any typos, no serial console) panic: initate_write_inodeblock: already started ... panic() initiate_write_inodeblock() softdep_disk_io_initiation() spec_stratety() bwrite() vop_stdbwrite() vop_defaultop() vfs_bio_awrite() spec_fsync() sched_sync() fork_trampoline() -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 18:41:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from geocities.com (mail8.geocities.com [209.1.224.42]) by hub.freebsd.org (Postfix) with ESMTP id D77D814D0A for ; Fri, 14 Jan 2000 18:41:07 -0800 (PST) (envelope-from arnee@geocities.com) Received: from geocities.com (mg130-101.ricochet.net [204.179.130.101]) by geocities.com (8.9.3/8.9.3) with ESMTP id SAA21237 for ; Fri, 14 Jan 2000 18:41:26 -0800 (PST) Message-ID: <387FDF2D.575DC537@geocities.com> Date: Fri, 14 Jan 2000 18:45:01 -0800 From: arnee X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: current@FreeBSD.org Subject: NFS and Samba (file transfer crashes system) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Not sure if this is the right place to report this. My system (server) crashes when i transfer files FROM a client (unix and win9x). The error seems to be random because i can sometimes transfer a whole directory that is more than 50mgs or so and sometimes i can't even transfer anything less than 15mgs. System: pcchips m571 with cyrix 6x86 promise ultra66 Anyone interested in more info let me know. Plus, is this kind of thread encourage in this list? I'm simply wondering if this would help, otherwise i could just follow cvs and hope things will work. arnee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 20:10:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from snowy.org (snowy.org [203.37.251.14]) by hub.freebsd.org (Postfix) with ESMTP id 0324E14E02 for ; Fri, 14 Jan 2000 20:10:48 -0800 (PST) (envelope-from snowy@snowy.org) Received: from localhost (snowy@localhost) by snowy.org (8.9.3/8.9.3) with ESMTP id OAA43217 for ; Sat, 15 Jan 2000 14:09:03 +1000 (EST) (envelope-from snowy@snowy.org) Date: Sat, 15 Jan 2000 14:09:03 +1000 (EST) From: Sleepless in Brisbane To: current@FreeBSD.ORG Subject: Problems with ATA Driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Tried out the new ATAPI driver last night with a CVS from a couple of days ago. All detected ok on boot but then I got a message roughly like: timeout waiting for command and then I get: ata0: resetting devices .. The system completely hung solid then. Firstly a question. Is there anyway of getting the log of what happens on booting before you actually get to starting init? (I'm assuming only via some sort of serial console to another PC?) Next I have 4 hardrives and a CDROM in this - I disconnected the cdrom, and also took out a Promise FASTTRAK66 controller which had 2 harddrives in it - so I am using only a single controller on an ASUS MEW board which has an i810-DC100 chipset in it. The hard-drives are Western Digital 18Gb 7200rpm. So the problem has something to do with the motherboard and/or drives - BIOS for the motherboard is at rev1.0006 - the latest. The machine works flawlessly with the old wd driver - so what are the main differences between the old wd and the new ATA stuff - and is there a compatiblity mode in the new ATAPI driver I can set for specific interfaces? Relevent SNIP from config-file is as follows: # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata2 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives #device atapifd0 # ATAPI floppy drives #device atapist0 # ATAPI tape drives options ATA_STATIC_ID #Static device numbering -- PGP Fingerprint16 = D4 D9 ED B4 5F 07 70 36 14 E2 02 01 DE 19 69 52 ------- S Maslov a.k.a. Sleepless in Brisbane ----- snowy@snowy.org ------ Involved with the | Fujitsu Australia (www.fujitsu.com.au) following Organisations | Webwise Solutions (info@webwise.net) -------------------------------------------------------------------------- Any material detailed in this meessage has not been endorsed by the companies mentioned above unless explicityly noted otherwise. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 20:27:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx3.mail.ru (mx3.mail.ru [194.67.23.37]) by hub.freebsd.org (Postfix) with ESMTP id 3F62314CE0; Fri, 14 Jan 2000 20:27:45 -0800 (PST) (envelope-from kabaev@mail.ru) Received: from h0050da20495b.ne.mediaone.net ([24.147.104.88] helo=kan.ne.mediaone.net) by mx3.mail.ru with esmtp (Exim 3.02 #114) id 129KmJ-000GnR-00; Sat, 15 Jan 2000 07:25:31 +0300 Received: (from kan@localhost) by kan.ne.mediaone.net (8.9.3/8.9.3) id XAA01130; Fri, 14 Jan 2000 23:27:30 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 14 Jan 2000 23:27:30 -0500 (EST) From: "Alexander N. Kabaev" To: "Alexander N. Kabaev" , obrien@FreeBSD.ORG Subject: Re: C++ exceptions doesn't work in shared libraries Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As promised, I tried to look into the problem little futher. The following patch fixes all crashes for me and I was unable to reproduce the bug anymore. I would really like to hear if it works for you too. I am especially interested to know if it works on Alpha, because I cannot test it myself. PS. The code in question is in mashine independent, so I have reason to believe that this patch may fix the problem for other platforms too... Index: contrib/gcc/except.c =================================================================== RCS file: /home/ncvs/src/contrib/gcc/except.c,v retrieving revision 1.1.1.2 diff -u -r1.1.1.2 except.c --- contrib/gcc/except.c 1999/10/16 06:03:55 1.1.1.2 +++ contrib/gcc/except.c 2000/01/15 04:06:03 @@ -724,9 +724,11 @@ rtx handler_label; { emit_label (handler_label); - + #ifdef HAVE_exception_receiver +#ifdef DONT_USE_BUILTIN_SETJMP if (! exceptions_via_longjmp) +#endif if (HAVE_exception_receiver) emit_insn (gen_exception_receiver ()); #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 21:16: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from goofy.zort.on.ca (cr575310-a.shprd1.on.wave.home.com [24.112.185.167]) by hub.freebsd.org (Postfix) with ESMTP id F242114CE0 for ; Fri, 14 Jan 2000 21:16:06 -0800 (PST) (envelope-from rod@zort.on.ca) Received: from rbtBSD.intranet (rbtBSD.zort.on.ca [10.0.0.50]) by goofy.zort.on.ca (Postfix) with SMTP id 0C646256 for ; Sat, 15 Jan 2000 00:17:00 -0500 (EST) From: Rod Taylor Reply-To: rod@zort.on.ca Organization: Zort To: freebsd-current@freebsd.org Subject: Thoughts... Date: Sat, 15 Jan 2000 00:05:46 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <0001150016090H.04098@rbtBSD.intranet> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ -current seemed like the best place to put this as I suspect thats what I'll be using for the various NFS & linux compat updates.] In early March I'd like to setup a system of 300 systems network booted from multiple central servers. These systems should include server mirroring (it'd be nice to have more than one active) and somekind of hoarding (for laptops and local cache). The systems will have relatively small harddrives in them (approx. 1.8gb). I want to use FreeBSD on both the workstations (running things like KDE v2, Star Office for it's MSOffice compatibilities, various electronics ports, and some of the programming basics). Only thing I'm really missing is a replacement for windows Matlab. Machines all have ne2k nics with eproms on them. I'd like to mount most filesystems with CODA due to it's advantages. I notice theres no way to mount a CODA filesystem for /. Should I use NFS then (which relies upon the network being up) or is there an easy method to create an image on the disk? Perhaps a pre-configured install disk would due? (If machine broken, insert disk, wait 10 minutes till it says install is done and reboot?), Any thoughts on this are welcome. The system doesn't need to be installed until March, but I'm forming a proposal which I'll submit in the middle of next week. Thanks, Rod Taylor -- Rod Taylor Partner of Zort (zort.on.ca) -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 21:27:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 00DDC14E3F for ; Fri, 14 Jan 2000 21:27:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA95920; Fri, 14 Jan 2000 21:24:44 -0800 (PST) (envelope-from dillon) Date: Fri, 14 Jan 2000 21:24:44 -0800 (PST) From: Matthew Dillon Message-Id: <200001150524.VAA95920@apollo.backplane.com> To: Rod Taylor Cc: freebsd-current@FreeBSD.ORG Subject: Re: Thoughts... References: <0001150016090H.04098@rbtBSD.intranet> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :[ -current seemed like the best place to put this as I suspect thats what I'll :be using for the various NFS & linux compat updates.] : :In early March I'd like to setup a system of 300 systems network booted from :multiple central servers. These systems should include server mirroring (it'd :be nice to have more than one active) and somekind of hoarding (for laptops and :local cache). : :The systems will have relatively small harddrives in them (approx. 1.8gb). : :I want to use FreeBSD on both the workstations (running things like KDE v2, :Star Office for it's MSOffice compatibilities, various electronics ports, and :some of the programming basics). Only thing I'm really missing is a :replacement for windows Matlab. : :Machines all have ne2k nics with eproms on them. I'd like to mount most :filesystems with CODA due to it's advantages. I notice theres no way to mount :a CODA filesystem for /. : :Should I use NFS then (which relies upon the network being up) or is there an :easy method to create an image on the disk? Perhaps a pre-configured install :disk would due? (If machine broken, insert disk, wait 10 minutes till it says :install is done and reboot?), : :Any thoughts on this are welcome. The system doesn't need to be installed :until March, but I'm forming a proposal which I'll submit in the middle of next :week. : :Thanks, : Rod Taylor : :-- :Rod Taylor :Partner of Zort (zort.on.ca) I'm not sure I would consider CODA to be a production filesystem, at least not on that scale. The author might disagree with me. Generally speaking if you limit the functionality of the servers, it should be possible to depend on them being up. You have to consider the network-disconnect case: Will CODA really result in the clients still being useable or is it a pipedream for the type of work being done on them? If the network-disconnect case would cause too much trouble, then using CODA will not give you any advantages. In terms of disk space and NFS -- you have to decide what you want to put on those 1.8GB drives. E.G. do you use them just for swap? Do you put a minimal system on them (potentially synchronized via NFS?), is security an issue (a reason for booting entirely via read-only NFS mounts for / and /usr), and so forth. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 21:29:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 343C21501E for ; Fri, 14 Jan 2000 21:29:52 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA95955; Fri, 14 Jan 2000 21:28:33 -0800 (PST) (envelope-from dillon) Date: Fri, 14 Jan 2000 21:28:33 -0800 (PST) From: Matthew Dillon Message-Id: <200001150528.VAA95955@apollo.backplane.com> To: arnee Cc: current@FreeBSD.ORG Subject: Re: NFS and Samba (file transfer crashes system) References: <387FDF2D.575DC537@geocities.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hello, : :Not sure if this is the right place to report this. My system (server) :crashes when i transfer files FROM a client (unix and win9x). The error :seems to be random because i can sometimes transfer a whole directory :that is more than 50mgs or so and sometimes i can't even transfer :anything less than 15mgs. : :System: : :pcchips m571 with cyrix 6x86 :promise ultra66 : :Anyone interested in more info let me know. Plus, is this kind of thread :encourage in this list? I'm simply wondering if this would help, :otherwise i could just follow cvs and hope things will work. : :arnee Well, you haven't given very much information. What FreeBSD OS release (or, if current, when did you last sync your source tree)? If you are running an older release the very first thing you need to do is upgrade to the latest -stable or -current depending on which tree you are using. You haven't described very well exactly what the situation is... you talk of NFS and Samba but you do not say which one the transfer is going over. If the machine still crashes then we need to know what the panic message is. It may be useful to configure a kernel with DDB enabled to cause it to drop into DDB on a crash (this assuming you aren't running X on the machine, since DDB only runs on the console). In that case you should be able to obtain the panic message and do a 'trace' to get more detailed information on where the box is crashing. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 21:41:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from goofy.zort.on.ca (cr575310-a.shprd1.on.wave.home.com [24.112.185.167]) by hub.freebsd.org (Postfix) with ESMTP id 50F8614FA9 for ; Fri, 14 Jan 2000 21:41:16 -0800 (PST) (envelope-from rod@zort.on.ca) Received: from rbtBSD.intranet (rbtBSD.zort.on.ca [10.0.0.50]) by goofy.zort.on.ca (Postfix) with SMTP id 69265256; Sat, 15 Jan 2000 00:42:09 -0500 (EST) From: Rod Taylor Reply-To: rod@zort.on.ca Organization: Zort To: Matthew Dillon , freebsd-current@freebsd.org Subject: Re: Thoughts... Date: Sat, 15 Jan 2000 00:34:26 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <0001150016090H.04098@rbtBSD.intranet> <200001150524.VAA95920@apollo.backplane.com> In-Reply-To: <200001150524.VAA95920@apollo.backplane.com> MIME-Version: 1.0 Message-Id: <0001150041180I.04098@rbtBSD.intranet> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The main reason for choosing Coda was inteed On Sat, 15 Jan 2000, you wrote: > :[ -current seemed like the best place to put this as I suspect thats what I'll > :be using for the various NFS & linux compat updates.] > Generally speaking if you limit the functionality of the servers, > it should be possible to depend on them being up. I've not used NFS heavily in -current. Sounds like a lot of work has been put into it. > You have to consider the network-disconnect case: Will CODA really > result in the clients still being useable or is it a pipedream for > the type of work being done on them? If the network-disconnect case > would cause too much trouble, then using CODA will not give you any > advantages. Hmm.. My main thoughts for this was the hoarding issue. As the school would like to allow students to 'link up' via laptops and have them synchronized via the same mechanism. Their current solution is to copy a 1.8GB disk image across the network onto the drives and use that as a normal local disk. The copy time takes several minutes. If for some reason 50 people decided to do this at the same time you could see where some network lag would come from. The other reason has to do with the laggy network and booting off it. The things not even 10MB switched per station. 8 workstations share 10mbit hubs. Netscape for example would take ages to load over NFS that way. (Afterall, in a class like that they tend to do everything in unison). Mounting / under NFS on the other hand doesn't appear that it would be trouble. It's /usr/local/bin that could use a little local caching. > In terms of disk space and NFS -- you have to decide what you want to > put on those 1.8GB drives. E.G. do you use them just for swap? Do > you put a minimal system on them (potentially synchronized via NFS?), > is security an issue (a reason for booting entirely via read-only NFS > mounts for / and /usr), and so forth. -- Rod Taylor Partner of Zort (zort.on.ca) -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 21:52:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A2BD714F09; Fri, 14 Jan 2000 21:52:09 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA95996; Fri, 14 Jan 2000 21:33:31 -0800 (PST) (envelope-from dillon) Date: Fri, 14 Jan 2000 21:33:31 -0800 (PST) From: Matthew Dillon Message-Id: <200001150533.VAA95996@apollo.backplane.com> To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: New softupdates panic References: <200001150238.SAA04852@mass.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Uniprocessor kernel, checking out /sys from an NFS-mounted repository, :kernel built from sources current as of this afternoon. :(apologies for any typos, no serial console) : :panic: initate_write_inodeblock: already started Checking out from an NFS mounted repository into a local filesystem w/ softupdates enabled? ... :panic() :initiate_write_inodeblock() :softdep_disk_io_initiation() :spec_stratety() :bwrite() :vop_stdbwrite() :vop_defaultop() :vfs_bio_awrite() :spec_fsync() :sched_sync() :fork_trampoline() This is definitely new, I've never seen this one before. I'll try to reproduce it on monday when I get back to Berkeley. In the mean time, please see if you can reproduce the panic. If we can get the panic reproducable then I can reproduce it on my test box and handle all the crash dump nicities to hand over to Kirk. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 22: 0: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6680214EEC for ; Fri, 14 Jan 2000 21:59:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA96077; Fri, 14 Jan 2000 21:55:59 -0800 (PST) (envelope-from dillon) Date: Fri, 14 Jan 2000 21:55:59 -0800 (PST) From: Matthew Dillon Message-Id: <200001150555.VAA96077@apollo.backplane.com> To: Rod Taylor Cc: freebsd-current@FreeBSD.ORG Subject: Re: Thoughts... References: <0001150016090H.04098@rbtBSD.intranet> <200001150524.VAA95920@apollo.backplane.com> <0001150041180I.04098@rbtBSD.intranet> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hmm.. My main thoughts for this was the hoarding issue. As the school would :like to allow students to 'link up' via laptops and have them synchronized via :the same mechanism. : :Their current solution is to copy a 1.8GB disk image across the network onto :the drives and use that as a normal local disk. The copy time takes several :minutes. If for some reason 50 people decided to do this at the same time you :could see where some network lag would come from. There are lots of ways of syncing up that do not require sending the entire image over the network every time. Syncing is something you could do with an NFS mount quite easily, combined with something like cpdup (see /usr/ports/sysutils/cpdup). This way the user maintains everything on their local HD, and syncs-up when convenient. You can do this with or without a network boot. It may be more convienient to do a network-boot to handle the case where the client's disk is totally munged and can't even boot itself. Alternatively you could network boot the kernel and the initial startup and then switch over to the local disk for the bulk of it (once you've determined that the local disk is reasonable), but that would mean the client cannot boot on its own without the network. Or you could provide a 'recovery' floppy that does the network boot and if the floppy isn't in the client it boots from its local HD. :The other reason has to do with the laggy network and booting off it. The :things not even 10MB switched per station. 8 workstations share 10mbit hubs. :Netscape for example would take ages to load over NFS that way. (Afterall, in :a class like that they tend to do everything in unison). : :Mounting / under NFS on the other hand doesn't appear that it would be trouble. :It's /usr/local/bin that could use a little local caching. :... :Rod Taylor :Partner of Zort (zort.on.ca) :-- Using NFS for /, /usr, and /usr/local/bin over a slow 10BaseT network being shared with many other clients is going to depend heavily on the amount of memory the laptops have. NFS is very good at caching binaries on the client if the client has sufficient memory. If the client does not have sufficient memory then every time you run a binary it will have to load it from the server. The NFS server will need enough memory to cache lots of vnodes in order to be able to handle synchronizing scans without eating its disk alive. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 22: 2:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from goofy.zort.on.ca (cr575310-a.shprd1.on.wave.home.com [24.112.185.167]) by hub.freebsd.org (Postfix) with ESMTP id 8912A14CB3 for ; Fri, 14 Jan 2000 22:02:37 -0800 (PST) (envelope-from rod@zort.on.ca) Received: from rbtBSD.intranet (rbtBSD.zort.on.ca [10.0.0.50]) by goofy.zort.on.ca (Postfix) with SMTP id 89EB4218; Sat, 15 Jan 2000 01:01:44 -0500 (EST) From: Rod Taylor Reply-To: rod@zort.on.ca Organization: Zort To: Matthew Dillon , freebsd-current@freebsd.org Subject: Re: Thoughts... Date: Sat, 15 Jan 2000 00:59:16 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <0001150016090H.04098@rbtBSD.intranet> <0001150041180I.04098@rbtBSD.intranet> <200001150555.VAA96077@apollo.backplane.com> In-Reply-To: <200001150555.VAA96077@apollo.backplane.com> MIME-Version: 1.0 Message-Id: <0001150100540J.04098@rbtBSD.intranet> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok... You've mostly convinced me. On Monday I'll pick up a few boxes and test them out. Thanks for your information... On Sat, 15 Jan 2000, you wrote: > :Their current solution is to copy a 1.8GB disk image across the network onto > :the drives and use that as a normal local disk. The copy time takes several > :minutes. If for some reason 50 people decided to do this at the same time you > :could see where some network lag would come from. > > There are lots of ways of syncing up that do not require sending the > entire image over the network every time. Syncing is something you could > do with an NFS mount quite easily, combined with something like cpdup > (see /usr/ports/sysutils/cpdup). > :The other reason has to do with the laggy network and booting off it. The > :things not even 10MB switched per station. 8 workstations share 10mbit hubs. > :Netscape for example would take ages to load over NFS that way. (Afterall, in > :a class like that they tend to do everything in unison). > : > :Mounting / under NFS on the other hand doesn't appear that it would be trouble. > :It's /usr/local/bin that could use a little local caching. > > Using NFS for /, /usr, and /usr/local/bin over a slow 10BaseT network > being shared with many other clients is going to depend heavily on the > amount of memory the laptops have. NFS is very good at caching binaries > on the client if the client has sufficient memory. If the client does not > have sufficient memory then every time you run a binary it will have > to load it from the server. > > The NFS server will need enough memory to cache lots of vnodes in order > to be able to handle synchronizing scans without eating its disk alive. > -- Rod Taylor Partner of Zort (zort.on.ca) -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 22:16:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 15F2715027 for ; Fri, 14 Jan 2000 22:16:22 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id PAA18249; Sat, 15 Jan 2000 15:13:55 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp527.kt.rim.or.jp [202.247.140.177]) by mail1.rim.or.jp (3.7W/) id PAA13764; Sat, 15 Jan 2000 15:13:56 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id PAA39814; Sat, 15 Jan 2000 15:13:55 +0900 (JST) Date: Sat, 15 Jan 2000 15:13:54 +0900 Message-ID: <14464.4130.424957.81174H@localhost.sky.rim.or.jp> From: Jun Kuriyama To: wpaul@skynet.ctr.columbia.edu Cc: current@FreeBSD.org Subject: Re: panic in uipc_mbuf.c or if_aue.c In-Reply-To: In your message of "Thu, 13 Jan 2000 15:29:43 -0500 (EST)" <200001132029.PAA26129@skynet.ctr.columbia.edu> References: <14461.62128.675464.13362J@localhost.sky.rim.or.jp> <200001132029.PAA26129@skynet.ctr.columbia.edu> User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Bill Paul > Please try updating /sys/dev/usb with the latest code from today. I > added some changes both today and yesterday to avoid touching mbufs > at splbio/splusb. I also fixed the aue driver to work with the LinkSys > USB100TX. I've updated to v1.11 of if_aue.c and tested with heavy traffic for few hours. But I cannot see any panics. It seems fine. Thanks! Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 22:33:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat200.60.mpoweredpc.net [142.177.200.60]) by hub.freebsd.org (Postfix) with ESMTP id A664A156E9 for ; Fri, 14 Jan 2000 22:33:41 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id CAA93380; Sat, 15 Jan 2000 02:29:08 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 15 Jan 2000 02:29:08 -0400 (AST) From: The Hermit Hacker To: Matthew Dillon Cc: Rod Taylor , freebsd-current@FreeBSD.ORG Subject: Re: Thoughts... In-Reply-To: <200001150555.VAA96077@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Jan 2000, Matthew Dillon wrote: > > :Hmm.. My main thoughts for this was the hoarding issue. As the school would > :like to allow students to 'link up' via laptops and have them synchronized via > :the same mechanism. > : > :Their current solution is to copy a 1.8GB disk image across the network onto > :the drives and use that as a normal local disk. The copy time takes several > :minutes. If for some reason 50 people decided to do this at the same time you > :could see where some network lag would come from. > > There are lots of ways of syncing up that do not require sending the > entire image over the network every time. Syncing is something you could > do with an NFS mount quite easily, combined with something like cpdup > (see /usr/ports/sysutils/cpdup). we use rdist on our network to keep our production servers in sync...we tend to avoid 'nfs traffic' as much as possible... 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-current" in the body of the message From owner-freebsd-current Fri Jan 14 22:37:12 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id E8CBC14F5E; Fri, 14 Jan 2000 22:37:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E08941CD5E7; Fri, 14 Jan 2000 22:37:10 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 14 Jan 2000 22:37:10 -0800 (PST) From: Kris Kennaway To: "Vladimir B. Grebeschikov" Cc: current@freebsd.org Subject: Re: ATAPI CDROM trouble In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000, Vladimir B. Grebeschikov wrote: > > Does it freeze completely, or just for a long time? I see something very > > similar, but mine unwedges after about 1 1/2 - 2 minutes (it just seems to > > be spinning hard in the kernel). > > Yes ! after long delay it begins response to keys and after more delay it > mounts CD. reading does with delay too :( > > do you know how to fix it ? No, but sos is working on it. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 14 23:16:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 6BDFB15288 for ; Fri, 14 Jan 2000 23:16:17 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id CAA10595; Sat, 15 Jan 2000 02:11:53 -0500 (EST) (envelope-from efutch@nyct.net) Date: Sat, 15 Jan 2000 02:11:53 -0500 (EST) From: "Eric D. Futch" To: The Hermit Hacker Cc: Matthew Dillon , Rod Taylor , freebsd-current@FreeBSD.ORG Subject: Re: Thoughts... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just thinking of something, I don't know how feasible it is. Couldn't you setup a CVS repository with all the files you need. You could even have it keep track of different sets of files for each class/course right? Kinda like how FreeBSD keeps track of -stable and -current seperately. When they plug in, just have it to cvsup and fetch the most recent material for this class. It might be a little more complicated this way though. Just an idea... -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Sat, 15 Jan 2000, The Hermit Hacker wrote: On Fri, 14 Jan 2000, Matthew Dillon wrote: > > :Hmm.. My main thoughts for this was the hoarding issue. As the school would > :like to allow students to 'link up' via laptops and have them synchronized via > :the same mechanism. > : > :Their current solution is to copy a 1.8GB disk image across the network onto > :the drives and use that as a normal local disk. The copy time takes several > :minutes. If for some reason 50 people decided to do this at the same time you > :could see where some network lag would come from. > > There are lots of ways of syncing up that do not require sending the > entire image over the network every time. Syncing is something you could > do with an NFS mount quite easily, combined with something like cpdup > (see /usr/ports/sysutils/cpdup). we use rdist on our network to keep our production servers in sync...we tend to avoid 'nfs traffic' as much as possible... 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-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 1: 1:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 6476014E63; Sat, 15 Jan 2000 01:01:53 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 129P5V-0004L3-00; Sat, 15 Jan 2000 11:01:37 +0200 From: Sheldon Hearn To: "Pierre Y. Dampure" Cc: current@FreeBSD.ORG, marcel@FreeBSD.org Subject: Re: make world breaks in /usr/src/usr.bin/xlint In-reply-to: Your message of "Sat, 15 Jan 2000 01:45:37 GMT." <01bf5efa$385b3680$c0a84202@jfsebastian.ldn.bzwint.com> Date: Sat, 15 Jan 2000 11:01:37 +0200 Message-ID: <16680.947926897@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000 01:45:37 GMT, "Pierre Y. Dampure" wrote: > Sorry if my previous message wasn't clear: the change of behaviour in cpp > breaks lint, hence the build. I fixed lint, so I'm surprised that world should break when lint is called. Perhaps lint needs to be added to the built-tools? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 1: 3:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 2312814E50; Sat, 15 Jan 2000 01:03:31 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 129P7D-0004LW-00; Sat, 15 Jan 2000 11:03:23 +0200 From: Sheldon Hearn To: "Pierre Y. Dampure" Cc: current@FreeBSD.ORG, marcel@FreeBSD.org Subject: Re: make world breaks in /usr/src/usr.bin/xlint In-reply-to: Your message of "Sat, 15 Jan 2000 01:45:37 GMT." <01bf5efa$385b3680$c0a84202@jfsebastian.ldn.bzwint.com> Date: Sat, 15 Jan 2000 11:03:23 +0200 Message-ID: <16708.947927003@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000 01:45:37 GMT, "Pierre Y. Dampure" wrote: > Sorry if my previous message wasn't clear: the change of behaviour in > cpp breaks lint, hence the build. I forgot to mention in my previous message that I've backed out rev 1.5. Any world breakage you're experience should be fixed with rev 1.5 of src/usr.bin/xlint/Makefile Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 1: 4: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id EFE8F14D3F for ; Sat, 15 Jan 2000 01:03:55 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 129P7b-0004Lm-00; Sat, 15 Jan 2000 11:03:47 +0200 From: Sheldon Hearn To: "Pierre Y. Dampure" Cc: current@FreeBSD.ORG Subject: Re: make world breaks in /usr/src/usr.bin/xlint In-reply-to: Your message of "Sat, 15 Jan 2000 01:45:37 GMT." <01bf5efa$385b3680$c0a84202@jfsebastian.ldn.bzwint.com> Date: Sat, 15 Jan 2000 11:03:47 +0200 Message-ID: <16725.947927027@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000 01:45:37 GMT, "Pierre Y. Dampure" wrote: > Sorry if my previous message wasn't clear: the change of behaviour in cpp > breaks lint, hence the build. You weren't building with -DNOCLEAN or -DNOTOOLS, were you? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 1:20:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 65CD61503D; Sat, 15 Jan 2000 01:20:43 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA98140; Sat, 15 Jan 2000 10:20:29 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001150920.KAA98140@freebsd.dk> Subject: Re: UDF In-Reply-To: <20000114214234.A14486@foobar.franken.de> from Harold Gutch at "Jan 14, 2000 09:42:34 pm" To: logix@foobar.franken.de (Harold Gutch) Date: Sat, 15 Jan 2000 10:20:29 +0100 (CET) Cc: beattie@aracnet.com (Brian Beattie), hackers@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Harold Gutch wrote: > On Fri, Jan 14, 2000 at 09:29:58AM +0100, Soren Schmidt wrote: > > It seems Brian Beattie wrote: > > > I have been looking at UDF ( the filesystem used on CD-RW and DVD's ). I > > > was wondering if anybody was working on it. I'm thinking about trying to > > > implement it for CD-RW's and would like to avoid duplication of effort and > > > the anoyance of getting half way through the effort and having somebody > > > else show up with a completed implementation. > > > > I have it on my TODO list, but I'm not started yet, and probably wont for > > some time to come. > > The reason I've put it on the backburner for now, is that DVD's can > > be read using the cd9660 filesystem, and that is sufficient for my > > needs for the time being. > > I was under the impression that this was only possible as long as > the DVDs actually had an ISO9660 filesystem as well - which all > of my DVDs have, but which still doesn't mean that there are no > DVDs with only UDF, but no ISO9660 filesystem. I'm pretty sure all DVD's produced to date have an iso9660 file sys on them, but they might change that in the future, so having UDF support would be a win for us in the long run. Again, I'll do the needed things in the ata driver for packet writing etc, but I dont have the time to take on UDF right now... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 1:21:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 9DCFF14E15 for ; Sat, 15 Jan 2000 01:21:31 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 7A7171C03; Sat, 15 Jan 2000 17:21:29 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Bruce Evans Cc: John Polstra , current@FreeBSD.ORG Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. In-Reply-To: Message from Bruce Evans of "Sat, 15 Jan 2000 05:04:53 +1100." Date: Sat, 15 Jan 2000 17:21:29 +0800 From: Peter Wemm Message-Id: <20000115092129.7A7171C03@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Wed, 12 Jan 2000, John Polstra wrote: > > > Jason Evans wrote: > > > > > 2) Make a separate copy of mktemp.c to remove the internal dependency. > > > > I think this is the best approach -- likewise for getobjformat.c, > > I agree. egcs provided "mkstemp.c" to handle the problem, but this > didn't work on Warner's system because he had mkstemps() in libc > (mkstemp.c actually implements mkstemps()) and there is a linker > bug that breaks elf static linkage (library functions can only be > replaced by functions of the same size?). The "fix" was to add > mkstemps() to the -current libc and not use the egcs version. Three > or four subsequent "fixes" led to the current evil one. gcc has > complicated things a little by moving mkstemp.c to a version of > libiberty which we don't have. Reaching out to the libiberty tree > is only slightly better than reaching out to the libc tree. > > Anyway, the main problem is yours to fix in ld :-). No, that's not the problem. The problem is that libc.a has several functions, including mktemp, mkstemp, tmpnam etc, all in the one .o file. gcc (g++ at least) uses mktemp() from that .o file in libc.a. That .o file also provides mkstemps on newer builds. Now, if you try and do this with a function that refers to mktemps: cc -o foo uses_mkstemps.o uses_mktemp.o -lmymkstemps -lc then you end up with mkstemps coming from the first library and then mktemp causing the mktemp+mkstemp+mkstemps+etc.o file to come from libc.a leading to a conflict... we have two mkstemps()'s in the file now and hence the problem. The solution is to break up all the multi-function files in libc as we should have done ages ago. Not only does this work out more efficient for static binaries, it also cuts down a good deal of symbol cross-reference explosions where some file is linked because of one of it's functions and then one of the other functions that came along with it (but is otherwise unused) then causes 20 other .o files to be pulled in to satisfy it's symbols. In dynamic linking mode this doesn't matter. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 3: 3: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 28AED14CB6 for ; Sat, 15 Jan 2000 03:03:01 -0800 (PST) (envelope-from marcel@scc.nl) Received: from scc.nl (dweezil [192.168.3.2]) by mail.scc.nl (8.9.3/8.9.3) with ESMTP id MAA88267; Sat, 15 Jan 2000 12:02:10 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <388053B1.F80D3E01@scc.nl> Date: Sat, 15 Jan 2000 12:02:09 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: "Pierre Y. Dampure" , current@FreeBSD.ORG Subject: Re: make world breaks in /usr/src/usr.bin/xlint References: <16680.947926897@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Sat, 15 Jan 2000 01:45:37 GMT, "Pierre Y. Dampure" wrote: > > > Sorry if my previous message wasn't clear: the change of behaviour in cpp > > breaks lint, hence the build. > > I fixed lint, so I'm surprised that world should break when lint is > called. Perhaps lint needs to be added to the built-tools? No. build-tools are those tiny little utilities that are part of the sources and are only used to build the sources. sed/awk/perl/sh scripts are the things you should be thinking about here. Some of those build-tools are a bit more complex (see gcc) and are C utilities, but that doesn't change their function. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 4:59:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcat.heimat.gr.jp (pcat.heimat.gr.jp [211.0.53.98]) by hub.freebsd.org (Postfix) with ESMTP id A6D8814C07 for ; Sat, 15 Jan 2000 04:59:17 -0800 (PST) (envelope-from nakaji@tutrp.tut.ac.jp) Received: from xa12.heimat.gr.jp (xa12.heimat.gr.jp [211.0.53.97]) by pcat.heimat.gr.jp (8.9.3/3.7W) with ESMTP id VAA12185 for ; Sat, 15 Jan 2000 21:59:15 +0900 (JST) To: current@FreeBSD.ORG Subject: Re: lint not working on -current? MIME-Version: 1.0 (generated by EMIKO 1.13.9 - "Euglena tripteris") Content-Type: text/plain; charset=US-ASCII From: NAKAJI Hiroyuki Date: 15 Jan 2000 21:59:14 +0900 Message-ID: <86zou77aot.fsf@xa12.heimat.gr.jp> Lines: 29 User-Agent: T-gnus/6.14.1 (based on Gnus v5.8.3) (revision 01) EMIKO/1.13.9 (Euglena tripteris) FLIM/1.13.2 (Kasanui) APEL/10.0 Emacs/20.5 (i386--freebsd) MULE/4.0 (HANANOEN) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Sheldon Hearn wrote: SH> I mailed publically a patch to fix this last week. Not a single SH> follow-up since then, so I'll commit it now. :-) Related to this? Today's buildworld fails. ===> usr.bin/xlint/llib lint -Cposix /export/src/usr.bin/xlint/llib/llib-lposix lint -Cstdc /export/src/usr.bin/xlint/llib/llib-lstdc llib-lstdc: llib-lposix: cpp: Invalid option `-undef' *** Error code 1 cpp: Invalid option `-undef' *** Error code 1 2 errors *** 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 -- NAKAJI Hiroyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 5:36:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id DBD5814CCA for ; Sat, 15 Jan 2000 05:36:28 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:01QotcDu6OtlNzINspT7qfStXDSPGW1L@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id WAA13723 for ; Sat, 15 Jan 2000 22:36:27 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id WAA21644; Sat, 15 Jan 2000 22:41:57 +0900 (JST) Message-Id: <200001151341.WAA21644@zodiac.mech.utsunomiya-u.ac.jp> To: current@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: semi-HEADUP: the 3rd stage of syscons code reorganization. Date: Sat, 15 Jan 2000 22:41:56 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a semi-HEADUP. I am going to commit the 3rd stage of syscons code reorganization to -CURRENT. As this is internal source code reorganization, you shouldn't see any functional change. There are a few new files. So, you need to run config(8) before you compile a new kernel next time. If you experience or notice anything strange in the console, please let me know. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 5:54: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [62.104.201.3]) by hub.freebsd.org (Postfix) with ESMTP id 069F814C4F for ; Sat, 15 Jan 2000 05:54:04 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.6] (helo=mx0.01019freenet.de) by mout1.freenet.de with esmtp (Exim 3.12 #2) id 129TeU-0004qG-00 for current@freebsd.org; Sat, 15 Jan 2000 14:54:02 +0100 Received: from [212.81.238.136] (helo=Magelan.Leidinger.net) by mx0.01019freenet.de with esmtp (Exim 3.12 #2) id 129TeU-0000uy-00 for current@freebsd.org; Sat, 15 Jan 2000 14:54:02 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id OAA00557 for ; Sat, 15 Jan 2000 14:45:30 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200001151345.OAA00557@Magelan.Leidinger.net> Date: Sat, 15 Jan 2000 14:45:29 +0100 (CET) From: Alexander Leidinger Subject: crash with ffs_softdep.c 1.52 To: current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, unfortunally no core dump, but I'm able to reproduce it (I just have to enable softupdates). ---snip--- panic: softdep_disk_write_complete: lock is held Debugger("panic") Stopped at Debugger+0x36: mocb $0,in_Debugger.354 db> trace Debugger(x027c6a3) at Debugger+0x36 panic(c028a900, c33618c0, c0a54000, c3361a10, c02a4a34) at panic+0x70 softdep_disk_write_complete(c3361a10) at softdep_disk_write_complete+0x1f vfs_backgroundwritedone(c3361a10, c3361a10, c0a54000, c0aa3400, c0aa3400) at vfs_backgroundwritedone+0x45 biodone(c3361a10, c0a54014, c3361a10) at biodone+0x5a dadone(c0aa0780, c0aa3400, c073ba20, 40000200, ffffffff) at dadone+0x202 camisr(c02d93b4, c02a4cec, c0241b30, 4000200, c0256486) at camisr+0x1ed swi_cambio(40000200, c0256486, c0255f21, 40000200, c0a32800) at swi_cambio+0xd splz_swi(c073bb20, 0, 10, c0240010, 10) at splz_swi+0x14 Xresume9() at Xresume9+0x2b --- interrupt, eip: 0xc024c6ce, esp = 0xc02a4d34, ebp = 0 --- default_halt() at default_halt+0x2 ---snip-- Bye, Alexander. -- Stamp out reality! http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 6:27:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from ds.express.ru (ds.express.ru [212.24.32.7]) by hub.freebsd.org (Postfix) with ESMTP id 7416C14DE4 for ; Sat, 15 Jan 2000 06:26:39 -0800 (PST) (envelope-from vova@express.ru) Received: from lanturn.kmost.express.ru ([212.24.37.109]) by ds.express.ru with esmtp (Exim 2.12 #8) id 129U9r-0004HR-00 for current@freebsd.org; Sat, 15 Jan 2000 17:26:27 +0300 Date: Sat, 15 Jan 2000 17:26:41 +0300 (MSK) From: "Vladimir B. Grebeschikov" X-Sender: vova@lanturn.kmost.express.ru To: current@freebsd.org Subject: syslogd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've make small patch to syslogd, to enable terminate search of logfiles when matched specifig progname, like: # log anything interesting to console *.err;kern.debug;auth.notice;mail.crit /dev/console *.err root *.notice;news.err root *.alert root *.emerg * # log firewall messages ONLY in this file (noy in messages below) !!ipfw *.* /var/log/ipfw !* *.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages mail.info /var/log/maillog lpr.info /var/log/lpd-errs cron.* /var/cron/log may be this patch will be interesting to other freebsd people ? --- usr.sbin/syslogd/syslogd.c.orig Sat Jan 15 14:56:37 2000 +++ usr.sbin/syslogd/syslogd.c Sat Jan 15 16:57:25 2000 @@ -153,6 +153,7 @@ #define PRI_EQ 0x2 #define PRI_GT 0x4 char *f_program; /* program this applies to */ + short f_prog_excl; /* don't match files after chane prog */ union { char f_uname[MAXUNAMES][UT_NAMESIZE+1]; struct { @@ -657,6 +658,7 @@ char *timestamp; char prog[NAME_MAX+1]; char buf[MAXLINE+1]; + int pexcl = 0; dprintf("logmsg: pri %o, flags %x, from %s, msg %s\n", pri, flags, from, msg); @@ -721,6 +723,7 @@ return; } for (f = Files; f; f = f->f_next) { + int pok = 0; /* skip messages that are incorrect priority */ if (!(((f->f_pcmp[fac] & PRI_EQ) && (f->f_pmask[fac] == prilev)) ||((f->f_pcmp[fac] & PRI_LT) && (f->f_pmask[fac] < prilev)) @@ -729,9 +732,20 @@ || f->f_pmask[fac] == INTERNAL_NOPRI) continue; /* skip messages with the incorrect program name */ - if(f->f_program) + if(f->f_program) { if(strcmp(prog, f->f_program) != 0) continue; + else + pok = 1; + + if(f->f_prog_excl) + pexcl = 1; + + } + + if (pexcl && !pok) + break; /* terminate search when f->f_program + no longer match prog */ if (f->f_type == F_CONSOLE && (flags & IGN_CONS)) continue; @@ -1305,7 +1319,7 @@ continue; } for(i = 0; i < NAME_MAX; i++) { - if(!isalnum(p[i])) + if(!isalnum(p[i]) && p[i] != '!') break; prog[i] = p[i]; } @@ -1396,7 +1410,9 @@ if(prog) { f->f_program = calloc(1, strlen(prog)+1); if(f->f_program) { - strcpy(f->f_program, prog); + f->f_prog_excl = (*prog == '!'); + strcpy(f->f_program, prog + (f->f_prog_excl?1:0)); + } } -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 6:45: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 6EE8C14D6A for ; Sat, 15 Jan 2000 06:45:03 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id HAA27675; Sat, 15 Jan 2000 07:07:31 -0800 (PST) Date: Sat, 15 Jan 2000 07:07:31 -0800 From: Alfred Perlstein To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: crash with ffs_softdep.c 1.52 Message-ID: <20000115070730.M508@fw.wintelcom.net> References: <200001151345.OAA00557@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001151345.OAA00557@Magelan.Leidinger.net>; from Alexander@Leidinger.net on Sat, Jan 15, 2000 at 02:45:29PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Alexander Leidinger [000115 06:17] wrote: > Hi, > > unfortunally no core dump, but I'm able to reproduce it (I just have to > enable softupdates). how? It looks like splbio is not up but the softdep lock is held. -Alfred > > ---snip--- > panic: softdep_disk_write_complete: lock is held > Debugger("panic") > Stopped at Debugger+0x36: mocb $0,in_Debugger.354 > db> trace > Debugger(x027c6a3) at Debugger+0x36 > panic(c028a900, c33618c0, c0a54000, c3361a10, c02a4a34) at panic+0x70 > softdep_disk_write_complete(c3361a10) at softdep_disk_write_complete+0x1f > vfs_backgroundwritedone(c3361a10, c3361a10, c0a54000, c0aa3400, c0aa3400) at vfs_backgroundwritedone+0x45 > biodone(c3361a10, c0a54014, c3361a10) at biodone+0x5a > dadone(c0aa0780, c0aa3400, c073ba20, 40000200, ffffffff) at dadone+0x202 > camisr(c02d93b4, c02a4cec, c0241b30, 4000200, c0256486) at camisr+0x1ed > swi_cambio(40000200, c0256486, c0255f21, 40000200, c0a32800) at swi_cambio+0xd > splz_swi(c073bb20, 0, 10, c0240010, 10) at splz_swi+0x14 > Xresume9() at Xresume9+0x2b > --- interrupt, eip: 0xc024c6ce, esp = 0xc02a4d34, ebp = 0 --- > default_halt() at default_halt+0x2 > ---snip-- > > Bye, > Alexander. > > -- > Stamp out reality! > > http://www.Leidinger.net Alexander+Home @ Leidinger.net > Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 7: 1:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 8E07414C96 for ; Sat, 15 Jan 2000 07:01:40 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 25C5D1CD4; Sat, 15 Jan 2000 23:01:38 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Alfred Perlstein Cc: Alexander Leidinger , current@FreeBSD.ORG Subject: Re: crash with ffs_softdep.c 1.52 In-Reply-To: Message from Alfred Perlstein of "Sat, 15 Jan 2000 07:07:31 PST." <20000115070730.M508@fw.wintelcom.net> Date: Sat, 15 Jan 2000 23:01:38 +0800 From: Peter Wemm Message-Id: <20000115150138.25C5D1CD4@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > * Alexander Leidinger [000115 06:17] wrote: > > Hi, > > > > unfortunally no core dump, but I'm able to reproduce it (I just have to > > enable softupdates). > > how? It looks like splbio is not up but the softdep lock is held. The best thing is to look at this global variable for lkt_held: static struct lockit { int lkt_spl; pid_t lkt_held; } lk; and see which process held the lock. Do a traceback on that process as well.. > -Alfred > > > > > ---snip--- > > panic: softdep_disk_write_complete: lock is held > > Debugger("panic") > > Stopped at Debugger+0x36: mocb $0,in_Debugger.354 > > db> trace > > Debugger(x027c6a3) at Debugger+0x36 > > panic(c028a900, c33618c0, c0a54000, c3361a10, c02a4a34) at panic+0x70 > > softdep_disk_write_complete(c3361a10) at softdep_disk_write_complete+0x1f > > vfs_backgroundwritedone(c3361a10, c3361a10, c0a54000, c0aa3400, c0aa3400) a t vfs_backgroundwritedone+0x45 > > biodone(c3361a10, c0a54014, c3361a10) at biodone+0x5a > > dadone(c0aa0780, c0aa3400, c073ba20, 40000200, ffffffff) at dadone+0x202 > > camisr(c02d93b4, c02a4cec, c0241b30, 4000200, c0256486) at camisr+0x1ed > > swi_cambio(40000200, c0256486, c0255f21, 40000200, c0a32800) at swi_cambio+ 0xd > > splz_swi(c073bb20, 0, 10, c0240010, 10) at splz_swi+0x14 > > Xresume9() at Xresume9+0x2b > > --- interrupt, eip: 0xc024c6ce, esp = 0xc02a4d34, ebp = 0 --- > > default_halt() at default_halt+0x2 > > ---snip-- > > > > Bye, > > Alexander. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 7:22:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 35AF714A2C for ; Sat, 15 Jan 2000 07:22:19 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id AAA15041; Sun, 16 Jan 2000 00:21:59 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id AAA10723; Sun, 16 Jan 2000 00:21:58 +0900 (JST) Received: from localhost ([192.168.245.223]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id AAA13540; Sun, 16 Jan 2000 00:21:50 +0900 (JST) To: tcrimi+@andrew.cmu.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help In-Reply-To: <20000112232656W.shin@nd.net.fujitsu.co.jp> References: <20000112232656W.shin@nd.net.fujitsu.co.jp> X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000116002228P.shin@nd.net.fujitsu.co.jp> Date: Sun, 16 Jan 2000 00:22:28 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 32 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What is curious, though, is that during a telnet, running any command > > to dump a large amount of information to the screen will lock up the > > connection forcing me to login again. Similar things happen with ftp > > (locked up after logging in when I first issue an ls). The surest way > > to lock up teh connection is to go to /sys/compile/KERN and do an ls. > > Data piped to more (a screenful at a time) seems to be ok, but > > substancially more locks up TCP connections. This does not occur with > > NFS (I build a kernel using it). > > I suppose something going wrong when multiple mbuf cluster is > used for encrypted TCP connection. I found the problem and my assumption was wrong. That was due to basic mistake that opt_ipsec.h inclusion is missing on several tcp related files. (Actually there was also another bugs behind that, and I could also fix them in the debugging process, luckily.) I fixed the problem and confirmed that it has been fixed. Could you please try it after updating following files? sys/netinet/tcp_input.c sys/netinet/tcp_output.c sys/netinet/tcp_subr.c sys/netinet6/ipsec.h sys/netinet6/ipsec.c Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 10:10:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 698DF14E02 for ; Sat, 15 Jan 2000 10:10:45 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id FAA18109; Sun, 16 Jan 2000 05:10:21 +1100 Date: Sun, 16 Jan 2000 05:10:18 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Peter Wemm Cc: John Polstra , current@FreeBSD.ORG Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. In-Reply-To: <20000115092129.7A7171C03@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000, Peter Wemm wrote: > Bruce Evans wrote: > > ... and there is a linker > > bug that breaks elf static linkage (library functions can only be > > replaced by functions of the same size?). > No, that's not the problem. The problem is that libc.a has several But it is (was). It used to break static linkage of at least ctm_dequeue too, because ctm_dequeue has its own err() which needs to override the standard one. The problem has mysteriously vanished. It was present from approx. last August until recently. It still occurs if ctm_dequeue.c is broken by adding a call to one of the other functions in the library err.o conglomeration: # cc -O -pipe -Wall -I/usr/src/usr.sbin/ctm/ctm_dequeue/../ctm_rmail -static -o ctm_dequeue ctm_dequeue.o error.o # /usr/lib/libc.a(err.o): In function `err': # err.o(.text+0x30): multiple definition of `err' # error.o(.text+0x70): first defined here # /usr/libexec/elf/ld: Warning: size of symbol `err' changed from 232 to 30 in err.o # *** Error code 1 > functions, including mktemp, mkstemp, tmpnam etc, all in the one .o file. > gcc (g++ at least) uses mktemp() from that .o file in libc.a. That .o file > also provides mkstemps on newer builds. Now, if you try and do this with a > function that refers to mktemps: > > cc -o foo uses_mkstemps.o uses_mktemp.o -lmymkstemps -lc > > then you end up with mkstemps coming from the first library and then > mktemp causing the mktemp+mkstemp+mkstemps+etc.o file to come from libc.a > leading to a conflict... we have two mkstemps()'s in the file now and hence > the problem. Indeed. At least cc/cc has this problem when it links to a private copy of mkstemps(), because it uses other functions in the library mktemp.o conglomeration. I thought that this had been fixed. Static linkage should work the same as shared linkage here. Since the library organisation is clearly broken, the bug must be in shared linkage :-). This problem is currently handled by putting a copy of the entire library mktemp.o (rebuilt from current sources) in a private library. It has to provide private versions for all the functions in the host mktemp.o that it uses. There is some potential for getting it wrong, because it needs to satisfy some of the functionality of the host mktemp.o but it uses the target sources. E.g., when we break up mktemp.c, the private library copy of mktemp.o will no longer contain mkstemps, and piecing together current sources to create an object enough like the old mktemp.o will be difficult. > The solution is to break up all the multi-function files in libc as we > should have done ages ago. Not only does this work out more efficient for Not a solution for bootstrapping cc, since it will have no effect on linking cc to an old host library. Given that old libraries are broken, cc should consider that mkstemps() is library magic and use a different name for its version of of it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 10:24: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from dnvrpop1.dnvr.uswest.net (dnvrpop1.dnvr.uswest.net [206.196.128.3]) by hub.freebsd.org (Postfix) with SMTP id D10E614E02 for ; Sat, 15 Jan 2000 10:23:59 -0800 (PST) (envelope-from Davec@unforgettable.com) Received: (qmail 28789 invoked by alias); 15 Jan 2000 18:23:55 -0000 Delivered-To: fixup-current@FreeBSD.ORG@fixme Received: (qmail 28784 invoked by uid 0); 15 Jan 2000 18:23:55 -0000 Received: from odsl228.dnvr.uswest.net (HELO Amber.XtremeDev.com) (209.181.79.228) by dnvrpop1.dnvr.uswest.net with SMTP; 15 Jan 2000 18:23:55 -0000 From: Davec Reply-To: Davec@unforgettable.com To: current@FreeBSD.ORG Subject: games/larn/savelev.c Date: Sat, 15 Jan 2000 11:20:17 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00011511235700.35875@Amber.XtremeDev.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has there been any resolution to the larn game thread? Past week (and more recently, last night since I buildworld nightly) my buildworld has been dying with: ===> games/larn rm -f .depend mkdep -f .depend -a -DCOMPAT_LINUX_THREADS -DVM_STACK -DBSD -DVER=12 -DSUBVER=0 -DNONAP -DU IDSCORE -I/usr/obj/usr/src/i386/usr/include /usr/src/games/larn/main.c /usr/src/games/larn/ob ject.c /usr/src/games/larn/create.c /usr/src/games/larn/tok.c /usr/src/games/larn/display.c /u sr/src/games/larn/global.c /usr/src/games/larn/data.c /usr/src/games/larn/io.c /usr/src/games/ larn/monster.c /usr/src/games/larn/store.c /usr/src/games/larn/diag.c /usr/src/games/larn/help .c /usr/src/games/larn/config.c /usr/src/games/larn/nap.c /usr/src/games/larn/bill.c /usr/src/ games/larn/scores.c /usr/src/games/larn/signal.c /usr/src/games/larn/moreobj.c /usr/src/games/ larn/movem.c /usr/src/games/larn/regen.c /usr/src/games/larn/fortune.c /usr/src/games/larn/sav elev.c *** Error code 130 Stop in /usr/src/games/larn. *** Error code 1 Davec -- Davec@unforgettable.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 11:55: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [62.104.201.5]) by hub.freebsd.org (Postfix) with ESMTP id 9C2AA14C85 for ; Sat, 15 Jan 2000 11:54:58 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.2] (helo=mx1.01019freenet.de) by mout0.freenet.de with esmtp (Exim 3.12 #2) id 129ZHc-0005ga-00; Sat, 15 Jan 2000 20:54:48 +0100 Received: from [213.6.45.139] (helo=Magelan.Leidinger.net) by mx1.01019freenet.de with esmtp (Exim 3.12 #2) id 129ZHb-0000Ao-00; Sat, 15 Jan 2000 20:54:47 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id UAA01264; Sat, 15 Jan 2000 20:11:36 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200001151911.UAA01264@Magelan.Leidinger.net> Date: Sat, 15 Jan 2000 20:11:35 +0100 (CET) From: Alexander Leidinger Subject: Re: crash with ffs_softdep.c 1.52 To: peter@netplex.com.au Cc: bright@wintelcom.net, current@FreeBSD.ORG In-Reply-To: <20000115150138.25C5D1CD4@overcee.netplex.com.au> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Jan, Peter Wemm wrote: > Alfred Perlstein wrote: >> * Alexander Leidinger [000115 06:17] wrote: >> > Hi, >> > >> > unfortunally no core dump, but I'm able to reproduce it (I just have to >> > enable softupdates). >> >> how? It looks like splbio is not up but the softdep lock is held. ^^^^ I just have to enable softupdates on /home, /var, /usr, /usr/obj to get a panic at "Additional daemons: syslogd" while booting. If I disable softupdates at /var I'm able to log in (X11) and dial out -> panic (because of fetchnews/fetchmail/whatever are accessing something). > The best thing is to look at this global variable for lkt_held: > static struct lockit { > int lkt_spl; > pid_t lkt_held; > } lk; > > and see which process held the lock. Do a traceback on that process as well.. How do I do this with _DDB_ (step by step please, I'm not very experienced with it), I get no core dump? Do I have to boot a debug-kernel? Bye, Alexander. -- Animal testing is futile: they always get nervous and give the wrong answers. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 12:20:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id C6116150D4 for ; Sat, 15 Jan 2000 12:20:50 -0800 (PST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id VAA29416; Sat, 15 Jan 2000 21:20:46 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id VAA01099; Sat, 15 Jan 2000 21:06:49 +0100 (CET) (envelope-from root@nihil.plaut.de) Date: Sat, 15 Jan 2000 21:06:48 +0100 (CET) From: Michael Reifenberger To: Rod Taylor Cc: freebsd-current@FreeBSD.ORG Subject: Re: Thoughts... In-Reply-To: <0001150016090H.04098@rbtBSD.intranet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000, Rod Taylor wrote: ... > I want to use FreeBSD on both the workstations (running things like KDE v2, > Star Office for it's MSOffice compatibilities, various electronics ports, and > some of the programming basics). Only thing I'm really missing is a > replacement for windows Matlab. /usr/ports/math/octave Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 12:26:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 7E3B614BC3 for ; Sat, 15 Jan 2000 12:26:14 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id PAA01649; Sat, 15 Jan 2000 15:26:28 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Sat, 15 Jan 2000 15:26:28 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Rod Taylor Cc: freebsd-current@freebsd.org Subject: Re: Thoughts... In-Reply-To: <0001150016090H.04098@rbtBSD.intranet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000, Rod Taylor wrote: > Machines all have ne2k nics with eproms on them. I'd like to mount most > filesystems with CODA due to it's advantages. I notice theres no way to > mount a CODA filesystem for /. Coda is not ready for production use, at least in my experience as a Coda developer :-). I would not recommend using Coda in the environment you describe, although Coda may eventually be the right solution for this kind of environment. There was work to get AFS working with disconnected clients (Arla has some code committed but I don't know how useable it is) -- at this point AFS requires a commercial solution although that also may change in the future. The end answer may be that there is no distributed file system solution that fits your needs at this time. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 14: 7:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id DE1B01510E for ; Sat, 15 Jan 2000 14:07:29 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id OAA88525; Sat, 15 Jan 2000 14:07:15 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 15 Jan 2000 14:07:15 -0800 (PST) From: Doug White To: "Vladimir B. Grebeschikov" Cc: current@FreeBSD.ORG Subject: Re: syslogd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000, Vladimir B. Grebeschikov wrote: > > I've make small patch to syslogd, to enable terminate search of logfiles > when matched specifig progname, like: > > # log anything interesting to console > *.err;kern.debug;auth.notice;mail.crit /dev/console > *.err root > *.notice;news.err root > *.alert root > *.emerg * > > > # log firewall messages ONLY in this file (noy in messages below) > !!ipfw > *.* /var/log/ipfw This is a bad example. ipfw messages come from the kernel so you can't filter those. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 14:34:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 89AA215107 for ; Sat, 15 Jan 2000 14:34:40 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA28069; Sat, 15 Jan 2000 23:25:54 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA61496; Sat, 15 Jan 2000 21:50:19 +0100 (CET) (envelope-from wilko) Date: Sat, 15 Jan 2000 21:50:19 +0100 From: Wilko Bulte To: Bill Paul Cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld fails on Alpha Message-ID: <20000115215018.E61252@yedi.iaf.nl> References: <20000115000720.A28839@yedi.iaf.nl> <200001142352.SAA28490@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001142352.SAA28490@skynet.ctr.columbia.edu>; from wpaul@skynet.ctr.columbia.edu on Fri, Jan 14, 2000 at 06:52:33PM -0500 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 14, 2000 at 06:52:33PM -0500, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Wilko Bulte had > to walk into mine and say: > > > On a very freshly supped -current on Alpha: > > ... > > ===> sys/modules/an > > cd: can't cd to /usr/src/sys/modules/an > > *** Error code 2 > > > > Stop in /usr/src/sys/modules. > > *** Error code 1 > > Roar. I swear I checked in this module Makefile. Honest and for true. Plea accepted ;) > Okay, I think I've really got it this time. Please try cvsupping > again: you should get a src/sys/modules/an/Makefile for compiling > the Aironet driver module. Problem is fixed, buildworld just completed without incidents. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 15: 4: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9B2AE14CA5 for ; Sat, 15 Jan 2000 15:04:06 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id PAA09300; Sat, 15 Jan 2000 15:26:25 -0800 (PST) Date: Sat, 15 Jan 2000 15:26:25 -0800 From: Alfred Perlstein To: Alexander Leidinger Cc: peter@netplex.com.au, current@FreeBSD.ORG Subject: Re: crash with ffs_softdep.c 1.52 Message-ID: <20000115152625.T508@fw.wintelcom.net> References: <20000115150138.25C5D1CD4@overcee.netplex.com.au> <200001151911.UAA01264@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001151911.UAA01264@Magelan.Leidinger.net>; from Alexander@leidinger.net on Sat, Jan 15, 2000 at 08:11:35PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Alexander Leidinger [000115 12:17] wrote: > On 15 Jan, Peter Wemm wrote: > > Alfred Perlstein wrote: > >> * Alexander Leidinger [000115 06:17] wrote: > >> > Hi, > >> > > >> > unfortunally no core dump, but I'm able to reproduce it (I just have to > >> > enable softupdates). > >> > >> how? It looks like splbio is not up but the softdep lock is held. > > ^^^^ > I just have to enable softupdates on /home, /var, /usr, /usr/obj to > get a panic at "Additional daemons: syslogd" while booting. > If I disable softupdates at /var I'm able to log in (X11) and dial out > -> panic (because of fetchnews/fetchmail/whatever are accessing > something). > > > The best thing is to look at this global variable for lkt_held: > > static struct lockit { > > int lkt_spl; > > pid_t lkt_held; > > } lk; > > > > and see which process held the lock. Do a traceback on that process as well.. > > How do I do this with _DDB_ (step by step please, I'm not very > experienced with it), I get no core dump? Do I have to boot a > debug-kernel? http://www.freebsd.org/handbook/kerneldebug.html -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 16:20: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id AC6701513D for ; Sat, 15 Jan 2000 16:20:01 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id QAA46706; Sat, 15 Jan 2000 16:19:59 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id QAA99071; Sat, 15 Jan 2000 16:19:58 -0800 (PST) (envelope-from obrien) Date: Sat, 15 Jan 2000 16:19:58 -0800 From: "David O'Brien" To: wonko@entropy.tmok.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Making sure /var/tmp/vi.recover exists during reboot Message-ID: <20000115161958.A72114@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001141602.LAA51996@blackhelicopters.org> <200001141817.NAA04478@entropy.tmok.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001141817.NAA04478@entropy.tmok.com>; from wonko@users.tmok.com on Fri, Jan 14, 2000 at 01:17:52PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 14, 2000 at 01:17:52PM -0500, Brian Hechinger wrote: > > /var/tmp on MFS makes cc go faster, but breaks vi.recovery What version of src/contrib/gcc/choose-temp.c do you have? /* $FreeBSD: src/contrib/gcc/choose-temp.c,v 1.3 1999/11/04 10:23:25 obrien Exp $ */ has /tmp being used before /var/tmp. AND why the HELL is this cross posted?? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 16:39:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from ds.express.ru (ds.express.ru [212.24.32.7]) by hub.freebsd.org (Postfix) with ESMTP id 638E3150F5 for ; Sat, 15 Jan 2000 16:39:34 -0800 (PST) (envelope-from vova@express.ru) Received: from lanturn.kmost.express.ru ([212.24.37.109]) by ds.express.ru with esmtp (Exim 2.12 #8) id 129dii-0006Jk-00; Sun, 16 Jan 2000 03:39:04 +0300 Date: Sun, 16 Jan 2000 03:39:23 +0300 (MSK) From: "Vladimir B. Grebeschikov" X-Sender: vova@lanturn.kmost.express.ru To: Doug White Cc: current@FreeBSD.ORG Subject: Re: syslogd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000, Doug White wrote: > > # log firewall messages ONLY in this file (noy in messages below) > > !!ipfw > > *.* /var/log/ipfw > > This is a bad example. ipfw messages come from the kernel so you can't > filter those. You are not right, man syslog.conf: ... Each block of lines is separated from the previous block by a tag. The tag is a line beginning with #!prog or !prog (the former is for compati- bility with the previous syslogd, if one is sharing syslog.conf files, for example) and each block will be associated with calls to syslog from > that specific program. A tag for ``foo'' will also match any message > logged by the kernel with the prefix ``foo: ''. ... it really works, try it > Doug White | FreeBSD: The Power to Serve > dwhite@resnet.uoregon.edu | www.FreeBSD.org -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 21:21:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id EF138151EB for ; Sat, 15 Jan 2000 21:21:14 -0800 (PST) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id EFA371C41; Sun, 16 Jan 2000 00:21:13 -0500 (EST) Date: Sun, 16 Jan 2000 00:21:13 -0500 From: Bill Fumerola To: current@FreeBSD.org Subject: PNPBIOS + Dell PowerEdge = panic() Message-ID: <20000116002113.B75768@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i X-Operating-System: FreeBSD 3.2-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hola, As the subject indicated PNPBIOS and Dell PowerEdge servers seem to be a recipe for disaster. This doesn't bother me too terribly much as I don't need PNPBIOS for anything on this machine, but I figured the new-bus folks didn't have enough to do, so I'd help. This machine is a dual pIII/450 w/512MB. This is not SMP specific, BTW. This post exposes my DDB and newbus stupidity. If this was gdb, I'd at least try and pull out some sort of relevent data. I have a guess that the sheer amount/range of the ports and iomem has something to do with it. That or the fact one starts with 0. Thanks and e-mail me privatly or catch me on IRC (bfumerola) if you want me to try things with this server. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - The relative part: unknown0: at port 0x800-0x83f,0x850-0x85f,0xe0-0xef,0x22,0x2e-0x2f,0x80,0xaa00-0xaa7f iomem 0-0x9ffff,0x100000-0x1fffdfff,0xfff80000-0xffffffff,0xf0000-0xfffff,0xec000-0xeffff irq 15 on isa0 panic: pmap_mapdev: Couldn't alloc kernel virtual memory mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.555 The full boot -v: -- Forwarded message from Bill Fumerola -- SMAP type=01 base=00000000 00000000 len=00000000 000a0000 SMAP type=02 base=00000000 000f0000 len=00000000 00010000 SMAP type=01 base=00000000 00100000 len=00000000 1fefe000 SMAP type=02 base=00000000 1fffe000 len=00000000 00002000 SMAP type=02 base=00000000 fff80000 len=00000000 00080000 SMAP type=02 base=00000000 fec00000 len=00000000 00010000 SMAP type=02 base=00000000 fee00000 len=00000000 00010000 Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Jan 14 20:51:21 GMT 2000 jkhblows@crazyhorse.internal.chc-chimes.com:/usr/src/sys/compile/GLUEPNP Calibrating clock(s) ... TSC clock: 447668222 Hz, i8254 clock: 1193124 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium III/Xeon (447.69-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 536862720 (524280K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00300000 - 0x1fffbfff, 533708800 bytes (130300 pages) avail memory = 518021120 (505880K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 bios32: Found BIOS32 Service Directory header at 0xc00ffe80 bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xcc0e pnpbios: Found PnP BIOS data at 0xc00fe2d0 pnpbios: Entry = f0000:e2f4 Rev = 1.0 Other BIOS signatures found: ACPI: 000fdef0 Preloaded elf kernel "pnpbios" at 0xc02e4000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x80000090 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71a08086) devclass_alloc_unit: pcib0 already exists, using next available unit number npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71a08086) pcib0: on motherboard found-> vendor=0x8086, dev=0x71a0, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base f0000000, size 26 found-> vendor=0x8086, dev=0x71a1, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x1011, dev=0x0024, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=3 secondarybus=2 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=0 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 00000850, size 4 Freeing (NOT implemented) redirected PCI irq 14. found-> vendor=0x10b8, dev=0x0005, revid=0x08 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=20 map[10]: type 1, range 32, base 0000dc00, size 8 map[14]: type 1, range 32, base fe000000, size 12 pci0: on pcib0 pcib2: at device 1.0 on pci0 found-> vendor=0x1002, dev=0x4744, revid=0x5c class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base fc000000, size 24 map[14]: type 1, range 32, base 0000fc00, size 8 map[18]: type 1, range 32, base fbfff000, size 12 pci1: on pcib2 vga-pci0: port 0xfc00-0xfcff mem 0xfbfff000-0xfbffffff,0xfc000000-0xfcffffff at device 0.0 on pci1 pcib3: at device 2.0 on pci0 Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x9005, dev=0x001f, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 1, range 32, base 0000ec00, size 8 map[14]: type 1, range 64, base f9fff000, size 12 found-> vendor=0x8086, dev=0x0960, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=1 subordinatebus=3 secondarybus=3 Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x8086, dev=0x1960, revid=0x03 class=0e-00-01, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=18 map[10]: type 1, range 32, base f6c00000, size 22 pci2: on pcib3 ahc0: port 0xec00-0xecff mem 0xf9fff000-0xf9ffffff irq 16 at device 4.0 on pci2 ahc0: Reading SEEPROM...done. ahc0: Manual LVD Termination ahc0: BIOS eeprom is present ahc0: Secondary High byte termination Enabled ahc0: Secondary Low byte termination Enabled ahc0: Primary Low Byte termination Enabled ahc0: Primary High Byte termination Enabled ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 399 instructions downloaded pcib4: at device 10.0 on pci2 pci3: on pcib4 amr0: mem 0xf6c00000-0xf6ffffff irq 18 at device 10.1 on pci2 amr0: firmware 3.00 bios 1.36 16MB memory amrd0: on amr0 amrd0: 17136MB (35094528 sectors) RAID 5 (optimal) Creating DISK amrd0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: Intel PIIX4 ATA controller (vendor=0x8086, dev=0x7111) at 7.1 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 0 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x850-0x85f at device 7.3 on pci0 tx0: port 0xdc00-0xdcff mem 0xfe000000-0xfe000fff irq 20 at device 8.0 on pci0 tx0: address 00:e0:29:36:21:2d, type SMC9432TX, Auto-Neg 100Mbps bpf: tx0 attached pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71a08086) devclass_alloc_unit: pci1 already exists, using next available unit number pcib1: on motherboard pci4: on pcib1 pnpbios: 16 devices, largest 179 bytes PNP0c02: adding memory range 0-0x9ffff, size=0xa0000 PNP0c02: adding memory range 0x100000-0x1fffdfff, size=0x1fefe000 PNP0c02: adding memory range 0xfff80000-0xffffffff, size=0x80000 PNP0c02: adding memory range 0xf0000-0xfffff, size=0x10000 PNP0c02: adding memory range 0xec000-0xeffff, size=0x4000 PNP0c02: adding io range 0x800-0x83f, size=0x40, align=0x1 PNP0c02: adding io range 0x850-0x85f, size=0x10, align=0x1 PNP0c02: adding io range 0xe0-0xef, size=0x10, align=0x1 PNP0c02: adding io range 0x22-0x22, size=0x1, align=0x1 PNP0c02: adding io range 0x2e-0x2f, size=0x2, align=0x1 PNP0c02: adding io range 0x80-0x80, size=0x1, align=0x1 PNP0c02: adding io range 0xaa00-0xaa7f, size=0x80, align=0x1 PNP0c02: adding irq mask 0x8000 PNP0c02: start dependant pnpbios: handle 0 device ID PNP0c02 (020cd041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 PNP0501: start dependant pnpbios: handle 2 device ID PNP0501 (0105d041) PNP0501: adding irq mask 00x8 PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0x8 PNP0501: start dependant pnpbios: handle 3 device ID PNP0501 (0105d041) PNP0401: adding dma mask 0x2 PNP0401: adding irq mask 0x80 PNP0401: adding io range 0x378-0x37f, size=0x8, align=0x8 PNP0401: adding io range 0x778-0x77b, size=0x4, align=0x8 PNP0401: start dependant pnpbios: handle 4 device ID PNP0401 (0104d041) PNP0700: adding irq mask 0x40 PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x8 PNP0700: adding dma mask 0x4 PNP0700: start dependant pnpbios: handle 5 device ID PNP0700 (0007d041) PNP0f13: adding irq mask 0x1000 PNP0f13: start dependant pnpbios: handle 6 device ID PNP0f13 (130fd041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0a03: start dependant pnpbios: handle 7 device ID PNP0a03 (030ad041) PNP0c02: adding irq mask 0x200 PNP0c02: start dependant pnpbios: handle 8 device ID PNP0c02 (020cd041) PNP0000: adding irq mask 00x4 PNP0000: adding io range 0x20-0x21, size=0x2, align=0x1 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0x1 PNP0000: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0000: start dependant pnpbios: handle 9 device ID PNP0000 (0000d041) PNP0003: adding memory range 0xfee00000-0xfee0ffff, size=0x10000 PNP0003: adding memory range 0xfec00000-0xfec0ffff, size=0x10000 PNP0003: start dependant pnpbios: handle 10 device ID PNP0003 (0300d041) PNP0100: adding irq mask 00x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 PNP0100: start dependant pnpbios: handle 11 device ID PNP0100 (0001d041) PNP0200: adding io range 0x81-0x8f, size=0xf, align=0x1 PNP0200: adding io range 0-0xf, size=0x10, align=0x1 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 PNP0200: adding dma mask 0x10 PNP0200: start dependant pnpbios: handle 12 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: start dependant pnpbios: handle 13 device ID PNP0303 (0303d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 PNP0800: start dependant pnpbios: handle 14 device ID PNP0800 (0008d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x73, size=0x4, align=0x1 PNP0b00: start dependant pnpbios: handle 15 device ID PNP0b00 (000bd041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: start dependant pnpbios: handle 16 device ID PNP0c04 (040cd041) Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices 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 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> sc0: fb0 kbd0 sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold isa_probe_children: probing PnP devices unknown0: at port 0x800-0x83f,0x850-0x85f,0xe0-0xef,0x22,0x2e-0x2f,0x80,0xaa00-0xaa7f iomem 0-0x9ffff,0x100000-0x1fffdfff,0xfff80000-0xffffffff,0xf0000-0xfffff,0xec000-0xeffff irq 15 on isa0 panic: pmap_mapdev: Couldn't alloc kernel virtual memory mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.555 db> trace Debugger(c0242cd2) at Debugger+0x35 panic(c0258d00,0,c148d540,3,c0296360) at panic+0xa4 pmap_mapdev(100000,1fefdfff,2,1fefe000,1fffdfff) at pmap_mapdev+0x46 nexus_alloc_resource(c147b200,c1483b80,3,c02f8cdc,100000) at nexus_alloc_resource+0xa8 BUS_ALLOC_RESOURCE(c147b200,c1483b80,3,c02f8cdc,100000) at BUS_ALLOC_RESOURCE+0x43 bus_generic_alloc_resource(c147b180,c1483b80,3,c02f8cdc,100000) at bus_generic_alloc_resource+0x2d BUS_ALLOC_RESOURCE(c147b180,c1483b80,3,c02f8cdc,100000) at BUS_ALLOC_RESOURCE+0x43 resource_list_alloc(c147c5c4,c147b000,c1483b80,3,c02f8cdc) at resource_list_alloc+0x69 pci_alloc_resource(c147b000,c1483b80,3,c02f8cdc,100000) at pci_alloc_resource+0x38 BUS_ALLOC_RESOURCE(c147b000,c1483b80,3,c02f8cdc,100000) at BUS_ALLOC_RESOURCE+0x43 bus_generic_alloc_resource(c147dc00,c1483b80,3,c02f8cdc,100000) at bus_generic_alloc_resource+0x2d BUS_ALLOC_RESOURCE(c147dc00,c1483b80,3,c02f8cdc,100000) at BUS_ALLOC_RESOURCE+0x43 resource_list_alloc(c147c5c0,c1483f80,c1483b80,3,c02f8cdc,100000,ffffffff,1,2) at resource_list_alloc+0xf1 isa_probe_children(c1483f80) at isa_probe_children+0x186 configure(0,2f6c00,300000,0,c011c4d6) at configure+0x41 mi_startup(c02f8fb4,0,0,a04,0) at mi_startup+0x70 begin() at begin+0x4b db> panic panic: from debugger mp_lock = 00000003; cpuid = 0; lapic.id = 01000000 Uptime: 0s amr0: flushing cache... ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 21:26:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2CF3A15229 for ; Sat, 15 Jan 2000 21:26:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA02919; Sat, 15 Jan 2000 21:26:08 -0800 (PST) (envelope-from dillon) Date: Sat, 15 Jan 2000 21:26:08 -0800 (PST) From: Matthew Dillon Message-Id: <200001160526.VAA02919@apollo.backplane.com> To: The Hermit Hacker Cc: Rod Taylor , freebsd-current@FreeBSD.ORG Subject: Re: Thoughts... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> There are lots of ways of syncing up that do not require sending the :> entire image over the network every time. Syncing is something you could :> do with an NFS mount quite easily, combined with something like cpdup :> (see /usr/ports/sysutils/cpdup). : :we use rdist on our network to keep our production servers in sync...we :tend to avoid 'nfs traffic' as much as possible... : :Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy I've never trusted rdist for exact mirroring. I remember trying to use it at BEST and it not getting everything right, though I can't remember exactly what it didn't get right... probably things like devices and hardlinks. I wound up taking the 'stat' hit and having the clients scan the disk hierarchy for changes, and making sure the NFS server could handle it. But you do not have to do things that way -- for example, the server could keep track of the changes itself and send a list to the client which the client then copies via NFS. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 15 21:33: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id B860715091; Sat, 15 Jan 2000 21:33:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id AE79F1CD5D7; Sat, 15 Jan 2000 21:33:05 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 15 Jan 2000 21:33:05 -0800 (PST) From: Kris Kennaway To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Cc: current@freebsd.org Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile In-Reply-To: <200001160523.VAA88902@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000, Kris Kennaway wrote: > Support RSA via RSAref. This autodetects the RSAref package, and if it > is not found, compiles without RSA. Openssl should now be fully functional for both US and international users - please report any problems you have in using it to me. You should be able to compile all openssl-using code (some of them require rsaref and therefore cannot be used in a commercial setting, others do not), although the ports may need tweaking to deal with the changed base location (/usr instead of /usr/local). Dirk Froemberg (dirk@freebsd.org) has kindly offered to help with integration issues with the ports - so any issues with ports please CC to both of us (and the maintainer). The only outstanding issue I'm aware of with OpenSSL is enabling platform-specific optimizations (e.g. assembler versions of algorithms) which is next on my list of things to tackle. Thanks, Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message