From owner-freebsd-current Sun Jan 14 0:19:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id AFB1937B400 for ; Sun, 14 Jan 2001 00:19:21 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0E8IuZ27762; Sun, 14 Jan 2001 09:18:56 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matt Dillon Cc: Garrett Wollman , Matthew Thyer , Sheldon Hearn , Edwin Culp , current@FreeBSD.ORG Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed In-Reply-To: Your message of "Sat, 13 Jan 2001 22:36:45 PST." <200101140636.f0E6ajX43032@earth.backplane.com> Date: Sun, 14 Jan 2001 09:18:56 +0100 Message-ID: <27760.979460336@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101140636.f0E6ajX43032@earth.backplane.com>, Matt Dillon writes: > MFS is very inefficient. I didn't fix that... it isn't possible to > fix it without a lot of work. The real fix is to make "struct buf" more object oriented, so that instead of bwrite(bp) one does bp->b_op[BOP_BWRITE](bp) (possibly through a suitable #define.) Once this is in place, the UFS layer doesn't have to operate on a disk and the following things should be within our grasp: Mounting of filesystems in plain files (rather than using vn) A real VMFS or TMPFS which uses UFS as naming for anonymous VM objects. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 4:18:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 8621437B400 for ; Sun, 14 Jan 2001 04:18:26 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0ECIHY77893; Sun, 14 Jan 2001 04:18:17 -0800 (PST) (envelope-from obrien) Date: Sun, 14 Jan 2001 04:18:16 -0800 From: "David O'Brien" To: Matthew Thyer Cc: current@freebsd.org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed Message-ID: <20010114041815.A67367@dragon.nuxi.com> Reply-To: freebsd-current@freebsd.org References: <12391.979395443@axl.fw.uunet.co.za> <3A614312.DAAEA5E0@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A614312.DAAEA5E0@camtech.net.au>; from thyerm@camtech.net.au on Sun, Jan 14, 2001 at 04:41:30PM +1030 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 14, 2001 at 04:41:30PM +1030, Matthew Thyer wrote: > At the time the message occurred I had less than 6 MB usage in > /tmp if that. I believe that for `df' output. But what was the memory usage of the mfs processes (using `ps')? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 5:11: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail1-gui.server.ntli.net (mail1-gui.server.ntli.net [194.168.222.13]) by hub.freebsd.org (Postfix) with ESMTP id B430737B698 for ; Sun, 14 Jan 2001 05:10:37 -0800 (PST) Received: from sunrise.wells.org.uk ([62.253.133.8]) by mail1-gui.server.ntli.net (Post.Office MTA v3.1 release PO203a ID# 0-33929U70000L2S50) with ESMTP id AAA7256 for ; Sun, 14 Jan 2001 13:04:47 +0000 Received: from michael by sunrise.wells.org.uk with local (Exim 3.20 FreeBSD) id 14Hmw6-000080-00 for ; Sun, 14 Jan 2001 13:11:06 +0000 Date: Sun, 14 Jan 2001 13:11:06 +0000 From: Michael Wells To: freebsd-current@freebsd.org Subject: Soundblaster 64 PCI Message-ID: <20010114131106.A476@wells.org.uk> Mail-Followup-To: Michael Wells , freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGPkeyserver: wwwkeys.eu.pgp.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I just got round to popping the lid on my machine and installing a Soundblaster 64 PCI card. I already had pcm in my kernel. It's working, but there are some Strange Things Happening. Firstly, here's /dev/sndstat: FreeBSD Audio Driver (newpcm) Jan 5 2001 12:50:04 Installed devices: pcm0: at io 0xec00 irq 16 (1p/1r channels duplex) (Aside: is that really the chipset on the Soundblaster 64?). I get kernel warnings since I installed the card: Jan 14 13:00:15 sunrise /boot/kernel/kernel: pcm0: hwptr went backwards 2112 -> 1888 I'm using FreeBSD Current, built on 5 January 2001. What I've got is some very strange sounds when I run mpg123 on a standard MP3 file. It's going through /dev/dsp and appears to play the samples at a very slow speed, with weird echoes. It's like a special effect. Using the -a flag with mpg123 allows me to play through /dev/audio, which sounds right except that it's distorted. At all volume levels, the audio sounds overdriven, and I know this is not due to impedance mismatches or faults elsewhere having used the card in Linux with the same cabling arrangements, amplifier etc. If this is a known problem, I'll stop for now and watch out for fixes. If it's not the expected behaviour from the PCM driver though, can anyone advise? Regards Michael -- www.wells.org.uk +44 7715 747252 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 6:56:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from nod.voidpointer.com (unknown [64.50.142.194]) by hub.freebsd.org (Postfix) with ESMTP id EDAE837B400 for ; Sun, 14 Jan 2001 06:56:06 -0800 (PST) Received: from localhost (mark@localhost) by nod.voidpointer.com (8.9.3/8.9.3) with ESMTP id JAA01709 for ; Sun, 14 Jan 2001 09:55:55 -0500 Date: Sun, 14 Jan 2001 09:55:55 -0500 (EST) From: To: freebsd-current@FreeBSD.org Subject: subscribe 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 7: 6:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 64CDD37B400 for ; Sun, 14 Jan 2001 07:06:01 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14Hoit-0005iB-00; Sun, 14 Jan 2001 17:05:35 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id RAA02573; Sun, 14 Jan 2001 17:05:01 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 2439; Sun Jan 14 17:04:11 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.20 #1) id 14HohX-0004sy-00; Sun, 14 Jan 2001 17:04:11 +0200 From: Sheldon Hearn To: Matthew Thyer Cc: Edwin Culp , current@freebsd.org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed In-reply-to: Your message of "Sun, 14 Jan 2001 16:41:30 +1030." <3A614312.DAAEA5E0@camtech.net.au> Date: Sun, 14 Jan 2001 17:04:11 +0200 Message-ID: <18783.979484651@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Jan 2001 16:41:30 +1030, Matthew Thyer wrote: > Sheldon, I'm not stupid. Sorry to have come across like that. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 10: 4: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from uvika.dn.ua (unknown [195.184.223.26]) by hub.freebsd.org (Postfix) with ESMTP id 042FA37B698 for ; Sun, 14 Jan 2001 10:03:20 -0800 (PST) Received: from uvika.dn.ua (i-ris.donbass.com [195.184.222.22]) by uvika.dn.ua (8.11.1/8.11.1) with SMTP id f0EI2X899824 for ; Sun, 14 Jan 2001 20:02:34 +0200 (EET) Message-Id: <200101141802.f0EI2X899824@uvika.dn.ua> From: "Igor E. Segal" To: Subject: Momentary readout information Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sun, 14 Jan 2001 20:02:58 +0200 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sears! We are glad to propose You the unique opportunity of fundamental life changing with the consultation of Universe Informational Center. We suggest momentary readout information from any animate and inanimate object independently from time and distance. Diagnostics of everything alive, that exists on the Earth and in the Space. It's enough for you to name the living being and the age or the object of your interest, its number and what you'd like to find out about it. The exactness of answer depends on the exactness of an asked question. Everything occurs as in computer system. You formulate your question, briefly and exactly, and receive a brief and exact answer. SCIENCE, TECHNICS, ASTRONAUTICS We can diagnose any facilities, buildings, constructions, examine the lands for construction. We can analyse of expedience and prospects of developed scientific, military and state programs, scientific hypothesis and discoveries. Drawing conclusions about all future positive and negative qualities of an invention, including every detail of a future machine. If it is a vehicle for Mars or Venus - we'll describe its mode of work and its service life at this planet. We'll say beforehand what detail will go out of service and why, what is desirable to improve, to change and so on. At the same time we can already now describe not only what your vehicle will find there, but also what is really exists there: kind of vegetation, its color, growth, taste, smell, presence of water, minerals, forms of intellect, etc. We know the time of contact failure with any apparatus at any planet, we can find the reason and re-establish the contact. For military, navy, space and other subdivisions of state and united forces without departure to the location we can instantly look through the technical condition of any fighting unit, warship, spaceship of any country, professional training of any separate serviceman, an expedience of war actions and their final result, and we can give answers to other questions of interest. Complete examination of all military and civil planes, rockets, etc. As to their security and a state of wear at the whole territory of any country. Instant checking of service ability of all devices, reactors, control instruments and sensors at any sections independently of its distance and location. Prediction of the any spaceship launch result 3-4 days before the event. In case of unsuccessful launch we can locate the cause of a fault in a spaceship beforehand. It's possible to invent the machines of the far future (XXI, XXII c.) now. Several minutes it is enough to form future staff of designers, scientists, leaders - to choose the most talented of all students of high schools (in any branch). It's possible to talk to any archaeological finding, to go with it deep through decades, centuries, millennium, etc. An instant answer whether there is a virus in your computer. Answers to the questions of science: structure of the Universe, genesis of human and all animate, the secrets of microcosm, of gene structures and activity of human brain, search of new sources of energy, mysteries of time, etc. Examination of the Earth, the Sun, the Moon, any planet, etc. in section. Questions should be asked by specialists, the answers will be given instantly and at once to any question. PUBLIC HEALTH, ECOLOGY According to your wish we can examine the state of each organ separately: blond circulatory, nervous and other systems. Complete diagnostics of any person health during several minutes independently of distance and location. ( It's enough to point out name and age). We can analyze suitability of any medicine to a definite person, expedience of an impending operation and its reasons. If you are still going to be operated, I can prompt a favorable dale and hour for a perfect operation. ( It's enough to point out a doctor's name and place of operation). We can predict and examine the course of pregnancy, sex and growth of a baby, etc. For specialists - the medicine of future, the methods of struggle with cancer, viruses, ageing, vaccine against AIDS and other questions. Examination of territory and food as to their ecological safety. ECONOMICS, POLITICS Prediction of real chances of victory in pre-election and election campaigns of this or that candidate. Any member of government can instantly find out what is dune in other government establishments, their true attitude to governments and to the country in the whole. It is possible to find out what is done in any town of country, etc. In case you have to lead business meetings, you may know it beforehand how negotiations will go what can be expected from your partners, to financial state, the results of negotiations, future deals, credit rating of your partners and whether al all they have that what they offer you. You may know it beforehand whether your money or credit you are going to lend be returnable. (It is enough to name a debtor). If you hire a man for work, it is enough for you to name a position he is hired for and you may know all about his professional, business and human qualities, etc. For the leaders of all levels - all questions related their life and activity, including the questions of security. PRIVATE With our help you may talk to any relatives and acquaintances at any distance, find out their true attitude towards you, their thoughts, thoughts and attitude to you of your pets, trees and flowers in your garden, your cars - of all animate and inanimate objects. You may know what name is suitable for your child, what occupation your child is intended for, whether it is worth for him or her to marry (expedience of this or that marriage and its reasons). Your past (including your last lives), present and future. Your predestination and tasks in this life. The ways of solving problems. You'll get assistance in buying any immovable property. It is possible to examine quality of any selected wares, safety of your trips, flights and voyages. If you want to know about the weather in a day of your interest, it is enough for you to point out a day of week, month, year and You will get all necessary information. We have a favour to ask for You don`t ask the questions about non-existent objects and criminal or heated - playing features. Our work is being constructed at the base of agreement or contract. Please, ask You first three questions for free and, if You will satisfied by the results, we shell sign agreement about consultation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 10:17:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id E2CA937B400 for ; Sun, 14 Jan 2001 10:17:29 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.11.1/8.11.1) id f0EIH3F34298 for current@freebsd.org; Sun, 14 Jan 2001 13:17:03 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200101141817.f0EIH3F34298@hda.hda.com> Subject: Re: Fan speed control sony vaio lx800 slimtop In-Reply-To: <200101121305.f0CD5kx23941@hda.hda.com> from Peter Dufault at "Jan 12, 2001 08:04:31 am" To: current@freebsd.org Date: Sun, 14 Jan 2001 13:17:02 -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 I'm slightly hoping that enabling an AUTO HALT mode will turn the fan down. I don't think it will, I think I will have to do some subset of what "acpiconf -s 1" does in cpu_idle but will still respond to the next clock interrupt... So my two questions are: 1. Is there an obvious subset of S1 that would be an acceptable replacement for executing HLT and nothing happening in cpu_idle, and, 2. Does anyone understand "AUTO HALT", low power mode, etc on the Pentium III? I found programs (previous message has links) to enable power saving modes on Pentia, but they set a bit in "Model Specific Register 0x12: CTR0", and the Pentium III documentation says "code that accesses registers 11H, 12H, and 13H will generate exceptions on a P6 family processor". (IA-32 Software Developer's Manual, Volume 3: System Programming Guide, Intel order number 245472, page B-25) Peter (The system is reasonably quiet now with my additional sound proofing, but I'm afraid it isn't designed to continously run what was originally an unacceptably noisy fan). -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 12:58:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 5EE3237B698 for ; Sun, 14 Jan 2001 12:58:38 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f0EKuox08029; Sun, 14 Jan 2001 16:56:50 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 14 Jan 2001 16:56:50 -0400 (AST) From: The Hermit Hacker To: Michael Wells Cc: Subject: Re: Soundblaster 64 PCI In-Reply-To: <20010114131106.A476@wells.org.uk> 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, 14 Jan 2001, Michael Wells wrote: > Hi all, > > I just got round to popping the lid on my machine and installing a > Soundblaster 64 PCI card. I already had pcm in my kernel. It's working, > but there are some Strange Things Happening. > > Firstly, here's /dev/sndstat: > > FreeBSD Audio Driver (newpcm) Jan 5 2001 12:50:04 > Installed devices: > pcm0: at io 0xec00 irq 16 (1p/1r channels duplex) > > (Aside: is that really the chipset on the Soundblaster 64?). I get kernel warnings since I installed the card: > > Jan 14 13:00:15 sunrise /boot/kernel/kernel: pcm0: hwptr went backwards > 2112 -> 1888 > > I'm using FreeBSD Current, built on 5 January 2001. > > What I've got is some very strange sounds when I run mpg123 on a > standard MP3 file. It's going through /dev/dsp and appears to play the > samples at a very slow speed, with weird echoes. It's like a special > effect. Using the -a flag with mpg123 allows me to play through > /dev/audio, which sounds right except that it's distorted. At all > volume levels, the audio sounds overdriven, and I know this is not > due to impedance mismatches or faults elsewhere having used the card in > Linux with the same cabling arrangements, amplifier etc. > > If this is a known problem, I'll stop for now and watch out for fixes. > If it's not the expected behaviour from the PCM driver though, can > anyone advise? Okay, just checked and it appears tha htis is the same error that I'm seeing on mine, as reported yesterday ... not sure if its known or not, but its not "just you" ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 13: 2:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 41ACC37B402; Sun, 14 Jan 2001 13:02:32 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0EL2OI25280; Sun, 14 Jan 2001 23:02:27 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101142102.f0EL2OI25280@gratis.grondar.za> To: jhb@freebsd.org Cc: current@freebsd.org Subject: Atomic breakage? Date: Sun, 14 Jan 2001 23:02:28 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi John There seems to be same breakage in the atomic stuff: link_elf: symbol atomic_load_acq_int undefined KLD file random.ko - could not finalize loading I back out the latest commit to sys/i386/include/atomic.h, and things work a bit better (on my laptop). M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 13:12:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from vilnya.demon.co.uk (vilnya.demon.co.uk [158.152.19.238]) by hub.freebsd.org (Postfix) with ESMTP id 0991A37B698 for ; Sun, 14 Jan 2001 13:12:27 -0800 (PST) Received: from darkstar (dyn18.rings [10.2.4.146]) by vilnya.demon.co.uk (Postfix) with SMTP id 11E91D9BC; Sun, 14 Jan 2001 21:12:25 +0000 (GMT) Message-ID: <002f01c07e6e$2fe234b0$9204020a@darkstar> From: "Cameron Grant" To: "The Hermit Hacker" , "Michael Wells" Cc: References: Subject: Re: Soundblaster 64 PCI Date: Sun, 14 Jan 2001 21:08:47 -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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If this is a known problem, I'll stop for now and watch out for fixes. > > If it's not the expected behaviour from the PCM driver though, can > > anyone advise? > > Okay, just checked and it appears tha htis is the same error that I'm > seeing on mine, as reported yesterday ... not sure if its known or not, > but its not "just you" ... are either of you using esound or xmms? if so, i know the cause of this and it will be fixed shortly, once my primary development box recovers from killing its cpu. if not, i'll try to reproduce this. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 13:29:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 25A3237B400 for ; Sun, 14 Jan 2001 13:29:40 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f0ELRvk19242; Sun, 14 Jan 2001 17:27:57 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 14 Jan 2001 17:27:57 -0400 (AST) From: The Hermit Hacker To: Cameron Grant Cc: Michael Wells , Subject: Re: Soundblaster 64 PCI In-Reply-To: <002f01c07e6e$2fe234b0$9204020a@darkstar> 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, 14 Jan 2001, Cameron Grant wrote: > > > If this is a known problem, I'll stop for now and watch out for fixes. > > > If it's not the expected behaviour from the PCM driver though, can > > > anyone advise? > > > > Okay, just checked and it appears tha htis is the same error that I'm > > seeing on mine, as reported yesterday ... not sure if its known or not, > > but its not "just you" ... > > are either of you using esound or xmms? if so, i know the cause of this and > it will be fixed shortly, once my primary development box recovers from > killing its cpu. > > if not, i'll try to reproduce this. for me, I tried using splay ... but, not sure how old my compile was, so am just installing a new copy and will report back ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 13:32:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 27C0A37B402 for ; Sun, 14 Jan 2001 13:32:04 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f0ELUJN20585; Sun, 14 Jan 2001 17:30:19 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 14 Jan 2001 17:30:19 -0400 (AST) From: The Hermit Hacker To: Cameron Grant Cc: Michael Wells , Subject: Re: Soundblaster 64 PCI 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 yup, just confirmed ... it does it with splay as well ... On Sun, 14 Jan 2001, The Hermit Hacker wrote: > On Sun, 14 Jan 2001, Cameron Grant wrote: > > > > > If this is a known problem, I'll stop for now and watch out for fixes. > > > > If it's not the expected behaviour from the PCM driver though, can > > > > anyone advise? > > > > > > Okay, just checked and it appears tha htis is the same error that I'm > > > seeing on mine, as reported yesterday ... not sure if its known or not, > > > but its not "just you" ... > > > > are either of you using esound or xmms? if so, i know the cause of this and > > it will be fixed shortly, once my primary development box recovers from > > killing its cpu. > > > > if not, i'll try to reproduce this. > > for me, I tried using splay ... but, not sure how old my compile was, so > am just installing a new copy and will report back ... > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 13:57: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 9D8E137B401; Sun, 14 Jan 2001 13:56:44 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0ELubZ31575; Sun, 14 Jan 2001 22:56:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Andrea Campi Cc: developer@freebsd.org, current@freebsd.org Subject: Re: cvs commit: src/sys/i386/conf GENERIC In-Reply-To: Your message of "Sun, 14 Jan 2001 22:16:52 +0100." <20010114221651.A3627@webcom.it> Date: Sun, 14 Jan 2001 22:56:36 +0100 Message-ID: <31573.979509396@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010114221651.A3627@webcom.it>, Andrea Campi writes: >> >> I think it's the time to throw i386 over the railing and lower the >> >> waterline a fair bit on -current. >> > >> >Does it make any sense at all to make 80386 a separate platform >> >a'la pc98/alpha/ia64? Do enough people care about it? >> >> No it doesn't. I think you'll find that running 5.x in less than >> 32MB is going to be painfull or impossible in the first place. > >Sorry Poul, I think the question here is: "if we decide to remove i386 support >BUT a few people still want to use it and can maintain it as a separate >platform port, is it an option to do so, from a technical point of view?" > >Personally, I don't care about i386 support in -current, but if it's possible >to keep it in parallel, then why not? (This is a general answer, not just about i386 support:) Any feature in FreeBSD needs a minimum amount of maintenance. If nobody cares about some particular bit of code, it will slowly of quickly rot away. It's not that the actual bits themselves change, but FreeBSD changes around them all the time. APIs get tweaked, usage models change, all the time, a continuous growth process. If nobody has the hardware to test it on, *and* the inclination to do so, it will not get tested, and the code will erode as a result. I have a 386SX/20 CPU, but I'll be damned if I can be bothered to boot FreeBSD-current on it, in fact it didn't even boot a 4.x last I tried. Any feature can survive in FreeBSD if sufficient manpower is spent maintaining it: If you came in with 10 dedicated and able hackers, you could get a VAX-11 architecture into FreeBSD. If you can muster the people needed to write the increasinly quirky assembler code replacements for features the i386 CPU doesn't have I'm sure you can keep the i386 alive for some years. The reason against doing so is that it complicates our code. Makes it less readable. Forces us to make tradeoffs which hits modern hardware on the performance meter. Yes, like anybody else I'll be sad to see i386 support go, but hey... none of my i486 systems can even boot the current install floppy anymore, I think you need 32MB RAM for that and I only have 16MB in my systems. If we should do anything for the i386, it should be for some intrinsic value that particular chip has. Apart from maybe the rad-hard and possibly VHDL-macro aspects, the only unique property the i386 has for me these days is "history". I don't do satelites, I suspect most of you don't, and I suspect those of you who do know just how far FreeBSD-5.x will be from that market segment for some years to come. If you design something with a VHDL i386 core these days, I bet you're not trying to load it with a unix kernel anyway. If you are you'll have so many tweaks already, that I doubt you would want to look at FreeBSD 5.x for your one-chip design. Personally I would not really find it interesting to have a BSD2.X style "FreeBSD-lite" created for the i386 for mostly sentimental reasons, and I have a perfectly good reason for that: My i386 box has that one last intrinsic feature served much better with the OS I have installed on it: "386BSD 0.1newer + patchkit". Not only does it boot in 20 seconds flat but most importantly it reminds me how far we have come in the last 9 years by sweeping the broom every so often. As David Scheiffler wrote in his X11 book: "It is as important to decide what a system is not as to decide what it is. Do not serve all the world's needs; rather, make the system extensible so that additional needs can be met in an upwardly compatible fashion." Poul-Henning PS: Anyone with a i386 box is welcome to send me email if they want a copy of 386bsd and the patchkit -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 14:17:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 4FDD637B400; Sun, 14 Jan 2001 14:17:25 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0EMFM964229; Sun, 14 Jan 2001 14:15:22 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Jan 2001 14:15:22 -0800 (PST) From: Matt Dillon Message-Id: <200101142215.f0EMFM964229@earth.backplane.com> To: Poul-Henning Kamp Cc: Andrea Campi , developer@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf GENERIC References: <31573.979509396@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :If nobody has the hardware to test it on, *and* the inclination :to do so, it will not get tested, and the code will erode as a :result. : :I have a 386SX/20 CPU, but I'll be damned if I can be bothered :to boot FreeBSD-current on it, in fact it didn't even boot :a 4.x last I tried. : :Any feature can survive in FreeBSD if sufficient manpower is spent :maintaining it: If you came in with 10 dedicated and able hackers, :you could get a VAX-11 architecture into FreeBSD. : :If you can muster the people needed to write the increasinly quirky :assembler code replacements for features the i386 CPU doesn't have :I'm sure you can keep the i386 alive for some years. :... I'll just point out here that the situation we wind up placing ourselves in re: keeping the 386 support capability, but removing it from GENERIC, is no different from the (positive) situation we place ourselves in when we slow or stop support for older releases after rolling newer ones. There are still people actively using 2.2.x, and even more people using 3.x. But the development community as a whole does not bother to do full compatibility testing of their work when MFCing to 3.x or 2.2.x any more. Most in fact don't MFC bug fixes to 2.2.x or 3.x at all. There is nothing wrong with this, just as there is nothing wrong with leaving the 386 cpu support intact as long as it does not interfere with current work. All that is happening here is that the burden of continuing support for these older releases and cpu's shifts from the development community to the people still actively using those systems. This is entirely reasonable. There is no reason for us to gratuitously rip out support for anything that might still be in active use, even if we are no longer actively developing for it. As long as the support in question does not interfere with our own work, we might as well leave it intact. In fact, I think many of our customers rest easy at night knowing that some level of support still exists for these older releases, that they can continue to support the older releases themselves, and that nobody is intentionally trying to nix the support. - I'm going to leave you all with an anectdote. When Motorola finally decided to stop manufacturing non-integrated 68000 core's some of their largest customers (who were still using the core's) asked motorola to re-specify the timing and frequency limits. You see, even though the design was old Motorola was producing the 68000 core's with modern chip fabs, but all the timing specs were 15 years old. Many of their customers were actually running the chips at higher frequencies then spec because, well, it seemed to work just fine. Motorola tested the 68000 core and found that they could operate a 12.5 MHz 68000 core at 60+ MHz before it crapped out. This delighted Motorola's customers. Despite its age, the 386 has a number of things going for it. You can produce it extremely cheaply as part of a larger chip, and you can run such 386 implementations much faster then you would think. The 386 may be dead to the consumer world, but it's still kicking away in the embedded world - and it isn't just because there are rad-hard versions of it available. The 486 has only just recently started to supplant the 386 in the embedded and aerospace worlds. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 14:26:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 0132137B400; Sun, 14 Jan 2001 14:26:18 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id JAA17573; Mon, 15 Jan 2001 09:25:48 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01JYXJDWNLM8GKTV7E@cim.alcatel.com.au>; Mon, 15 Jan 2001 09:25:54 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id f0EMPjd16508; Mon, 15 Jan 2001 09:25:45 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Mon, 15 Jan 2001 09:25:45 +1100 From: Peter Jeremy Subject: Re: Atomic breakage? In-reply-to: <200101142102.f0EL2OI25280@gratis.grondar.za>; from mark@grondar.za on Sun, Jan 14, 2001 at 11:02:28PM +0200 To: Mark Murray Cc: jhb@FreeBSD.ORG, current@FreeBSD.ORG Mail-followup-to: Mark Murray , jhb@FreeBSD.ORG, current@FreeBSD.ORG Message-id: <20010115092544.U91029@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <200101142102.f0EL2OI25280@gratis.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-14 23:02:28 +0200, Mark Murray wrote: >Hi John > >There seems to be same breakage in the atomic stuff: > >link_elf: symbol atomic_load_acq_int undefined >KLD file random.ko - could not finalize loading > >I back out the latest commit to sys/i386/include/atomic.h, and things >work a bit better (on my laptop). Basically, the problem is that some of the recent commits have broken the interface between sys/i386/include/atomic.h and sys/i386/i386/atomic.c The latter file builds non-inlined versions of the atomic functions defined in atomic.h. This means that atomic.h must be laid out in a suitable manner so that the non-inlined functions are built by atomic.c. (Modules use explicit function calls, rather than inlined atomic functions to remove the need to have distinct UP and SMP versions.) The layout of atomic.h should look like: #ifdef KLD_MODULE #defines expanding to prototypes. #else #defines expanding to inline function definitions #endif List of atomic functions (invoking above macros) Due to incompatibilities between __asm in different versions of gcc, several different versions of various macros (and expansions) are necessary. atomic.c will include atomic.h with "static" and "__inline" #define'd to nothing to build a set of atomic functions with external visibility. The problem is that over time, atomic.h has been expanded and things have gotten a bit confused. Mark's reported breakage is a result of the new atomic_cmpset_int(). This has been defined in the !KLD_MODULE section (but only for new versions of gcc - which should be OK since it'll never be used in conjunction with the old gcc) and a suitable prototype has been inserted in the KLD_MODULE section. The problem is that a pile of #defines have been incorrectly put in this section, rather than outside the KLD_MODULE section. This means that modules are left with dangling references to these functions. Two (untested) patches are attached, the first is simpler (and equivalent to the current code), but I think it will report type mismatches. And for BDE's benefit - atomic.h is broken for IA32's with 64-bit longs. (I believe that can be fixed for Pentiums and above using CMPXCHG8B, but I can't test the code). Index: atomic.h =================================================================== RCS file: /home/CVSROOT/src/sys/i386/include/atomic.h,v retrieving revision 1.16 diff -u -r1.16 atomic.h --- atomic.h 2000/10/28 00:28:15 1.16 +++ atomic.h 2001/01/14 22:14:31 @@ -151,12 +151,6 @@ } #endif /* defined(I386_CPU) */ -#define atomic_cmpset_long atomic_cmpset_int -#define atomic_cmpset_acq_int atomic_cmpset_int -#define atomic_cmpset_rel_int atomic_cmpset_int -#define atomic_cmpset_acq_long atomic_cmpset_acq_int -#define atomic_cmpset_rel_long atomic_cmpset_rel_int - #else /* gcc <= 2.8 version */ #define ATOMIC_ASM(NAME, TYPE, OP, V) \ @@ -222,6 +216,12 @@ #undef ATOMIC_ASM +#define atomic_cmpset_long atomic_cmpset_int +#define atomic_cmpset_acq_int atomic_cmpset_int +#define atomic_cmpset_rel_int atomic_cmpset_int +#define atomic_cmpset_acq_long atomic_cmpset_acq_int +#define atomic_cmpset_rel_long atomic_cmpset_rel_int + #ifndef WANT_FUNCTIONS #define ATOMIC_ACQ_REL(NAME, TYPE) \ static __inline void \ Index: atomic.h =================================================================== RCS file: /home/CVSROOT/src/sys/i386/include/atomic.h,v retrieving revision 1.16 diff -u -r1.16 atomic.h --- atomic.h 2000/10/28 00:28:15 1.16 +++ atomic.h 2001/01/14 22:20:30 @@ -151,12 +151,6 @@ } #endif /* defined(I386_CPU) */ -#define atomic_cmpset_long atomic_cmpset_int -#define atomic_cmpset_acq_int atomic_cmpset_int -#define atomic_cmpset_rel_int atomic_cmpset_int -#define atomic_cmpset_acq_long atomic_cmpset_acq_int -#define atomic_cmpset_rel_long atomic_cmpset_rel_int - #else /* gcc <= 2.8 version */ #define ATOMIC_ASM(NAME, TYPE, OP, V) \ @@ -223,6 +217,22 @@ #undef ATOMIC_ASM #ifndef WANT_FUNCTIONS + +static __inline long +atomic_cmpset_long(volatile u_long *dst, u_long exp, u_long src) +{ + return (atomic_cmpset_int((volatile u_int *)dst, (u_int)exp, (u_int)src)); +} + +#define atomic_cmpset_acq_int(dst, exp, src) \ + atomic_cmpset_int(dst, exp, src) +#define atomic_cmpset_rel_int(dst, exp, src) \ + atomic_cmpset_int(dst, exp, src) +#define atomic_cmpset_acq_long(dst, exp, src) \ + atomic_cmpset_long(dst, exp, src) +#define atomic_cmpset_rel_long(dst, exp, src) \ + atomic_cmpset_long(dst, exp, src) + #define ATOMIC_ACQ_REL(NAME, TYPE) \ static __inline void \ atomic_##NAME##_acq_##TYPE(volatile u_##TYPE *p, u_##TYPE v)\ 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 14 15:21:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 8D45037B400; Sun, 14 Jan 2001 15:20:56 -0800 (PST) Received: from monrovia-31.budapest.interware.hu ([195.70.53.223] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14HwSD-0001dS-00; Mon, 15 Jan 2001 00:20:53 +0100 Message-ID: <3A6233E7.E47F2E04@elischer.org> Date: Sun, 14 Jan 2001 15:19:03 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP! New netgraph code coming References: <3A5567A7.A11F47E3@elischer.org> <3A566BCB.BFD6FA2D@elischer.org> <7m1yu9mdlt.wl@waterblue.imgsrc.co.jp> <3A5F1788.9AD8509A@elischer.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Julian Elischer writes: > > Jun Kuriyama wrote: > > > # kldload ng_bridge > > > kldload: can't load ng_bridge: Exec format error > > > And /var/log/messages says: > > > > > > Jan 12 16:27:07 waterblue /boot/kernel/kernel: KLD ng_bridge.ko: depends on ng_ether - not available > > > > something is terribly broken with the kld loading at the moment. > > Something is terribly broken with ng_ether at the moment. It lacks a > MODULE_VERSION line. hmmmm is this required for something to be a depency? Where is it documented? > > DES > -- > Dag-Erling Smorgrav - des@ofug.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 15:54:16 2001 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 43FC537B402; Sun, 14 Jan 2001 15:53:55 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id AAA24613; Mon, 15 Jan 2001 00:53:45 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Julian Elischer Cc: Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP! New netgraph code coming References: <3A5567A7.A11F47E3@elischer.org> <3A566BCB.BFD6FA2D@elischer.org> <7m1yu9mdlt.wl@waterblue.imgsrc.co.jp> <3A5F1788.9AD8509A@elischer.org> <3A6233E7.E47F2E04@elischer.org> From: Dag-Erling Smorgrav Date: 15 Jan 2001 00:53:45 +0100 In-Reply-To: Julian Elischer's message of "Sun, 14 Jan 2001 15:19:03 -0800" 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 Julian Elischer writes: > Dag-Erling Smorgrav wrote: > > Something is terribly broken with ng_ether at the moment. It lacks a > > MODULE_VERSION line. > is this required for something to be a depency? Yes. > Where is it documented? It's not, AFAIK. UTSL (like the rest of us) DES -- Dag-Erling Smorgrav - des@ofug.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 14 16:27: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id BE5DA37B400 for ; Sun, 14 Jan 2001 16:26:41 -0800 (PST) Received: (qmail 4806 invoked by uid 1000); 15 Jan 2001 00:20:26 -0000 Date: Mon, 15 Jan 2001 01:20:26 +0100 From: Andrea Campi To: Poul-Henning Kamp Cc: developer@freebsd.org, current@freebsd.org Subject: Re: cvs commit: src/sys/i386/conf GENERIC Message-ID: <20010115012026.B4504@webcom.it> References: <20010114221651.A3627@webcom.it> <31573.979509396@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <31573.979509396@critter>; from phk@critter.freebsd.dk on Sun, Jan 14, 2001 at 10:56:36PM +0100 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Sorry Poul, I think the question here is: "if we decide to remove i386 support > >BUT a few people still want to use it and can maintain it as a separate > >platform port, is it an option to do so, from a technical point of view?" > > > (This is a general answer, not just about i386 support:) > > Any feature in FreeBSD needs a minimum amount of maintenance. If > nobody cares about some particular bit of code, it will slowly of > quickly rot away. Sure, but my question was different. I wrote "want to use it and can maintain". I was asking, if somebody is willing enough, is it feasible to split it to a separate arch, and put it under that person's maintainership? Of course, if nobody is willing to do this, then obviously it's not worth it, I agree. And no, I'm not volunteering ;-) > The reason against doing so is that it complicates our code. Makes > it less readable. Forces us to make tradeoffs which hits modern > hardware on the performance meter. Agree. But splitting it out is a one time job, I don't think it would be that hard, and after that you can delete old code from x86 tree, and let x386 tree live its own life... Bye, Andrea -- If Bill Gates had a dime for every time a Windows box crashed... ...Oh, wait a minute, he already does. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 16:38:24 2001 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 E147C37B400; Sun, 14 Jan 2001 16:38:06 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id BAA29067; Mon, 15 Jan 2001 01:38:01 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Andrea Campi Cc: Poul-Henning Kamp , developer@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf GENERIC References: <20010114221651.A3627@webcom.it> <31573.979509396@critter> <20010115012026.B4504@webcom.it> From: Dag-Erling Smorgrav Date: 15 Jan 2001 01:38:00 +0100 In-Reply-To: Andrea Campi's message of "Mon, 15 Jan 2001 01:20:26 +0100" Message-ID: Lines: 6 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 I'm tempted to suggest that the freebsd-small and / or PicoBSD gang would be the right people to ask to maintain i386 support in FreeBSD. DES -- Dag-Erling Smorgrav - des@ofug.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 14 17: 5:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 22D5837B400 for ; Sun, 14 Jan 2001 17:05:35 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0F15Lx30751; Sun, 14 Jan 2001 17:05:21 -0800 (PST) (envelope-from obrien) Date: Sun, 14 Jan 2001 17:05:20 -0800 From: "David O'Brien" To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Atomic breakage? Message-ID: <20010114170520.B30588@dragon.nuxi.com> Reply-To: freebsd-current@FreeBSD.ORG References: <200101142102.f0EL2OI25280@gratis.grondar.za> <20010115092544.U91029@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010115092544.U91029@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Mon, Jan 15, 2001 at 09:25:45AM +1100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 09:25:45AM +1100, Peter Jeremy wrote: > Due to incompatibilities between __asm in different versions of gcc, > several different versions of various macros (and expansions) are > necessary. Why is that?? The base, and *only* supported compiler for building kernels is GCC 2.95.x, period. GCC 2.8 and 2.7 support should be garbage collected. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 17:23:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 6B60C37B400; Sun, 14 Jan 2001 17:23:00 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id MAA07003; Mon, 15 Jan 2001 12:22:57 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01JYXPKH8OO0GKTW3J@cim.alcatel.com.au>; Mon, 15 Jan 2001 12:23:01 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id f0F1Mou17166; Mon, 15 Jan 2001 12:22:50 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Mon, 15 Jan 2001 12:22:50 +1100 From: Peter Jeremy Subject: Re: Atomic breakage? In-reply-to: <20010114170520.B30588@dragon.nuxi.com>; from TrimYourCc@NUXI.com on Sun, Jan 14, 2001 at 05:05:20PM -0800 To: freebsd-current@FreeBSD.ORG Cc: current@FreeBSD.ORG Mail-followup-to: freebsd-current@FreeBSD.ORG, current@FreeBSD.ORG Message-id: <20010115122250.Y91029@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <200101142102.f0EL2OI25280@gratis.grondar.za> <20010115092544.U91029@gsmx07.alcatel.com.au> <20010114170520.B30588@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-14 17:05:20 -0800, David O'Brien wrote: >On Mon, Jan 15, 2001 at 09:25:45AM +1100, Peter Jeremy wrote: >> Due to incompatibilities between __asm in different versions of gcc, >> several different versions of various macros (and expansions) are >> necessary. > >Why is that?? The base, and *only* supported compiler for building >kernels is GCC 2.95.x, period. GCC 2.8 and 2.7 support should be garbage >collected. Feel free to delete it. It was added during the transition period (when we were migrating away from 2.7), but was never cleaned out. The (untested) patch is: Index: atomic.h =================================================================== RCS file: /home/CVSROOT/src/sys/i386/include/atomic.h,v retrieving revision 1.16 diff -u -r1.16 atomic.h --- atomic.h 2000/10/28 00:28:15 1.16 +++ atomic.h 2001/01/15 01:15:39 @@ -84,8 +84,6 @@ * The assembly is volatilized to demark potential before-and-after side * effects if an interrupt or SMP collision were to occur. */ -#if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ > 9) -/* egcs 1.1.2+ version */ #define ATOMIC_ASM(NAME, TYPE, OP, V) \ static __inline void \ atomic_##NAME##_##TYPE(volatile u_##TYPE *p, u_##TYPE v)\ @@ -157,24 +155,8 @@ #define atomic_cmpset_acq_long atomic_cmpset_acq_int #define atomic_cmpset_rel_long atomic_cmpset_rel_int -#else -/* gcc <= 2.8 version */ -#define ATOMIC_ASM(NAME, TYPE, OP, V) \ -static __inline void \ -atomic_##NAME##_##TYPE(volatile u_##TYPE *p, u_##TYPE v)\ -{ \ - __asm __volatile(MPLOCKED OP \ - : "=m" (*p) \ - : "ir" (V)); \ -} \ - \ - -#endif #endif /* KLD_MODULE */ -#if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ > 9) - -/* egcs 1.1.2+ version */ ATOMIC_ASM(set, char, "orb %b2,%0", v) ATOMIC_ASM(clear, char, "andb %b2,%0", ~v) ATOMIC_ASM(add, char, "addb %b2,%0", v) @@ -194,31 +176,6 @@ ATOMIC_ASM(clear, long, "andl %2,%0", ~v) ATOMIC_ASM(add, long, "addl %2,%0", v) ATOMIC_ASM(subtract, long, "subl %2,%0", v) - -#else - -/* gcc <= 2.8 version */ -ATOMIC_ASM(set, char, "orb %1,%0", v) -ATOMIC_ASM(clear, char, "andb %1,%0", ~v) -ATOMIC_ASM(add, char, "addb %1,%0", v) -ATOMIC_ASM(subtract, char, "subb %1,%0", v) - -ATOMIC_ASM(set, short, "orw %1,%0", v) -ATOMIC_ASM(clear, short, "andw %1,%0", ~v) -ATOMIC_ASM(add, short, "addw %1,%0", v) -ATOMIC_ASM(subtract, short, "subw %1,%0", v) - -ATOMIC_ASM(set, int, "orl %1,%0", v) -ATOMIC_ASM(clear, int, "andl %1,%0", ~v) -ATOMIC_ASM(add, int, "addl %1,%0", v) -ATOMIC_ASM(subtract, int, "subl %1,%0", v) - -ATOMIC_ASM(set, long, "orl %1,%0", v) -ATOMIC_ASM(clear, long, "andl %1,%0", ~v) -ATOMIC_ASM(add, long, "addl %1,%0", v) -ATOMIC_ASM(subtract, long, "subl %1,%0", v) - -#endif #undef ATOMIC_ASM 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 14 17:23:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 6B60C37B400; Sun, 14 Jan 2001 17:23:00 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id MAA07003; Mon, 15 Jan 2001 12:22:57 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01JYXPKH8OO0GKTW3J@cim.alcatel.com.au>; Mon, 15 Jan 2001 12:23:01 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id f0F1Mou17166; Mon, 15 Jan 2001 12:22:50 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Mon, 15 Jan 2001 12:22:50 +1100 From: Peter Jeremy Subject: Re: Atomic breakage? In-reply-to: <20010114170520.B30588@dragon.nuxi.com>; from TrimYourCc@NUXI.com on Sun, Jan 14, 2001 at 05:05:20PM -0800 To: freebsd-current@FreeBSD.ORG Cc: current@FreeBSD.ORG Mail-followup-to: freebsd-current@FreeBSD.ORG, current@FreeBSD.ORG Message-id: <20010115122250.Y91029@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <200101142102.f0EL2OI25280@gratis.grondar.za> <20010115092544.U91029@gsmx07.alcatel.com.au> <20010114170520.B30588@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-14 17:05:20 -0800, David O'Brien wrote: >On Mon, Jan 15, 2001 at 09:25:45AM +1100, Peter Jeremy wrote: >> Due to incompatibilities between __asm in different versions of gcc, >> several different versions of various macros (and expansions) are >> necessary. > >Why is that?? The base, and *only* supported compiler for building >kernels is GCC 2.95.x, period. GCC 2.8 and 2.7 support should be garbage >collected. Feel free to delete it. It was added during the transition period (when we were migrating away from 2.7), but was never cleaned out. The (untested) patch is: Index: atomic.h =================================================================== RCS file: /home/CVSROOT/src/sys/i386/include/atomic.h,v retrieving revision 1.16 diff -u -r1.16 atomic.h --- atomic.h 2000/10/28 00:28:15 1.16 +++ atomic.h 2001/01/15 01:15:39 @@ -84,8 +84,6 @@ * The assembly is volatilized to demark potential before-and-after side * effects if an interrupt or SMP collision were to occur. */ -#if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ > 9) -/* egcs 1.1.2+ version */ #define ATOMIC_ASM(NAME, TYPE, OP, V) \ static __inline void \ atomic_##NAME##_##TYPE(volatile u_##TYPE *p, u_##TYPE v)\ @@ -157,24 +155,8 @@ #define atomic_cmpset_acq_long atomic_cmpset_acq_int #define atomic_cmpset_rel_long atomic_cmpset_rel_int -#else -/* gcc <= 2.8 version */ -#define ATOMIC_ASM(NAME, TYPE, OP, V) \ -static __inline void \ -atomic_##NAME##_##TYPE(volatile u_##TYPE *p, u_##TYPE v)\ -{ \ - __asm __volatile(MPLOCKED OP \ - : "=m" (*p) \ - : "ir" (V)); \ -} \ - \ - -#endif #endif /* KLD_MODULE */ -#if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ > 9) - -/* egcs 1.1.2+ version */ ATOMIC_ASM(set, char, "orb %b2,%0", v) ATOMIC_ASM(clear, char, "andb %b2,%0", ~v) ATOMIC_ASM(add, char, "addb %b2,%0", v) @@ -194,31 +176,6 @@ ATOMIC_ASM(clear, long, "andl %2,%0", ~v) ATOMIC_ASM(add, long, "addl %2,%0", v) ATOMIC_ASM(subtract, long, "subl %2,%0", v) - -#else - -/* gcc <= 2.8 version */ -ATOMIC_ASM(set, char, "orb %1,%0", v) -ATOMIC_ASM(clear, char, "andb %1,%0", ~v) -ATOMIC_ASM(add, char, "addb %1,%0", v) -ATOMIC_ASM(subtract, char, "subb %1,%0", v) - -ATOMIC_ASM(set, short, "orw %1,%0", v) -ATOMIC_ASM(clear, short, "andw %1,%0", ~v) -ATOMIC_ASM(add, short, "addw %1,%0", v) -ATOMIC_ASM(subtract, short, "subw %1,%0", v) - -ATOMIC_ASM(set, int, "orl %1,%0", v) -ATOMIC_ASM(clear, int, "andl %1,%0", ~v) -ATOMIC_ASM(add, int, "addl %1,%0", v) -ATOMIC_ASM(subtract, int, "subl %1,%0", v) - -ATOMIC_ASM(set, long, "orl %1,%0", v) -ATOMIC_ASM(clear, long, "andl %1,%0", ~v) -ATOMIC_ASM(add, long, "addl %1,%0", v) -ATOMIC_ASM(subtract, long, "subl %1,%0", v) - -#endif #undef ATOMIC_ASM 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 14 17:28:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from burdell.cc.gatech.edu (burdell.cc.gatech.edu [130.207.3.207]) by hub.freebsd.org (Postfix) with ESMTP id 5B94237B400 for ; Sun, 14 Jan 2001 17:28:16 -0800 (PST) Received: from felix.cc.gatech.edu (felix.cc.gatech.edu [130.207.107.11]) by burdell.cc.gatech.edu (8.9.1/8.9.1) with ESMTP id UAA16287 for ; Sun, 14 Jan 2001 20:28:15 -0500 (EST) Received: from localhost (dibble@localhost) by felix.cc.gatech.edu (8.9.3+Sun/8.9.1) with ESMTP id UAA17597 for ; Sun, 14 Jan 2001 20:28:14 -0500 (EST) Date: Sun, 14 Jan 2001 20:28:14 -0500 (EST) From: Dibble To: freebsd-current@freebsd.org Subject: latest buildkernel 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 just updated my source tree and ran make buildkernel, and it runs until it gets to removing the old GENERIC directory in the /usr/obj/ tree. Just after it removes that directory, I get this error: ../../conf/files coda/coda_fbsd.c must be optional, mandatory or standard ** error code 1 stop in /usr/src **error code 1 stop in /usr/src What can I do to fix this and get the new kernel to build? ########################### Jeff Lee Dibble@cc.gatech.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 17:40: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id 7709E37B400 for ; Sun, 14 Jan 2001 17:39:43 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id RAA15093; Sun, 14 Jan 2001 17:41:00 -0800 Date: Sun, 14 Jan 2001 17:41:00 -0800 From: Kris Kennaway To: Dibble Cc: freebsd-current@FreeBSD.ORG Subject: Re: latest buildkernel Message-ID: <20010114174100.A15053@citusc.usc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from dibble@cc.gatech.edu on Sun, Jan 14, 2001 at 08:28:14PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 14, 2001 at 08:28:14PM -0500, Dibble wrote: > I just updated my source tree and ran make buildkernel, and it runs until > it gets to removing the old GENERIC directory in the /usr/obj/ tree. Just > after it removes that directory, I get this error: >=20 > ../../conf/files coda/coda_fbsd.c must be optional, mandatory or standard You are using a 4.x version of config(8) Kris --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6YlUsWry0BWjoQKURAiIwAKCJARPNoVSlU+lcjL4QXXwNZo/3FACeKVaO vqT2gAmxd8jklUOBClOdwgg= =/trA -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 19: 5:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id 11D7237B400; Sun, 14 Jan 2001 19:05:30 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id TAA15758; Sun, 14 Jan 2001 19:06:44 -0800 Date: Sun, 14 Jan 2001 19:06:44 -0800 From: Kris Kennaway To: Garrett Wollman Cc: current@freebsd.org, markm@freebsd.org Subject: Re: mount_mfs "fix" for entropy hang Message-ID: <20010114190644.C15423@citusc.usc.edu> References: <200101120007.f0C07ib14316@hergotha.lcs.mit.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="eHhjakXzOLJAF9wJ" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200101120007.f0C07ib14316@hergotha.lcs.mit.edu>; from wollman@hergotha.lcs.mit.edu on Thu, Jan 11, 2001 at 07:07:44PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --eHhjakXzOLJAF9wJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I wonder if a better approach might be to make /dev/random return 0 bytes when unseeded, instead of blocking. Then srandomdev() would automatically back down to seeding internally, for example, and no other code changes in mount_mfs would be needed. A warning could be emitted in this case for diagnostic purposes (e.g. in case something actually needs cryptographic randomness and isn't getting it because it's running too early) - this should be the only case when /dev/random returns 0 bytes on a read. Kris On Thu, Jan 11, 2001 at 07:07:44PM -0500, Garrett Wollman wrote: > Index: mkfs.c > =================================================================== > RCS file: /home/ncvs/src/sbin/newfs/mkfs.c,v > retrieving revision 1.32 > diff -u -r1.32 mkfs.c > --- mkfs.c 2000/10/24 03:28:59 1.32 > +++ mkfs.c 2001/01/12 00:05:59 > @@ -192,7 +192,13 @@ > #ifdef FSIRAND > if (!randinit) { > randinit = 1; > - srandomdev(); > + if (mfs) { > + time_t t; > + time(&t); > + srandom(t); > + } else { > + srandomdev(); > + } > } > #endif > if (mfs) { --eHhjakXzOLJAF9wJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6YmlEWry0BWjoQKURAnE3AKDrbTDmcwqFiJIAfA095q86JcFj1ACeNdbR C9HOHVt63yKQI3MlVE2Frr4= =Ulni -----END PGP SIGNATURE----- --eHhjakXzOLJAF9wJ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 21:50:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id BB63C37B400 for ; Sun, 14 Jan 2001 21:50:38 -0800 (PST) Received: (qmail 26719 invoked by uid 0); 15 Jan 2001 05:50:33 -0000 Received: from kmp-147gwx3k96c.kmp-bdi.ac.id (HELO redhat-bsd-server.net) (203.130.236.8) by mail.gmx.net (mail04) with SMTP; 15 Jan 2001 05:50:33 -0000 From: Yosuda Reply-To: Rains@gmx.net To: freebsd-current@FreeBSD.org Date: Mon, 15 Jan 2001 13:54:12 +0800 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <01011513543900.01098@redhat-bsd-server.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 14 23:35:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id D2D8937B400; Sun, 14 Jan 2001 23:35:31 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14I4An-0005wA-00; Mon, 15 Jan 2001 09:35:25 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id JAA19843; Mon, 15 Jan 2001 09:35:23 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 19475; Mon Jan 15 09:34:21 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.20 #1) id 14I49k-0008ry-00; Mon, 15 Jan 2001 09:34:20 +0200 From: Sheldon Hearn To: Dag-Erling Smorgrav Cc: Andrea Campi , Poul-Henning Kamp , developer@freebsd.org, current@freebsd.org Subject: Re: cvs commit: src/sys/i386/conf GENERIC In-reply-to: Your message of "15 Jan 2001 01:38:00 +0100." Date: Mon, 15 Jan 2001 09:34:20 +0200 Message-ID: <34097.979544060@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Jan 2001 01:38:00 +0100, Dag-Erling Smorgrav wrote: > I'm tempted to suggest that the freebsd-small and / or PicoBSD gang > would be the right people to ask to maintain i386 support in FreeBSD. Guys, was Matt Dillon's suggestion infeasible? Can't we keep CPU_I386 support and just make it mutually excllusive with SMP? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 0:10:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail1-gui.server.ntli.net (mail1-gui.server.ntli.net [194.168.222.13]) by hub.freebsd.org (Postfix) with ESMTP id B3B4237B400 for ; Mon, 15 Jan 2001 00:10:25 -0800 (PST) Received: from sunrise.wells.org.uk ([62.253.133.8]) by mail1-gui.server.ntli.net (Post.Office MTA v3.1 release PO203a ID# 0-33929U70000L2S50) with ESMTP id AAA22413 for ; Mon, 15 Jan 2001 08:04:33 +0000 Received: from michael by sunrise.wells.org.uk with local (Exim 3.20 FreeBSD) id 14I4id-00010Y-00 for ; Mon, 15 Jan 2001 08:10:23 +0000 Date: Mon, 15 Jan 2001 08:10:23 +0000 From: Michael Wells To: freebsd-current@FreeBSD.ORG Subject: Re: Soundblaster 64 PCI Message-ID: <20010115081023.B3849@wells.org.uk> Mail-Followup-To: Michael Wells , freebsd-current@FreeBSD.ORG References: <002f01c07e6e$2fe234b0$9204020a@darkstar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002f01c07e6e$2fe234b0$9204020a@darkstar>; from gandalf@vilnya.demon.co.uk on Sun, Jan 14, 2001 at 09:08:47PM -0000 X-PGPkeyserver: wwwkeys.eu.pgp.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Cameron, all, I'm not really tied to any single application. Streaming an .au file from the command line into /dev/dsp does it, mpg123, XMMS...really, the same symptoms everywhere. Any ideas? Michael On Sun, Jan 14, 2001 at 09:08:47PM -0000, Cameron Grant (gandalf@vilnya.demon.co.uk) wrote: > > > If this is a known problem, I'll stop for now and watch out for fixes. > > > If it's not the expected behaviour from the PCM driver though, can > > > anyone advise? > > > > Okay, just checked and it appears tha htis is the same error that I'm > > seeing on mine, as reported yesterday ... not sure if its known or not, > > but its not "just you" ... > > are either of you using esound or xmms? if so, i know the cause of this and > it will be fixed shortly, once my primary development box recovers from > killing its cpu. > > if not, i'll try to reproduce this. > > -cg > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- www.wells.org.uk +44 7715 747252 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 0:11:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id C480237B6A5; Mon, 15 Jan 2001 00:11:10 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0F88CQ01192; Mon, 15 Jan 2001 00:08:13 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101150808.f0F88CQ01192@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Sheldon Hearn Cc: Dag-Erling Smorgrav , Andrea Campi , Poul-Henning Kamp , developer@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf GENERIC In-Reply-To: <34097.979544060@axl.fw.uunet.co.za> Date: Mon, 15 Jan 2001 00:08:12 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > > On 15 Jan 2001 01:38:00 +0100, Dag-Erling Smorgrav wrote: > > > I'm tempted to suggest that the freebsd-small and / or PicoBSD gang > > would be the right people to ask to maintain i386 support in FreeBSD. > > Guys, was Matt Dillon's suggestion infeasible? Can't we keep CPU_I386 > support and just make it mutually excllusive with SMP? Right now it is. But as long as we support a super-kernel that runs on 386's through p3's we've got problems due to the lack of the cmpxchg instruction. ie: the moment you add I386_CPU, we switch to the inefficient instruction sequence: " pushfl ; " " cli ; " " cmpl %1,%3 ; " " jne 1f ; " " movl %2,%3 ; " "1: " " sete %%al; " " movzbl %%al,%0 ; " " popfl ; " .. which disables interrupts... Your 1GHz cpu uses the slower 386-friendly version instead of the optimal 486-and-above sequence: " cmpxchgl %2,%3 ; " " setz %%al ; " " movzbl %%al,%0 ; " The 486-and-above sequence is made MPsafe by adding the lock prefix when compiling under SMP mode. At the very least, we should warn people that they are shooting themselves in the foot if they add I386_CPU to their kernel (eg: copied from RELENG_4) and IMHO we should make the compile fail if you attempt to mix types. The patch below does this: http://people.freebsd.org/~peter/i386_cleanup.diff 1: it removes the 486-and-above code from the 386-only cases. 2: it removes the runtime conditionals that everybody currently executes if I386_CPU is present 3: prevents people shooting themselves in the foot at 'make depend' stage if they accidently activate I386_CPU. To be clear: THIS DOES NOT REMOVE i386 SUPPORT! It will actually slightly improve i386 runtime speed by removing the useless conditional tests. 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 Mon Jan 15 0:59:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from mx1.techconcepts.co.za (ns1.techconcepts.co.za [196.34.2.130]) by hub.freebsd.org (Postfix) with ESMTP id DB90F37B400 for ; Mon, 15 Jan 2001 00:59:02 -0800 (PST) Received: from aerasmus ([10.0.1.80]) by mx1.techconcepts.co.za (8.9.3/8.9.1) with SMTP id KAA07272 for ; Mon, 15 Jan 2001 10:57:58 +0200 Message-ID: <002101c07ed0$d5e313e0$5001000a@jhba.techconcepts.co.za> From: "Adriaan Erasmus" To: "FreeBSD Mailing List" Subject: Problem compiling Date: Mon, 15 Jan 2001 10:54:55 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001E_01C07EE1.9847FD50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_001E_01C07EE1.9847FD50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, My box hangs up solid when recompiling my kernel to add pcm driver. I got the latest src tree though cvsup and I followed the standard = procedure to recompile my new kernel to include pcm I can do a /usr/sbin/config MYNEWKERNEL Then in /usr/src/sys/compile/MYNEWKERNEL I can do make depend -- works = fine, but as soon as I do make, it hangs after 3 miniutes of compiling = ---- WHAT IS WRONG or is there a bug in the latest source ( to do with = pcm ) I have a sound blaster live and I really need to get it working in = FreeBSD=20 Can anyone please help Adriaan Erasmus ------------------------- ------=_NextPart_000_001E_01C07EE1.9847FD50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
My box hangs up solid when recompiling = my kernel to=20 add pcm driver.
I got the latest src tree though cvsup = and I=20 followed the standard procedure to recompile my new kernel to include=20 pcm
 
I can do a /usr/sbin/config=20 MYNEWKERNEL
Then in = /usr/src/sys/compile/MYNEWKERNEL I can do=20 make depend -- works fine, but as soon as I do make, it hangs after 3 = miniutes=20 of compiling ---- WHAT IS WRONG or is there a bug in the latest source ( = to do=20 with pcm )
 
I have a sound blaster live and I = really need to=20 get it working in FreeBSD
 
Can anyone please help
 
Adriaan Erasmus
-------------------------
------=_NextPart_000_001E_01C07EE1.9847FD50-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 2:43:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from cav.logica.co.uk (cav.logica.co.uk [158.234.10.66]) by hub.freebsd.org (Postfix) with ESMTP id 33F0237B400 for ; Mon, 15 Jan 2001 02:42:59 -0800 (PST) Received: from eckert.logica.co.uk (eckert.logica.co.uk [158.234.10.17]) by cav.logica.co.uk (8.9.1/8.9.1) with ESMTP id KAA10499; Mon, 15 Jan 2001 10:42:54 GMT Received: by eckert.logica.co.uk with Internet Mail Service (5.5.2448.0) id ; Mon, 15 Jan 2001 10:42:49 -0000 Message-ID: From: "Newton, Harry" To: "'Gerhard Sittig '" , "'freebsd-current@freebsd.org'" Subject: Re: Crash dumps during initialisation Date: Mon, 15 Jan 2001 10:42:46 -0000 X-Mailer: Internet Mail Service (5.5.2448.0) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think we might be talking at cross-purposes here. What does the kernel do if it panics before the /etc/rc script is run ? (i.e. before the dumpon command is issued ). I can't believe that it reads /etc/rc.conf and locates the dump_dev entry to determine where it should put the crash dump. In 4.4BSD one could specify: config kernel root on swap on dump on but this no longer exists in FreeBSD ? Is this right, and why ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 3: 5:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 9402137B400 for ; Mon, 15 Jan 2001 03:05:15 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0FB4vY01616; Mon, 15 Jan 2001 03:04:57 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101151104.f0FB4vY01616@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Newton, Harry" Cc: "'Gerhard Sittig '" , "'freebsd-current@freebsd.org'" Subject: Re: Crash dumps during initialisation In-Reply-To: Date: Mon, 15 Jan 2001 03:04:56 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Newton, Harry" wrote: > I think we might be talking at cross-purposes here. What does the kernel do > if it panics before the /etc/rc script is run ? (i.e. before the dumpon > command is issued ). I can't believe that it reads /etc/rc.conf and locates > the dump_dev entry to determine where it should put the crash dump. In > 4.4BSD one could specify: > > config kernel root on swap on dump on > > but this no longer exists in FreeBSD ? Is this right, and why ? We are missing some infrastructure to get this to work really early in the boot sequence - how early do you need? It should be possible to come up with some tweaks so that we can dump right after the device that we want to dump to has probed its disk label to get the partition sizes etc. Exactly when this happens is something I am not yet sure of. With some tweaks it should be moderately easy to get dumps enabled at the point where boot -v says "Creating DISK xxx" and your dump device is shown.. at least for drivers that use the minidisk layer. 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 Mon Jan 15 3:29:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from sina.com (unknown [202.106.187.156]) by hub.freebsd.org (Postfix) with SMTP id D289B37B69D for ; Mon, 15 Jan 2001 03:29:21 -0800 (PST) Received: (qmail 42883 invoked from network); 15 Jan 2001 11:23:50 -0000 Received: from unknown (HELO localhost) (202.105.12.29) by 202.106.187.156 with SMTP; 15 Jan 2001 11:23:50 -0000 X-Sender: hangersales@sina.com From: Trend Hanger To: current@freebsd.org Date: Mon, 15 Jan 2001 19:28:15 +0800 Subject: We are exporting quality Hanger for cloth, pants Reply-To: hangersales@sina.com Organization: Trend Hanger Co. MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20010115112921.D289B37B69D@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sir or Madam, Happy New Year! Here we send all the best wish to you. Trend Hanger, as a professional hanger manufacturer in China specializes in producing and designing various kinds of non-slip coated and chrome-plated metal frame clothes hangers. The company has been in the business for almost 10 years now. With experienced staff and workers, we always provide our customers from all over the world with good service, excellent quality and competitively-priced products. Today, people care a lot about environmental protection, and more and more people would choose to use low-waste materials, impressive and well-designed products. We are proud to say ours are among them. For this reason, during the past several years our selling records are quite well, and now the business is growing even faster than before--simply because our series of products are proven to be reliable and worthwhile in our consumers' eyes. Furthermore, we always observe a strict quality control system all throughout our production process. Each product must be carefully examined and tested in each stage so as to ensure excellent quality and nice packing order for our customers. If you are interested in our products, please do not hesitate to contact us. We are anxious to establish long-term, equal and mutual beneficial business relationship with you. Best wishes, Trend Hanger Manufacturer Contact Person: Mr Steve, Phoenix Sales Manager Zhen An Industrial Zone, Foshan City, Guangdong Province, China 528000 Tel: (86 757) 3982666 Fax: (86 757) 2282667 Email: brianced@21cn.com http://www.bosunnet.com/trendhanger/index/contacts.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 15 3:30:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from sina.com (unknown [202.106.187.156]) by hub.freebsd.org (Postfix) with SMTP id 2168937B698 for ; Mon, 15 Jan 2001 03:30:14 -0800 (PST) Received: (qmail 43372 invoked from network); 15 Jan 2001 11:24:39 -0000 Received: from unknown (HELO localhost) (202.105.12.29) by 202.106.187.156 with SMTP; 15 Jan 2001 11:24:39 -0000 X-Sender: hangersales@sina.com From: Trend Hanger To: freebsd-current@FreeBSD.org Date: Mon, 15 Jan 2001 19:29:04 +0800 Subject: We are exporting quality Hanger for cloth, pants Reply-To: hangersales@sina.com Organization: Trend Hanger Co. MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20010115113014.2168937B698@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sir or Madam, Happy New Year! Here we send all the best wish to you. Trend Hanger, as a professional hanger manufacturer in China specializes in producing and designing various kinds of non-slip coated and chrome-plated metal frame clothes hangers. The company has been in the business for almost 10 years now. With experienced staff and workers, we always provide our customers from all over the world with good service, excellent quality and competitively-priced products. Today, people care a lot about environmental protection, and more and more people would choose to use low-waste materials, impressive and well-designed products. We are proud to say ours are among them. For this reason, during the past several years our selling records are quite well, and now the business is growing even faster than before--simply because our series of products are proven to be reliable and worthwhile in our consumers' eyes. Furthermore, we always observe a strict quality control system all throughout our production process. Each product must be carefully examined and tested in each stage so as to ensure excellent quality and nice packing order for our customers. If you are interested in our products, please do not hesitate to contact us. We are anxious to establish long-term, equal and mutual beneficial business relationship with you. Best wishes, Trend Hanger Manufacturer Contact Person: Mr Steve, Phoenix Sales Manager Zhen An Industrial Zone, Foshan City, Guangdong Province, China 528000 Tel: (86 757) 3982666 Fax: (86 757) 2282667 Email: brianced@21cn.com http://www.bosunnet.com/trendhanger/index/contacts.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 15 4:18:16 2001 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 B13A037B699; Mon, 15 Jan 2001 04:17:56 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id XAA01685; Mon, 15 Jan 2001 23:17:52 +1100 Date: Mon, 15 Jan 2001 23:17:19 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: Jordan Hubbard , current@FreeBSD.ORG Subject: RE: Anybody else seeing a broken /dev/lpt with SMP on -current? 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, 12 Jan 2001, John Baldwin wrote: > On 13-Jan-01 Jordan Hubbard wrote: > > I've actually been seeing this for about 2 months now but only just > > now got motivated enough to enable crashdumps and get some information > > on what happens whenver I try to use the printer attached to my (sadly :) > > -current SMP box: > > > > IdlePTD 3682304 > > initial pcb at 2e70e0 > > panicstr: page fault > > panic messages: > > --- > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; lapic.id = 00000000 > > fault virtual address = 0xffff8640 > > fault code = supervisor write, page not present > > instruction pointer = 0x8:0xc8dc8676 > > stack pointer = 0x10:0xc8280f88 > > frame pointer = 0x10:0xc8280f9c > > 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 = 12322 (irq7: lpt0) > > trap number = 12 > > panic: page fault > > cpuid = 0; lapic.id = 00000000 > > boot() called on cpu#0 > > > > If anybody wants a fuller traceback then I'll compile up a kernel with > > debugging symbols, but it's going to be pretty sparse anyway since it > > basically only shows the trap() from the page fault and the subsequent > > panic. > > All the other traces show the kerenl having returned to an address that is > beyongd the end of the kernel (which causes the page fault) meaning that the > stack is fubar'd, so the trace isn't meaningful anyways. :( Knowing how and > why the lpd interrupt handler trashes the stack is the useful info, and with > teh stack already trashed, I don't know of an easy way to figure that out. > Suggestions welcome. This may be cause by the lpt driver (ab)using BUS_SETUP_INTR() on every write(). The interrupt system can't handle this. I noticed the following symptoms: - stray irq7's from when the driver interrupt isn't attached (BUS_SETUP_INTR() for ppbus first tears down any previously set up handler). - under UP, a slow memory leak from not freeing ih_name in inthand_remove(). Fixed in the enclosed patch. - under SMP with 1 cpu, panics in various places due to the process table filling up with undead ithreads. Worked around in the enclosed patch. This bug should go away almost automatically when interrupt handling actually works. Use something like "dd if=/dev/zero of=/dev/lpt0 bs=1" to see this bug. Use a small value for kern.maxproc to see it quickly. - "cp /dev/zero /dev/lpt0 &" caused about 50% interrupt overhead. Under UP, interactive response was not noticeably affected, but under SMP with 1 cpu, echoing of keystrokes in /bin/sh in single user mode took a few hundred msec. Index: dev/ppbus/lpt.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ppbus/lpt.c,v retrieving revision 1.20 diff -c -2 -r1.20 lpt.c *** dev/ppbus/lpt.c 2000/12/07 22:33:12 1.20 --- dev/ppbus/lpt.c 2001/01/15 02:44:40 *************** *** 70,73 **** --- 70,76 ---- #include #include + #include + #include + #include #include #include *************** *** 759,762 **** --- 762,797 ---- device_printf(lptdev, "handler registration failed, polled mode.\n"); sc->sc_irq &= ~LP_USE_IRQ; + } + + /* + * XXX setting up interrupts is a very expensive operation and + * shouldn't be done here. Despite its name, BUS_SETUP_INTR() + * for this bus both sets up and tears down interrupts (it + * first tears down any already-setup interrupt). This + * involves exiting from any existing ithread and starting a + * new one. The exit is done lazily, and at least under SMP, + * writing tinygrams resulted in ithreads being created faster + * than they were destroyed, resulting in assorted panics + * depending on where the resource exhaustion was detected. + * + * Yield so that the ithreads get a chance to exit. + * + * XXX following grot cloned from uio_yield(). + */ + { + struct proc *p; + int s; + + p = curproc; + s = splhigh(); + mtx_enter(&sched_lock, MTX_SPIN); + DROP_GIANT_NOSWITCH(); + p->p_priority = p->p_usrpri; + setrunqueue(p); + p->p_stats->p_ru.ru_nivcsw++; + mi_switch(); + mtx_exit(&sched_lock, MTX_SPIN); + PICKUP_GIANT(); + splx(s); } } Index: i386/isa/intr_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/intr_machdep.c,v retrieving revision 1.42 diff -c -2 -r1.42 intr_machdep.c *** i386/isa/intr_machdep.c 2000/12/08 21:50:11 1.42 --- i386/isa/intr_machdep.c 2001/01/15 01:27:24 *************** *** 710,713 **** --- 710,714 ---- } } + free(idesc->ih_name, M_DEVBUF); free(idesc, M_DEVBUF); return (0); 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 15 5:44:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from mx1.techconcepts.co.za (ns1.techconcepts.co.za [196.34.2.130]) by hub.freebsd.org (Postfix) with ESMTP id 1710D37B402 for ; Mon, 15 Jan 2001 05:44:28 -0800 (PST) Received: from aerasmus ([10.0.1.80]) by mx1.techconcepts.co.za (8.9.3/8.9.1) with SMTP id PAA25983 for ; Mon, 15 Jan 2001 15:43:24 +0200 Message-ID: <008601c07ef8$b6664a00$5001000a@jhba.techconcepts.co.za> From: "Adriaan Erasmus" To: "FreeBSD Mailing List" Subject: Darn Soundblaster Live :( Date: Mon, 15 Jan 2001 15:39:52 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0077_01C07F09.673EB550" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0077_01C07F09.673EB550 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I still have problems compiling my kernel. All I want to do is add a pcm device I have a Soundblaster Live and I must add a pcm device in my new kernel = config file. Every time I make the thing hangs up. I never had this problem b4 and I = think its has something to do with my CPU choice in my config file so = here is the million dollar question. If I have a Celeron 400 which CPU type should I choose i586 or i686 ???? HELP !!! Adriaan Erasmus --=3D=3D####=3D=3D-- I would change the world,=20 but God would never give=20 me the source code. ------=_NextPart_000_0077_01C07F09.673EB550 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I still have problems compiling my=20 kernel.
All I want to do is add a pcm = device
 
I have a Soundblaster Live and I must = add a pcm=20 device in my new kernel config file.
 
Every time I make the thing hangs up. I = never had=20 this problem b4 and I think its has something to do with my CPU choice = in my=20 config file so here is the million dollar question.
 
If I have a Celeron 400 which CPU type = should I=20 choose
i586 or i686 ????
 
HELP !!!
 
Adriaan Erasmus
--=3D=3D####=3D=3D--
 
I would change the world,
but God = would never=20 give
me the source code.
------=_NextPart_000_0077_01C07F09.673EB550-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 5:51:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 192BB37B6A1 for ; Mon, 15 Jan 2001 05:50:59 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f0FDn0j38329; Mon, 15 Jan 2001 09:49:00 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 15 Jan 2001 09:49:00 -0400 (AST) From: The Hermit Hacker To: Adriaan Erasmus Cc: FreeBSD Mailing List Subject: Re: Darn Soundblaster Live :( In-Reply-To: <008601c07ef8$b6664a00$5001000a@jhba.techconcepts.co.za> 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 try enabling both and seeing if that fixes it? On Mon, 15 Jan 2001, Adriaan Erasmus wrote: > I still have problems compiling my kernel. > All I want to do is add a pcm device > > I have a Soundblaster Live and I must add a pcm device in my new kernel config file. > > Every time I make the thing hangs up. I never had this problem b4 and I think its has something to do with my CPU choice in my config file so here is the million dollar question. > > If I have a Celeron 400 which CPU type should I choose > i586 or i686 ???? > > HELP !!! > > Adriaan Erasmus > --==####==-- > > I would change the world, > but God would never give > me the source code. > 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 Mon Jan 15 6: 3: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from burdell.cc.gatech.edu (burdell.cc.gatech.edu [130.207.3.207]) by hub.freebsd.org (Postfix) with ESMTP id 28DC737B404; Mon, 15 Jan 2001 06:02:52 -0800 (PST) Received: from felix.cc.gatech.edu (felix.cc.gatech.edu [130.207.107.11]) by burdell.cc.gatech.edu (8.9.1/8.9.1) with ESMTP id JAA03557; Mon, 15 Jan 2001 09:02:51 -0500 (EST) Received: from localhost (dibble@localhost) by felix.cc.gatech.edu (8.9.3+Sun/8.9.1) with ESMTP id JAA29800; Mon, 15 Jan 2001 09:02:50 -0500 (EST) Date: Mon, 15 Jan 2001 09:02:50 -0500 (EST) From: Dibble To: Kris Kennaway Cc: freebsd-current@freebsd.org Subject: Re: latest buildkernel In-Reply-To: <20010114183134.A15423@citusc.usc.edu> 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, 14 Jan 2001, Kris Kennaway wrote: > On Sun, Jan 14, 2001 at 08:50:06PM -0500, Dibble wrote: > > How would i go about fixing this? > > Actually build a 5.0 userland, not a 4.x one as you seem to have :-) > Make sure you are following the upgrade instructions precisely, located > in /usr/src/UPDATING. > > Kris > I am still getting an error, but a different one. I am following the directions exactly from /etc/UPDATING. When I make buildkernel, I get: => agp make: don't know how to make @/pci/pcivar.h. Stop ***Error code 2 Stop in /usr/src/sys/modules ***Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC ***Error code 1 Stop in /usr/src ***Error code 1 Stop in /usr/src ########################### Jeff Lee Dibble@cc.gatech.edu Public Key: http://www.prism.gatech.edu/~gte384v/pubkey.acs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 6:39:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id 7230A37B698 for ; Mon, 15 Jan 2001 06:39:35 -0800 (PST) Received: from HP2500B (veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id 294548C13 for ; Mon, 15 Jan 2001 08:38:52 -0600 (CST) Message-ID: <004401c07f00$b86aabe0$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: "FreeBSD-Current, " Subject: Buildworld failure as of 01-15-2001 @ 8:30 CST Date: Mon, 15 Jan 2001 08:37:43 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just installed the FreeBSD 5.0-20010107-CURRENT snapshot and have cvsup'd to the latest source (as of subject). Buildworld fails as below: -------------------------------------------------------------- >>> stage 4: populating /usr/obj/usr/src/i386/usr/include -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/ libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/li b:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexe c PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0 DESTDIR=/usr/obj/usr/s rc/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/ sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bi n:/u sr/sbin:/usr/bin make -f Makefile.inc1 SHARED=symlinks includes cd /usr/src/include; make -B all install creating osreldate.h from newvers.sh setvar PARAMFILE /usr/src/include/../sys/sys/param.h; . /usr/src/include/../sys /conf/newvers.sh; echo "$COPYRIGHT" > osreldate.h; echo \#'undef __FreeBSD_version' >> osreldate.h; echo \#'define __FreeBS D_version' $RELDATE >> osreldate.h ===> rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h rpcgen: cannot find any C preprocessor (cpp) *** Error code 1 Stop in /usr/src/include/rpcsvc. *** Error code 1 Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Tom Veldhouse veldy@veldy.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 15 7:16:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from mx1.techconcepts.co.za (ns1.techconcepts.co.za [196.34.2.130]) by hub.freebsd.org (Postfix) with ESMTP id 7155C37B400 for ; Mon, 15 Jan 2001 07:16:20 -0800 (PST) Received: from aerasmus ([10.0.1.80]) by mx1.techconcepts.co.za (8.9.3/8.9.1) with SMTP id RAA31783 for ; Mon, 15 Jan 2001 17:15:16 +0200 Message-ID: <000e01c07f05$8bf99e90$5001000a@jhba.techconcepts.co.za> From: "Adriaan Erasmus" To: "FreeBSD Mailing List" Subject: Kernel source Date: Mon, 15 Jan 2001 17:12:15 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C07F16.4EAF8E30" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C07F16.4EAF8E30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, As you have noticed, I am a fairly new FreeBSD user, I am a Linux Guru = though but BSD is more powerfull and I tend to use just BSD in the = future. I will post a lot of msg's in the future but I have one question. Where can I find a kernel source tree that will work with my Sound = Blaster Live Sound Card. I run FreeBSD 4.1.1-STABLE and its kernel source doesn't support the pcm = driver ?!? I did upgrade to the latest CURRENT but that just hangs my machine ( = another ?!? ) I am confused - what is the problem with BSD or is it me ? Adriaan Erasmus ------------------------- I would change the world,=20 but God would never give=20 me the source code. ------=_NextPart_000_000B_01C07F16.4EAF8E30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
As you have noticed, I am a fairly new = FreeBSD=20 user, I am a Linux Guru though but BSD is more powerfull and I tend to = use just=20 BSD in the future.
 
I will post a lot of msg's in the = future but I have=20 one question.
Where can I find a kernel source tree = that will=20 work with my Sound Blaster Live Sound Card.
 
I run FreeBSD 4.1.1-STABLE and its = kernel source=20 doesn't support the pcm driver ?!?
 
I did upgrade to the latest CURRENT but = that just=20 hangs my machine ( another ?!? )
 
I am confused - what is the problem = with BSD or is=20 it me ?
 
Adriaan Erasmus
-------------------------
 
I would change the world,
but God = would never=20 give
me the source code.
------=_NextPart_000_000B_01C07F16.4EAF8E30-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 7:58:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from gypsy.vrac.iastate.edu (gypsy.vrac.iastate.edu [129.186.232.122]) by hub.freebsd.org (Postfix) with ESMTP id 784C737B401 for ; Mon, 15 Jan 2001 07:58:30 -0800 (PST) Received: from tomservo.vrac.iastate.edu (tomservo.vrac.iastate.edu [129.186.232.121]) by gypsy.vrac.iastate.edu (Postfix) with ESMTP id 800D611 for ; Mon, 15 Jan 2001 09:58:30 -0600 (CST) Received: from tomservo.vrac.iastate.edu (localhost [127.0.0.1]) by tomservo.vrac.iastate.edu (Postfix) with ESMTP id 780475E16 for ; Mon, 15 Jan 2001 09:58:28 -0600 (CST) To: freebsd-current@FreeBSD.org Subject: Re: console freeze In-reply-to: "Tue, 12 Dec 2000 08:39:32 PST." Date: Mon, 15 Jan 2001 09:58:28 -0600 From: Patrick Hartling Message-Id: <20010115155828.780475E16@tomservo.vrac.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: } } On 12-Dec-00 Nicolas Souchu wrote: } > Hi there, } > } > I did browse the lists but found nothing about my problem. } > Compiling GENERIC of 5.0 works correctly but once I remove } > most of uneeded hardware, the console/kbd freeze. } > } > I join the MACHINE file and the output. } > } > I even tried to change the graphic card to a PCI S3, same. } > } > I can get the getty on the serial line, so I tried vidcontrol -i } > on it. It reports stupid info. } > } > Is there something I can try? } } You haven't setup device hints. You can either statically compile them into } your kernel or copy GENERIC.hints to /boot/device.hints and edit it } appropriately. Has there been any resolution to this? I've been having this problem ever since the SMPng stuff went into the tree. I have no success in getting my splash screen to work anymore or in changing video modes with vidcontrol. The splash_bmp KLD always reports the following: module_register_init: MOD_LOAD (splash_bmp, c037f824, 0) error 2 I have done a careful comparison of GENERIC.hints and the /boot/device.hints that I made back when it became a requirement. I've searched the archives and come up empty. I also read cvs-all faithfully, and while I have gotten backed up on mail due to a short vacation here and there, I haven't seen any related commits. What have I missed in keeping up to date? -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 7:59: 7 2001 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 3E95037B402 for ; Mon, 15 Jan 2001 07:58:48 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0FFwUS07131; Mon, 15 Jan 2001 07:58:30 -0800 (PST) Date: Mon, 15 Jan 2001 07:58:30 -0800 From: Alfred Perlstein To: Adriaan Erasmus Cc: FreeBSD Mailing List Subject: Re: Kernel source Message-ID: <20010115075830.U7240@fw.wintelcom.net> References: <000e01c07f05$8bf99e90$5001000a@jhba.techconcepts.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000e01c07f05$8bf99e90$5001000a@jhba.techconcepts.co.za>; from wokani@flameboy.za.net on Mon, Jan 15, 2001 at 05:12:15PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Adriaan Erasmus [010115 07:17] wrote: > Hi, > > > I will post a lot of msg's in the future but I have one question. > > Where can I find a kernel source tree that will work with my > Sound Blaster Live Sound Card. > > I run FreeBSD 4.1.1-STABLE and its kernel source doesn't support > the pcm driver ?!? > > I did upgrade to the latest CURRENT but that just hangs my machine > ( another ?!? ) ok, oops. -CURRENT isn't really for BSD newbies, what you wanted to do was upgrade to the latest -STABLE: http://www.freebsd.org/handbook/cutting-edge.html (read the entire chapter) > I am confused - what is the problem with BSD or is it me ? Well it's sorta BSD's fault for being a pain with -CURRENT, but it's your fault for running -CURRENT without having the necessary kernel-foo to do so at the moment. :) best of luck, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 9:41: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id BF97637B400 for ; Mon, 15 Jan 2001 09:40:43 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0FHeeJ40241; Mon, 15 Jan 2001 09:40:40 -0800 (PST) (envelope-from obrien) Date: Mon, 15 Jan 2001 09:40:40 -0800 From: "David O'Brien" To: "Thomas T. Veldhouse" Cc: "FreeBSD-Current, " Subject: Re: Buildworld failure as of 01-15-2001 @ 8:30 CST Message-ID: <20010115094040.A40110@dragon.nuxi.com> Reply-To: freebsd-current@freebsd.org References: <004401c07f00$b86aabe0$3028680a@tgt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004401c07f00$b86aabe0$3028680a@tgt.com>; from veldy@veldy.net on Mon, Jan 15, 2001 at 08:37:43AM -0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 08:37:43AM -0600, Thomas T. Veldhouse wrote: > I just installed the FreeBSD 5.0-20010107-CURRENT snapshot and have cvsup'd > to the latest source (as of subject). Buildworld fails as below: Do not manually do anything to get around this yet. Please apply and try this patch. Report here, if it works or not. Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.179 diff -u -r1.179 Makefile.inc1 --- Makefile.inc1 2000/12/03 20:29:31 1.179 +++ Makefile.inc1 2001/01/15 17:39:37 @@ -564,7 +564,7 @@ build-tools: .for _tool in bin/csh bin/sh ${_games} gnu/usr.bin/cc/cc_tools ${_fortran} \ - ${_libroken4} ${_libkrb5} lib/libncurses ${_share} + usr.bin/rpcgen ${_libroken4} ${_libkrb5} lib/libncurses ${_share} cd ${.CURDIR}/${_tool}; ${MAKE} build-tools .endfor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 9:59:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 4167B37B400; Mon, 15 Jan 2001 09:59:06 -0800 (PST) Received: from localhost (IDENT:C9686BhWcmz4H1QofwoGrjiQpMoUG+tiSUlquUCKdDAlWzdFI1GwqruyqTNeBlRt@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.2/8.11.2/peace) with ESMTP/inet6 id f0FHvjw00705; Tue, 16 Jan 2001 02:57:46 +0900 (JST) (envelope-from ume@FreeBSD.org) Date: Tue, 16 Jan 2001 02:57:41 +0900 (JST) Message-Id: <20010116.025742.74757685.ume@FreeBSD.org> To: current@freebsd.org, hackers@freebsd.org Subject: number of processes forked since boot From: Hajimu UMEMOTO X-Mailer: Mew version 1.95b97 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT 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 wish to obtain number of processes forked since boot from userland. So, I made a patch to intend to commit. Any comment? Index: lib/libc/gen/sysctl.3 diff -u lib/libc/gen/sysctl.3.orig lib/libc/gen/sysctl.3 --- lib/libc/gen/sysctl.3.orig Fri Jan 12 02:39:22 2001 +++ lib/libc/gen/sysctl.3 Tue Jan 16 02:13:19 2001 @@ -294,6 +294,7 @@ .It "KERN\_UPDATEINTERVAL integer no" .It "KERN\_VERSION string no" .It "KERN\_VNODE struct vnode no" +.It "KERN\_NFORKS integer no" .El .Pp .Bl -tag -width 6n @@ -445,6 +446,8 @@ .Va struct vnode * followed by the vnode itself .Va struct vnode . +.It Li KERN_NFORKS +Number of processes forked. .El .Ss CTL_MACHDEP The set of variables defined is architecture dependent. Index: sbin/sysctl/sysctl.8 diff -u sbin/sysctl/sysctl.8.orig sbin/sysctl/sysctl.8 --- sbin/sysctl/sysctl.8.orig Fri Jan 12 02:42:23 2001 +++ sbin/sysctl/sysctl.8 Tue Jan 16 02:13:19 2001 @@ -145,6 +145,7 @@ .It "kern.bootfile string yes .It "kern.corefile string yes .It "kern.logsigexit integer yes +.It "kern.nforks integer no .It "vm.loadavg struct no .It "hw.machine string no .It "hw.model string no Index: sys/kern/kern_fork.c diff -u sys/kern/kern_fork.c.orig sys/kern/kern_fork.c --- sys/kern/kern_fork.c.orig Fri Jan 12 02:46:53 2001 +++ sys/kern/kern_fork.c Tue Jan 16 02:30:26 2001 @@ -146,6 +146,9 @@ int nprocs = 1; /* process 0 */ static int nextpid = 0; +static unsigned int nforks = 0; +SYSCTL_UINT(_kern, KERN_NFORKS, nforks, CTLFLAG_RD, &nforks, 0, ""); + /* * Random component to nextpid generation. We mix in a random factor to make * it a little harder to predict. We sanity check the modulus value to avoid @@ -277,6 +280,8 @@ } newproc->p_vmspace = NULL; + + nforks++; /* * Find an unused process ID. We remember a range of unused IDs Index: sys/sys/sysctl.h diff -u sys/sys/sysctl.h.orig sys/sys/sysctl.h --- sys/sys/sysctl.h.orig Fri Jan 12 02:48:41 2001 +++ sys/sys/sysctl.h Tue Jan 16 02:13:19 2001 @@ -328,7 +328,8 @@ #define KERN_PS_STRINGS 32 /* int: address of PS_STRINGS */ #define KERN_USRSTACK 33 /* int: address of USRSTACK */ #define KERN_LOGSIGEXIT 34 /* int: do we log sigexit procs? */ -#define KERN_MAXID 35 /* number of valid kern ids */ +#define KERN_NFORKS 35 /* uint: number of forked */ +#define KERN_MAXID 36 /* number of valid kern ids */ #define CTL_KERN_NAMES { \ { 0, 0 }, \ @@ -366,6 +367,7 @@ { "ps_strings", CTLTYPE_INT }, \ { "usrstack", CTLTYPE_INT }, \ { "logsigexit", CTLTYPE_INT }, \ + { "nforks", CTLTYPE_UINT }, \ } /* -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 10: 6:37 2001 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 6042237B401; Mon, 15 Jan 2001 10:06:18 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0FI6In10517; Mon, 15 Jan 2001 10:06:18 -0800 (PST) Date: Mon, 15 Jan 2001 10:06:18 -0800 From: Alfred Perlstein To: Hajimu UMEMOTO Cc: current@FreeBSD.ORG Subject: Re: number of processes forked since boot Message-ID: <20010115100618.Y7240@fw.wintelcom.net> References: <20010116.025742.74757685.ume@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010116.025742.74757685.ume@FreeBSD.org>; from ume@FreeBSD.ORG on Tue, Jan 16, 2001 at 02:57:41AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Hajimu UMEMOTO [010115 10:00] wrote: > Hi, > > I wish to obtain number of processes forked since boot from userland. > So, I made a patch to intend to commit. > Any comment? Why not just use a dynamic sysctl for this? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 10:13:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn219.dh.casema.net [212.64.31.219]) by hub.freebsd.org (Postfix) with ESMTP id BBDAB37B400 for ; Mon, 15 Jan 2001 10:13:26 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0FIW8l98647; Mon, 15 Jan 2001 19:32:22 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010115190758.0304b7f0@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 15 Jan 2001 19:11:31 +0100 To: Patrick Hartling From: "Rogier R. Mulhuijzen" Subject: Re: console freeze Cc: freebsd-current@freebsd.org In-Reply-To: <20010115155828.780475E16@tomservo.vrac.iastate.edu> References: <"Tue, 12 Dec 2000 08:39:32 PST." 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 >Has there been any resolution to this? I've been having this problem >ever since the SMPng stuff went into the tree. I have no success in >getting my splash screen to work anymore or in changing video modes with >vidcontrol. The splash_bmp KLD always reports the following: > >module_register_init: MOD_LOAD (splash_bmp, c037f824, 0) error 2 > >I have done a careful comparison of GENERIC.hints and the >/boot/device.hints that I made back when it became a requirement. I've >searched the archives and come up empty. I also read cvs-all >faithfully, and while I have gotten backed up on mail due to a short >vacation here and there, I haven't seen any related commits. Sounds to me like your modules directory is outdated. Have you read UPDATING in the src root? A while ago we went from /modules to /boot/kernel. But /modules is checked first by the loader. So remove (or rename) /modules if it's still on your system. If that wasn't it..........let us know DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 10:17:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn219.dh.casema.net [212.64.31.219]) by hub.freebsd.org (Postfix) with ESMTP id 6F59E37B401 for ; Mon, 15 Jan 2001 10:17:20 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0FIaYl98664 for ; Mon, 15 Jan 2001 19:36:34 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010115191550.030cedc0@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 15 Jan 2001 19:15:56 +0100 To: freebsd-current@freebsd.org From: "Rogier R. Mulhuijzen" Subject: Re: latest buildkernel 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 >=> agp >make: don't know how to make @/pci/pcivar.h. Stop There's 2 possibilities off the top of my head.... 1) you've enabled threaded perl in /etc/make.conf.... don't do that 2) there are some files in the modules source tree that need removing. Try make clean in /usr/src/sys/ or /usr/src/sys/modules. I *think* this fixed it for me after I did a few makes in the wrong place. Otherwise just remove every damn file named @ in the /usr/src/sys/modules tree. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 10:22:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn219.dh.casema.net [212.64.31.219]) by hub.freebsd.org (Postfix) with ESMTP id D385937B400 for ; Mon, 15 Jan 2001 10:22:14 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0FIetl98676; Mon, 15 Jan 2001 19:41:03 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010115191629.0316f100@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 15 Jan 2001 19:20:18 +0100 To: "Adriaan Erasmus" From: "Rogier R. Mulhuijzen" Subject: Re: Darn Soundblaster Live :( Cc: freebsd-current@freebsd.org In-Reply-To: <008601c07ef8$b6664a00$5001000a@jhba.techconcepts.co.za> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_1108044176==_.ALT" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=====================_1108044176==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed >Every time I make the thing hangs up. I never had this problem b4 and I >think its has something to do with my CPU choice in my config file so here >is the million dollar question. From when is your current -current install? (no pun intended) I seem to recall people not being able to build anything without hangs not too long ago. Try installing 4.2 from binary distributions over your -current, and then CVSup and build a brand spanking new -current. >If I have a Celeron 400 which CPU type should I choose >i586 or i686 ???? CPU_I686.... 586 is Pentium, 686 is Pentium Pro, and Pentium II and up (Celeron started with having a P2 core with less cache IIRC) DocWilco --=====================_1108044176==_.ALT Content-Type: text/html; charset="us-ascii"
Every time I make the thing hangs up. I never had this problem b4 and I think its has something to do with my CPU choice in my config file so here is the million dollar question.

From when is your current -current install? (no pun intended)

I seem to recall people not being able to build anything without hangs not too long ago.

Try installing 4.2 from binary distributions over your -current, and then CVSup and build a brand spanking new -current.

If I have a Celeron 400 which CPU type should I choose
i586 or i686 ????

CPU_I686.... 586 is Pentium, 686 is Pentium Pro, and Pentium II and up (Celeron started with having a P2 core with less cache IIRC)

        DocWilco --=====================_1108044176==_.ALT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 10:22:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id A4EE037B401 for ; Mon, 15 Jan 2001 10:22:32 -0800 (PST) Received: from HP2500B (veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id D6FE38C13 for ; Mon, 15 Jan 2001 12:21:48 -0600 (CST) Message-ID: <027f01c07f1f$dd5542c0$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: References: <004401c07f00$b86aabe0$3028680a@tgt.com> <20010115094040.A40110@dragon.nuxi.com> Subject: Re: Buildworld failure as of 01-15-2001 @ 8:30 CST Date: Mon, 15 Jan 2001 12:20:39 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I still get the same error. ===> include/rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/klm_prot.x -o klm_prot.h rpcgen: cannot find any C preprocessor (cpp) *** Error code 1 Stop in /usr/src/include/rpcsvc. *** Error code 1 Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "David O'Brien" To: "Thomas T. Veldhouse" Cc: "FreeBSD-Current, " Sent: Monday, January 15, 2001 11:40 AM Subject: Re: Buildworld failure as of 01-15-2001 @ 8:30 CST > On Mon, Jan 15, 2001 at 08:37:43AM -0600, Thomas T. Veldhouse wrote: > > I just installed the FreeBSD 5.0-20010107-CURRENT snapshot and have cvsup'd > > to the latest source (as of subject). Buildworld fails as below: > > Do not manually do anything to get around this yet. > Please apply and try this patch. Report here, if it works or not. > > > Index: Makefile.inc1 > =================================================================== > RCS file: /home/ncvs/src/Makefile.inc1,v > retrieving revision 1.179 > diff -u -r1.179 Makefile.inc1 > --- Makefile.inc1 2000/12/03 20:29:31 1.179 > +++ Makefile.inc1 2001/01/15 17:39:37 > @@ -564,7 +564,7 @@ > > build-tools: > .for _tool in bin/csh bin/sh ${_games} gnu/usr.bin/cc/cc_tools ${_fortran} \ > - ${_libroken4} ${_libkrb5} lib/libncurses ${_share} > + usr.bin/rpcgen ${_libroken4} ${_libkrb5} lib/libncurses ${_share} > cd ${.CURDIR}/${_tool}; ${MAKE} build-tools > .endfor > > > > 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 15 10:34: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 8B2C537B402 for ; Mon, 15 Jan 2001 10:33:46 -0800 (PST) Received: from localhost (IDENT:yz+yS0z9y2MIRbWhbAGDHxrALSODhkTqmz/0W7H3N2CmpJeGhF/989oP/xdCrAsx@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.2/8.11.2/peace) with ESMTP/inet6 id f0FIWGw01567; Tue, 16 Jan 2001 03:32:17 +0900 (JST) (envelope-from ume@FreeBSD.org) Date: Tue, 16 Jan 2001 03:32:15 +0900 (JST) Message-Id: <20010116.033215.41625863.ume@FreeBSD.org> To: bright@wintelcom.net Cc: current@freebsd.org Subject: Re: number of processes forked since boot From: Hajimu UMEMOTO In-Reply-To: <20010115100618.Y7240@fw.wintelcom.net> References: <20010116.025742.74757685.ume@FreeBSD.org> <20010115100618.Y7240@fw.wintelcom.net> X-Mailer: xcite1.38> Mew version 1.95b97 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT 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, >>>>> On Mon, 15 Jan 2001 10:06:18 -0800 >>>>> Alfred Perlstein said: bright> * Hajimu UMEMOTO [010115 10:00] wrote: > Hi, > > I wish to obtain number of processes forked since boot from userland. > So, I made a patch to intend to commit. > Any comment? bright> Why not just use a dynamic sysctl for this? I think dynamic sysctl is useful for dynamic context. But, here is just static and it seems there is no advantage. Isn't it? -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 10:38:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id B955E37B401 for ; Mon, 15 Jan 2001 10:38:27 -0800 (PST) Received: from HP2500B (veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id EB0058C52 for ; Mon, 15 Jan 2001 12:37:43 -0600 (CST) Message-ID: <029a01c07f22$16a176f0$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: References: <004401c07f00$b86aabe0$3028680a@tgt.com> <20010115094040.A40110@dragon.nuxi.com> Subject: Re: Buildworld failure as of 01-15-2001 @ 8:30 CST Date: Mon, 15 Jan 2001 12:36:34 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I must have left some relics around or something. I am getting a different error: cd /usr/src/usr.bin/rpcgen; make build-tools make: don't know how to make build-tools. Stop *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. It appears that the patch didn't apply well. I looked at it manually and could not find anything wrong with it. Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "David O'Brien" To: "Thomas T. Veldhouse" Cc: "FreeBSD-Current, " Sent: Monday, January 15, 2001 11:40 AM Subject: Re: Buildworld failure as of 01-15-2001 @ 8:30 CST > On Mon, Jan 15, 2001 at 08:37:43AM -0600, Thomas T. Veldhouse wrote: > > I just installed the FreeBSD 5.0-20010107-CURRENT snapshot and have cvsup'd > > to the latest source (as of subject). Buildworld fails as below: > > Do not manually do anything to get around this yet. > Please apply and try this patch. Report here, if it works or not. > > > Index: Makefile.inc1 > =================================================================== > RCS file: /home/ncvs/src/Makefile.inc1,v > retrieving revision 1.179 > diff -u -r1.179 Makefile.inc1 > --- Makefile.inc1 2000/12/03 20:29:31 1.179 > +++ Makefile.inc1 2001/01/15 17:39:37 > @@ -564,7 +564,7 @@ > > build-tools: > .for _tool in bin/csh bin/sh ${_games} gnu/usr.bin/cc/cc_tools ${_fortran} \ > - ${_libroken4} ${_libkrb5} lib/libncurses ${_share} > + usr.bin/rpcgen ${_libroken4} ${_libkrb5} lib/libncurses ${_share} > cd ${.CURDIR}/${_tool}; ${MAKE} build-tools > .endfor > > > > 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 15 10:42:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn219.dh.casema.net [212.64.31.219]) by hub.freebsd.org (Postfix) with ESMTP id 05B3C37B401 for ; Mon, 15 Jan 2001 10:41:53 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0FJ16l98729 for ; Mon, 15 Jan 2001 20:01:06 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010115194022.030485c0@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 15 Jan 2001 19:40:28 +0100 To: freebsd-current@freebsd.org From: "Rogier R. Mulhuijzen" Subject: Re: number of processes forked since boot 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 > > I wish to obtain number of processes forked since boot from userland. >I think dynamic sysctl is useful for dynamic context. But, here is >just static and it seems there is no advantage. Isn't it? That sounds to me like a wholly dynamic thing. I mean the amount of forks since boot can rise in time right? Or am I losing my mind? =) DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 10:46:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from lolita.speakeasy.net (lolita.speakeasy.net [216.254.0.13]) by hub.freebsd.org (Postfix) with SMTP id 4DB2A37B404 for ; Mon, 15 Jan 2001 10:46:31 -0800 (PST) Received: (qmail 18520 invoked from network); 15 Jan 2001 18:38:53 -0000 Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by 192.168.0.13 with SMTP; 15 Jan 2001 18:38:53 -0000 Received: (qmail 28609 invoked from network); 15 Jan 2001 18:46:30 -0000 Received: from unknown (HELO celebris.tddhome) (64.81.20.229) by gonzo.speakeasy.net with SMTP; 15 Jan 2001 18:46:30 -0000 Received: (from tomdean@localhost) by celebris.tddhome (8.11.1/8.11.1) id f0FIkSh00385; Mon, 15 Jan 2001 10:46:28 -0800 (PST) (envelope-from tomdean@speakeasy.org) Date: Mon, 15 Jan 2001 10:46:28 -0800 (PST) Message-Id: <200101151846.f0FIkSh00385@celebris.tddhome> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: bde@zeta.org.au Cc: current@FreeBSD.ORG In-reply-to: (message from Bruce Evans on Mon, 15 Jan 2001 23:17:19 +1100 (EST)) Subject: Re: Anybody else seeing a broken /dev/lpt with SMP on -current? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Bruce, I applied the patch to dev/ppbus/lpt.c and sys/i386/isa/intr_machdep.c. Before the patch, I got the lpt failure almost immediately. df | lpr df | lpr df | lpr lpt .cshrc would normally do it. After the patch, it took lots more activity. I did the above a half-dozen times, successfully, and then: foreach i ( 1 2 3 4 5 6 7 8 9 a b c ) df | lpr end printf "\f" | lpr and, this failed. I had 4 sets of df on the page left to be ejected in the printer. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 10:47: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id EB78637B698; Mon, 15 Jan 2001 10:46:43 -0800 (PST) Received: from husten.security.at12.de (dial-213-168-73-149.netcologne.de [213.168.73.149]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id TAA10074; Mon, 15 Jan 2001 19:46:39 +0100 (MET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.1/8.11.1) with ESMTP id f0FIkWH60518; Mon, 15 Jan 2001 19:46:32 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Mon, 15 Jan 2001 19:46:32 +0100 (CET) From: Paul Herman To: Hajimu UMEMOTO Cc: , Subject: Re: number of processes forked since boot In-Reply-To: <20010116.033215.41625863.ume@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, 16 Jan 2001, Hajimu UMEMOTO wrote: > bright> * Hajimu UMEMOTO [010115 10:00] wrote: > > > I wish to obtain number of processes forked since boot from userland. > > So, I made a patch to intend to commit. > > Any comment? I like the idea, but this belongs in vmeter with context switches, page faults, etc, doesn't it? This is how OpenBSD does it, anyway. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 10:49:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id C4B1D37B400 for ; Mon, 15 Jan 2001 10:49:24 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 27197177E9F for ; Mon, 15 Jan 2001 12:49:26 -0600 (CST) Message-ID: <01d901c07f23$e46ceaa0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: Subject: VXA tape drive Date: Mon, 15 Jan 2001 12:49:29 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I checked in current with little luck. Does -current support VXA-1 tape drives by Ecrix. The site claims that freebsd does, but the only response by someone that has one says that it won't successfully backup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 10:50:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 82E6637B400 for ; Mon, 15 Jan 2001 10:50:34 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA07455; Mon, 15 Jan 2001 10:50:29 -0800 Date: Mon, 15 Jan 2001 10:50:27 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David W. Chapman Jr." Cc: freebsd-current@FreeBSD.ORG Subject: Re: VXA tape drive In-Reply-To: <01d901c07f23$e46ceaa0$931576d8@inethouston.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 Well, details would be nice. > I checked in current with little luck. Does -current support VXA-1 tape > drives by Ecrix. The site claims that freebsd does, but the only response > by someone that has one says that it won't successfully backup. > > > > 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 15 10:58: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from stox.sa.enteract.com (stox.sa.enteract.com [207.229.132.161]) by hub.freebsd.org (Postfix) with ESMTP id CC44337B6AE for ; Mon, 15 Jan 2001 10:57:50 -0800 (PST) Received: (from stox@localhost) by stox.sa.enteract.com (8.11.1/8.9.3) id f0F8dJG03073; Mon, 15 Jan 2001 02:39:19 -0600 (CST) (envelope-from stox) 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: <01d901c07f23$e46ceaa0$931576d8@inethouston.net> Date: Mon, 15 Jan 2001 02:39:19 -0600 (CST) From: "Kenneth P. Stox" To: "David W. Chapman Jr." Subject: RE: VXA tape drive Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been using one under 4.2-STABLE, for some time, without problems. On 15-Jan-01 David W. Chapman Jr. wrote: > I checked in current with little luck. Does -current support VXA-1 tape > drives by Ecrix. The site claims that freebsd does, but the only response > by someone that has one says that it won't successfully backup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 11:26:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from bilver.wjv.com (dhcp-1-195.n01.orldfl01.us.ra.verio.net [157.238.210.195]) by hub.freebsd.org (Postfix) with ESMTP id 12DCF37B401 for ; Mon, 15 Jan 2001 11:26:01 -0800 (PST) Received: (from bill@localhost) by bilver.wjv.com (8.9.3/8.9.3) id OAA17942 for freebsd-current@freebsd.org; Mon, 15 Jan 2001 14:25:59 -0500 (EST) (envelope-from bill) Date: Mon, 15 Jan 2001 14:25:52 -0500 From: Bill Vermillion To: freebsd-current@freebsd.org Subject: Re: VXA tape drive Message-ID: <20010115142551.A17891@wjv.com> Reply-To: bv@bilver.wjv.com References: <01d901c07f23$e46ceaa0$931576d8@inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01d901c07f23$e46ceaa0$931576d8@inethouston.net>; from dwcjr@inethouston.net on Mon, Jan 15, 2001 at 12:49:29PM -0600 Organization: W.J.Vermillion / Orlando - Winter Park Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 12:49:29PM -0600, David W. Chapman Jr. thus spoke: > I checked in current with little luck. Does -current support > VXA-1 tape drives by Ecrix. The site claims that freebsd does, > but the only response by someone that has one says that it won't > successfully backup. It really should work. I talked with the Ecrix people awhile back and the drive is essentially just a DAT drive. What makes it different is internally it is writing short packet across the width of the tape, and using multiple heads. The reason is that if you don't send data to a tape fast enough it will back up, stop and restart. Ecrix calls this 'back-hitching' but I remember it from the old days called 'shoe shining'. So they slow down the tape as it travels across the heads. This changed the anlge of the helical stripes. This would make the tape unreadable in a device which expects the data to be readable across the width of the tape. By using 'packets' they put several blocks of data across the width, and if a head can read the first packet, but the angle of the helix is such that the next one is not readable, the next head will pick this up. Quite an interesting approach to enable the tape to never stop and maximize the data throughput. What kind of errors are you having? Bill -- Bill Vermillion - bv @ wjv . 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 15 11:31:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 9BAD837B401 for ; Mon, 15 Jan 2001 11:31:32 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id EE20B177E9F; Mon, 15 Jan 2001 13:31:29 -0600 (CST) Message-ID: <025301c07f29$c49bb7a0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: Cc: Subject: Fw: SCSI Tape Drive support Date: Mon, 15 Jan 2001 13:31:33 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't any problems yet, just finding out who has used it, but Mr. Wayne informed me that he had problems as enclosed below so I started to ask. I have already been talking to Matthew Jacob about this and have heard from someone else that they got it working successfully so I think we can consider this thread closed if nobody has any further comments. ----- Original Message ----- From: "Michael R. Wayne" To: "David W. Chapman Jr." Sent: Monday, January 15, 2001 12:20 PM Subject: Re: SCSI Tape Drive support > On Sun, Jan 14, 2001 at 02:46:45PM -0600, David W. Chapman Jr. wrote: > > Does anyone know if FreeBSD supports VXA 33/66gig tape drives by Ecrix? > > Well, yes & no. I can talk to it and run dumps partway but always > get errors partway through. Tech support was not very helpful. > Gave up on the project for now. > > /\/\ \/\/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 11:41:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 6026237B400 for ; Mon, 15 Jan 2001 11:41:11 -0800 (PST) Received: from localhost (IDENT:17g2ZlG0gb4jprEU9fpecawe8gpq1jl1JwPeh8r5FhLDagYJ4vbaBzhhc09o/zIC@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.2/8.11.2/peace) with ESMTP/inet6 id f0FJcTw02339; Tue, 16 Jan 2001 04:38:30 +0900 (JST) (envelope-from ume@FreeBSD.org) Date: Tue, 16 Jan 2001 04:38:28 +0900 (JST) Message-Id: <20010116.043828.97301753.ume@FreeBSD.org> To: pherman@frenchfries.net Cc: bright@wintelcom.net, current@FreeBSD.ORG Subject: Re: number of processes forked since boot From: Hajimu UMEMOTO In-Reply-To: References: <20010116.033215.41625863.ume@FreeBSD.org> X-Mailer: xcite1.38> Mew version 1.95b97 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT 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 Mon, 15 Jan 2001 19:46:32 +0100 (CET) >>>>> Paul Herman said: pherman> On Tue, 16 Jan 2001, Hajimu UMEMOTO wrote: > bright> * Hajimu UMEMOTO [010115 10:00] wrote: > > > I wish to obtain number of processes forked since boot from userland. > > So, I made a patch to intend to commit. > > Any comment? pherman> I like the idea, but this belongs in vmeter with context switches, pherman> page faults, etc, doesn't it? This is how OpenBSD does it, anyway. I see. You mean accessing uvmexp.forks via sysctl. Does it solved by just moving nforks into vm_meter.c? -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 11:44:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id AB79937B404 for ; Mon, 15 Jan 2001 11:44:10 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0FJi8K41992; Mon, 15 Jan 2001 11:44:08 -0800 (PST) (envelope-from obrien) Date: Mon, 15 Jan 2001 11:44:08 -0800 From: "David O'Brien" To: "Thomas T. Veldhouse" Cc: freebsd-current@freebsd.org Subject: Re: Buildworld failure as of 01-15-2001 @ 8:30 CST Message-ID: <20010115114407.A41868@dragon.nuxi.com> Reply-To: freebsd-current@freebsd.org References: <004401c07f00$b86aabe0$3028680a@tgt.com> <20010115094040.A40110@dragon.nuxi.com> <029a01c07f22$16a176f0$3028680a@tgt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <029a01c07f22$16a176f0$3028680a@tgt.com>; from veldy@veldy.net on Mon, Jan 15, 2001 at 12:36:34PM -0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 12:36:34PM -0600, Thomas T. Veldhouse wrote: > I must have left some relics around or something. I am getting a different > error: No, I goofed. I'm getting my current test box back into shape so I can build a world before making stupid suggestions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 11:48: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id E8B4D37B404 for ; Mon, 15 Jan 2001 11:47:19 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0FJjj191208; Mon, 15 Jan 2001 11:45:45 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 15 Jan 2001 11:47:16 -0800 (PST) From: John Baldwin To: Garance A Drosihn Subject: RE: Anybody else seeing a broken /dev/lpt with SMP on -current? Cc: current@FreeBSD.org, Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Jan-01 Garance A Drosihn wrote: > At 6:55 PM -0800 1/12/01, John Baldwin wrote: >>On 13-Jan-01 Jordan Hubbard wrote: >> > If anybody wants a fuller traceback then I'll compile up a kernel >> > with debugging symbols, but it's going to be pretty sparse anyway >> > since it basically only shows the trap() from the page fault and >> > the subsequent panic. >> >>All the other traces show the kernel having returned to an address >>that is beyond the end of the kernel (which causes the page fault) >>meaning that the stack is fubar'd, so the trace isn't meaningful >>anyways. :( Knowing how and why the lpd interrupt handler trashes >>the stack is the useful info, and with the stack already trashed, >>I don't know of an easy way to figure that out. > > Do you really mean the "lpd interrupt handler", or do you mean > the "lpt interrupt handler"? Does this problem only happen when > lpd is sending data thru /dev/lpt? lpt interrupt handler, yes. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 11:48:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id AB38737B699 for ; Mon, 15 Jan 2001 11:47:24 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0FJjo191256; Mon, 15 Jan 2001 11:45:50 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010115092544.U91029@gsmx07.alcatel.com.au> Date: Mon, 15 Jan 2001 11:47:21 -0800 (PST) From: John Baldwin To: Peter Jeremy Subject: Re: Atomic breakage? Cc: current@FreeBSD.org, Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Jan-01 Peter Jeremy wrote: > On 2001-Jan-14 23:02:28 +0200, Mark Murray wrote: >>Hi John >> >>There seems to be same breakage in the atomic stuff: >> >>link_elf: symbol atomic_load_acq_int undefined >>KLD file random.ko - could not finalize loading >> >>I back out the latest commit to sys/i386/include/atomic.h, and things >>work a bit better (on my laptop). > > Basically, the problem is that some of the recent commits have broken > the interface between sys/i386/include/atomic.h and sys/i386/i386/atomic.c > > The latter file builds non-inlined versions of the atomic functions > defined in atomic.h. This means that atomic.h must be laid out in a > suitable manner so that the non-inlined functions are built by > atomic.c. (Modules use explicit function calls, rather than inlined > atomic functions to remove the need to have distinct UP and SMP > versions.) > > The layout of atomic.h should look like: > > >#ifdef KLD_MODULE >#defines expanding to prototypes. >#else >#defines expanding to inline function definitions >#endif > List of atomic functions (invoking above macros) > > > Due to incompatibilities between __asm in different versions of gcc, > several different versions of various macros (and expansions) are > necessary. The old asm should probably die for one thing. > The problem is that over time, atomic.h has been expanded and things > have gotten a bit confused. > > Mark's reported breakage is a result of the new atomic_cmpset_int(). > This has been defined in the !KLD_MODULE section (but only for new > versions of gcc - which should be OK since it'll never be used in > conjunction with the old gcc) and a suitable prototype has been > inserted in the KLD_MODULE section. The problem is that a pile of >#defines have been incorrectly put in this section, rather than > outside the KLD_MODULE section. This means that modules are > left with dangling references to these functions. Actually, the problem is that I changed atomic_load and atomic_store to be functions for modules instead of inlines because they are now different for I386_CPU. It seems that static versions aren't being compiled of these functions. I'll fix it in a second. atomic_cmpset_* are fine, however. > And for BDE's benefit - atomic.h is broken for IA32's with 64-bit > longs. (I believe that can be fixed for Pentiums and above using > CMPXCHG8B, but I can't test the code). The i386 with 64-bit longs doesn't boot from what I hear. Also, long in machine/types.h is 32-bits long. I don't think we need to bother with 64-bit longs. Adding 64-bit atomic ops will be expensive on <= 486. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 11:57:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from zaphon.llamas.net (zaphon.llamas.net [207.203.36.210]) by hub.freebsd.org (Postfix) with SMTP id 47FCC37B698 for ; Mon, 15 Jan 2001 11:57:22 -0800 (PST) Received: (qmail 82237 invoked by uid 1001); 15 Jan 2001 19:57:12 -0000 Date: Mon, 15 Jan 2001 11:57:12 -0800 From: Greg Rumple To: The Hermit Hacker Cc: Cameron Grant , Michael Wells , freebsd-current@FreeBSD.ORG Subject: Re: Soundblaster 64 PCI Message-ID: <20010115115711.H69786@zaphon.llamas.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from scrappy@hub.org on Sun, Jan 14, 2001 at 05:30:19PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the same problem I am having with a Soundblaster 16 PCI on 4.2-STABLE. I found a work around for it. It appears that there is something that is being un-initialized by the FreeBSD es1371 driver that other OS's do set. I have built a linux boot floppy, boot it, modprobe the linux es1371 driver, and than reboot into FreeBSD and the problem is gone. And until I power off the machine, the card works fine. I have brought this up several times on the freebsd-multimedia list, but have gone un-noticed each time. Anyway, I have found a lame work around, until it is fixed properly. Greg * The Hermit Hacker (scrappy@hub.org) [010114 21:33]: > > yup, just confirmed ... it does it with splay as well ... > > > On Sun, 14 Jan 2001, The Hermit Hacker wrote: > > > On Sun, 14 Jan 2001, Cameron Grant wrote: > > > > > > > If this is a known problem, I'll stop for now and watch out for fixes. > > > > > If it's not the expected behaviour from the PCM driver though, can > > > > > anyone advise? > > > > > > > > Okay, just checked and it appears tha htis is the same error that I'm > > > > seeing on mine, as reported yesterday ... not sure if its known or not, > > > > but its not "just you" ... > > > > > > are either of you using esound or xmms? if so, i know the cause of this and > > > it will be fixed shortly, once my primary development box recovers from > > > killing its cpu. > > > > > > if not, i'll try to reproduce this. > > > > for me, I tried using splay ... but, not sure how old my compile was, so > > am just installing a new copy and will report back ... > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Greg Rumple grumple@zaphon.llamas.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 15 12: 7:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 638F637B400; Mon, 15 Jan 2001 12:07:22 -0800 (PST) Received: from husten.security.at12.de (dial-213-168-72-73.netcologne.de [213.168.72.73]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id VAA12079; Mon, 15 Jan 2001 21:07:17 +0100 (MET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.1/8.11.1) with ESMTP id f0FK79Y52463; Mon, 15 Jan 2001 21:07:09 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Mon, 15 Jan 2001 21:07:08 +0100 (CET) From: Paul Herman To: Hajimu UMEMOTO Cc: Subject: Re: number of processes forked since boot In-Reply-To: <20010116.043828.97301753.ume@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, 16 Jan 2001, Hajimu UMEMOTO wrote: > >>>>> On Mon, 15 Jan 2001 19:46:32 +0100 (CET) > >>>>> Paul Herman said: > > pherman> I like the idea, but this belongs in vmeter with context switches, > pherman> page faults, etc, doesn't it? This is how OpenBSD does it, anyway. > > I see. > You mean accessing uvmexp.forks via sysctl. > Does it solved by just moving nforks into vm_meter.c? Yes, that's my read from the source. What I also like about it is that it counts [vr]forks to boot, plus vmpages affected by the fork. After I first saw this in OBSD I was really motivated to do just what you've done for FreeBSD, but never got around to it. If you like, I'll see if I can't come up with something similar. Shouldn't be too hard. I'll try that tonight. The hardest part would be finding a spot on the systat(1) display to put it. :-) -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 12:11:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from gypsy.vrac.iastate.edu (gypsy.vrac.iastate.edu [129.186.232.122]) by hub.freebsd.org (Postfix) with ESMTP id 30AA237B400 for ; Mon, 15 Jan 2001 12:10:55 -0800 (PST) Received: from tomservo.vrac.iastate.edu (tomservo.vrac.iastate.edu [129.186.232.121]) by gypsy.vrac.iastate.edu (Postfix) with ESMTP id 9A1A711; Mon, 15 Jan 2001 14:10:54 -0600 (CST) Received: from tomservo.vrac.iastate.edu (localhost [127.0.0.1]) by tomservo.vrac.iastate.edu (Postfix) with ESMTP id 337F15E16; Mon, 15 Jan 2001 14:10:54 -0600 (CST) To: "Rogier R. Mulhuijzen" Cc: freebsd-current@freebsd.org Subject: Re: console freeze In-reply-to: "Mon, 15 Jan 2001 19:11:31 +0100." <4.3.2.7.0.20010115190758.0304b7f0@mail.drwilco.net> Date: Mon, 15 Jan 2001 14:10:54 -0600 From: Patrick Hartling Message-Id: <20010115201054.337F15E16@tomservo.vrac.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rogier R. Mulhuijzen" wrote: } } >Has there been any resolution to this? I've been having this problem } >ever since the SMPng stuff went into the tree. I have no success in } >getting my splash screen to work anymore or in changing video modes with } >vidcontrol. The splash_bmp KLD always reports the following: } > } >module_register_init: MOD_LOAD (splash_bmp, c037f824, 0) error 2 } > } >I have done a careful comparison of GENERIC.hints and the } >/boot/device.hints that I made back when it became a requirement. I've } >searched the archives and come up empty. I also read cvs-all } >faithfully, and while I have gotten backed up on mail due to a short } >vacation here and there, I haven't seen any related commits. } } Sounds to me like your modules directory is outdated. Have you read } UPDATING in the src root? A while ago we went from /modules to } /boot/kernel. But /modules is checked first by the loader. So remove (or } rename) /modules if it's still on your system. } } If that wasn't it..........let us know I always keep my kernel, modules, and userland in sync. Right now, I am running sources from January 5, 2001. I no longer have a /modules directory--everything is coming from /boot/kernel. -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 12:26:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 5E2B037B402 for ; Mon, 15 Jan 2001 12:26:14 -0800 (PST) Received: from localhost (IDENT:oPV4SHMyEid7yJnTi97bp0+23eIWIPQlC4dNNYHXajpeyVu2cTFa48BczCOjXaYv@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.2/8.11.2/peace) with ESMTP/inet6 id f0FKJOd01215; Tue, 16 Jan 2001 05:19:25 +0900 (JST) (envelope-from ume@FreeBSD.org) Date: Tue, 16 Jan 2001 05:19:21 +0900 (JST) Message-Id: <20010116.051921.41625345.ume@FreeBSD.org> To: pherman@frenchfries.net Cc: current@FreeBSD.ORG Subject: Re: number of processes forked since boot From: Hajimu UMEMOTO In-Reply-To: References: <20010116.043828.97301753.ume@FreeBSD.org> X-Mailer: Mew version 1.95b97 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT 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 Mon, 15 Jan 2001 21:07:08 +0100 (CET) >>>>> Paul Herman said: pherman> Yes, that's my read from the source. What I also like about it is pherman> that it counts [vr]forks to boot, plus vmpages affected by the fork. pherman> After I first saw this in OBSD I was really motivated to do just what pherman> you've done for FreeBSD, but never got around to it. I just moved nforks into vm_meter.c Here is a patch: Index: sys/kern/kern_fork.c diff -u sys/kern/kern_fork.c.orig sys/kern/kern_fork.c --- sys/kern/kern_fork.c.orig Fri Jan 12 02:46:53 2001 +++ sys/kern/kern_fork.c Tue Jan 16 04:53:18 2001 @@ -145,6 +145,7 @@ int nprocs = 1; /* process 0 */ static int nextpid = 0; +extern unsigned int nforks; /* * Random component to nextpid generation. We mix in a random factor to make @@ -277,6 +278,8 @@ } newproc->p_vmspace = NULL; + + nforks++; /* * Find an unused process ID. We remember a range of unused IDs Index: sys/vm/vm_meter.c diff -u sys/vm/vm_meter.c.orig sys/vm/vm_meter.c --- sys/vm/vm_meter.c.orig Fri Jan 12 02:48:48 2001 +++ sys/vm/vm_meter.c Tue Jan 16 04:51:49 2001 @@ -126,6 +126,10 @@ SYSCTL_UINT(_vm, OID_AUTO, v_free_severe, CTLFLAG_RW, &cnt.v_free_severe, 0, ""); +unsigned int nforks = 0; +SYSCTL_UINT(_vm, OID_AUTO, nforks, CTLFLAG_RD, &nforks, 0, + "number of fork()s since boot"); + SYSCTL_STRUCT(_vm, VM_LOADAVG, loadavg, CTLFLAG_RD, &averunnable, loadavg, "Machine loadaverage history"); pherman> If you like, I'll see if I can't come up with something pherman> similar. Shouldn't be too hard. I'll try that tonight. Please do it. pherman> The hardest part would be finding a spot on the systat(1) display to pherman> put it. :-) Exactly. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 12:49:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id B3EE937B69C; Mon, 15 Jan 2001 12:48:53 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA25112; Tue, 16 Jan 2001 07:46:10 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01JYYU7JL9NK8ZYQKN@cim.alcatel.com.au>; Tue, 16 Jan 2001 07:46:09 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id f0FKk7F38033; Tue, 16 Jan 2001 07:46:07 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Tue, 16 Jan 2001 07:46:07 +1100 From: Peter Jeremy Subject: Re: cvs commit: src/sys/i386/conf GENERIC In-reply-to: <200101150808.f0F88CQ01192@mobile.wemm.org>; from peter@netplex.com.au on Mon, Jan 15, 2001 at 12:08:12AM -0800 To: Peter Wemm Cc: Sheldon Hearn , Dag-Erling Smorgrav , Andrea Campi , Poul-Henning Kamp , developer@FreeBSD.ORG, current@FreeBSD.ORG Mail-followup-to: Peter Wemm , Sheldon Hearn , Dag-Erling Smorgrav , Andrea Campi , Poul-Henning Kamp , developer@FreeBSD.ORG, current@FreeBSD.ORG Message-id: <20010116074606.E91029@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <34097.979544060@axl.fw.uunet.co.za> <200101150808.f0F88CQ01192@mobile.wemm.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-15 00:08:12 -0800, Peter Wemm wrote: >The patch below does this: >http://people.freebsd.org/~peter/i386_cleanup.diff ... >To be clear: THIS DOES NOT REMOVE i386 SUPPORT! It will actually slightly >improve i386 runtime speed by removing the useless conditional tests. IMHO, this is the right approach. I don't see any reason to rip out the (working) 386 code. If it rots due to lack of interest in future, then it can be stripped out. Note that the patch doesn't currently handle the PC98. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 13:38:43 2001 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 DD33D37B404; Mon, 15 Jan 2001 13:38:15 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id WAA33680; Mon, 15 Jan 2001 22:38:07 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Peter Wemm Cc: Sheldon Hearn , Andrea Campi , Poul-Henning Kamp , developer@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf GENERIC References: <200101150808.f0F88CQ01192@mobile.wemm.org> From: Dag-Erling Smorgrav Date: 15 Jan 2001 22:38:06 +0100 In-Reply-To: Peter Wemm's message of "Mon, 15 Jan 2001 00:08:12 -0800" Message-ID: Lines: 13 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm writes: > 1: it removes the 486-and-above code from the 386-only cases. > 2: it removes the runtime conditionals that everybody currently executes > if I386_CPU is present > 3: prevents people shooting themselves in the foot at 'make depend' stage > if they accidently activate I386_CPU. Add a big fat comment to GENERIC warning users not to include I386_CPU in their configs if they can help it. DES -- Dag-Erling Smorgrav - des@ofug.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 15 13:43:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from adrastea.sjc.ca.bbnow.net (adrastea.sjc.ca.bbnow.net [24.219.121.237]) by hub.freebsd.org (Postfix) with ESMTP id 016CE37B400 for ; Mon, 15 Jan 2001 13:43:27 -0800 (PST) Received: from localhost (aba@localhost) by adrastea.sjc.ca.bbnow.net (8.11.1/8.11.1) with ESMTP id f0FLlsw61239; Mon, 15 Jan 2001 13:47:59 -0800 (PST) (envelope-from aba@adrastea.sjc.ca.bbnow.net) Date: Mon, 15 Jan 2001 13:47:49 -0800 (PST) From: Andrew B Alexander To: Greg Rumple Cc: Subject: Re: Soundblaster 64 PCI In-Reply-To: <20010115115711.H69786@zaphon.llamas.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 I probably have the same card as you, I just went out and bought a soundblaster 16PCI because my new motherboard doesn't have any ISA slots. Unfortunately, the card is detected and does play sound, but it is soo distorted you can't really recognize anything. I was just wondering if you hard this distortion problem as well, I haven't seen anything on the lists about it until now. Thanks, Andrew On Mon, 15 Jan 2001, Greg Rumple wrote: > This is the same problem I am having with a Soundblaster 16 PCI on > 4.2-STABLE. I found a work around for it. It appears that there is > something that is being un-initialized by the FreeBSD es1371 driver that > other OS's do set. I have built a linux boot floppy, boot it, modprobe > the linux es1371 driver, and than reboot into FreeBSD and the problem is > gone. And until I power off the machine, the card works fine. > > I have brought this up several times on the freebsd-multimedia list, but > have gone un-noticed each time. > > Anyway, I have found a lame work around, until it is fixed properly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 14: 1:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 539B537B401 for ; Mon, 15 Jan 2001 14:01:10 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA08555; Mon, 15 Jan 2001 14:01:05 -0800 Date: Mon, 15 Jan 2001 14:01:04 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: sio && serial console in -current? 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 FWIW, serial now is happy again. I guess the planets realigned. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 14: 2: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B24F437B698 for ; Mon, 15 Jan 2001 14:01:47 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA08568; Mon, 15 Jan 2001 14:01:43 -0800 Date: Mon, 15 Jan 2001 14:01:41 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Wemm Cc: current@FreeBSD.ORG Subject: I take that back.... Re: sio && serial console in -current? 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, 15 Jan 2001, Matthew Jacob wrote: > > FWIW, serial now is happy again. I guess the planets realigned. Nope- it just happens more fitfully..... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 14: 2:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from adrastea.sjc.ca.bbnow.net (adrastea.sjc.ca.bbnow.net [24.219.121.237]) by hub.freebsd.org (Postfix) with ESMTP id 7E1B037B400 for ; Mon, 15 Jan 2001 14:02:31 -0800 (PST) Received: from localhost (aba@localhost) by adrastea.sjc.ca.bbnow.net (8.11.1/8.11.1) with ESMTP id f0FM76265480; Mon, 15 Jan 2001 14:07:11 -0800 (PST) (envelope-from aba@rackmount.org) X-Authentication-Warning: adrastea.sjc.ca.bbnow.net: aba owned process doing -bs Date: Mon, 15 Jan 2001 14:07:01 -0800 (PST) From: Andrew B Alexander X-X-Sender: To: Greg Rumple Cc: Subject: Re: Soundblaster 64 PCI In-Reply-To: <20010115115711.H69786@zaphon.llamas.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 i have the same problem with sounbblaster 16 pci. wondering if there will be a fix any time soon? On Mon, 15 Jan 2001, Greg Rumple wrote: > This is the same problem I am having with a Soundblaster 16 PCI on > 4.2-STABLE. I found a work around for it. It appears that there is > something that is being un-initialized by the FreeBSD es1371 driver that > other OS's do set. I have built a linux boot floppy, boot it, modprobe > the linux es1371 driver, and than reboot into FreeBSD and the problem is > gone. And until I power off the machine, the card works fine. > > I have brought this up several times on the freebsd-multimedia list, but > have gone un-noticed each time. > > Anyway, I have found a lame work around, until it is fixed properly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 14:23:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (unknown [213.162.128.50]) by hub.freebsd.org (Postfix) with ESMTP id 2FD3537B402; Mon, 15 Jan 2001 14:23:13 -0800 (PST) Received: by mimer.webgiro.com (Postfix, from userid 66) id 236582DC0E; Mon, 15 Jan 2001 23:26:56 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 523297817; Mon, 15 Jan 2001 23:24:22 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 4DCF010E1B; Mon, 15 Jan 2001 23:24:22 +0100 (CET) Date: Mon, 15 Jan 2001 23:24:22 +0100 (CET) From: Andrzej Bialecki To: Hajimu UMEMOTO Cc: current@freebsd.org Subject: Re: number of processes forked since boot In-Reply-To: <20010116.025742.74757685.ume@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, 16 Jan 2001, Hajimu UMEMOTO wrote: > Hi, > > I wish to obtain number of processes forked since boot from userland. > So, I made a patch to intend to commit. > Any comment? > Index: sys/kern/kern_fork.c > diff -u sys/kern/kern_fork.c.orig sys/kern/kern_fork.c > --- sys/kern/kern_fork.c.orig Fri Jan 12 02:46:53 2001 > +++ sys/kern/kern_fork.c Tue Jan 16 02:30:26 2001 > @@ -146,6 +146,9 @@ > int nprocs = 1; /* process 0 */ > static int nextpid = 0; > > +static unsigned int nforks = 0; > +SYSCTL_UINT(_kern, KERN_NFORKS, nforks, CTLFLAG_RD, &nforks, 0, ""); If any, I think this should be long, otherwise on machines like web servers the counter will overflow in a short time. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 15: 9:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 4DFF337B69D for ; Mon, 15 Jan 2001 15:09:36 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id KAA08778; Tue, 16 Jan 2001 10:09:31 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01JYYZ7G10I8GKTZKQ@cim.alcatel.com.au>; Tue, 16 Jan 2001 10:09:37 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id f0FN9SA38579; Tue, 16 Jan 2001 10:09:28 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Tue, 16 Jan 2001 10:09:28 +1100 From: Peter Jeremy Subject: Re: number of processes forked since boot In-reply-to: ; from abial@webgiro.com on Mon, Jan 15, 2001 at 11:24:22PM +0100 To: Andrzej Bialecki Cc: current@FreeBSD.ORG Mail-followup-to: Andrzej Bialecki , current@FreeBSD.ORG Message-id: <20010116100928.H91029@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20010116.025742.74757685.ume@FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-15 23:24:22 +0100, Andrzej Bialecki wrote: >On Tue, 16 Jan 2001, Hajimu UMEMOTO wrote: ... >> +static unsigned int nforks = 0; >> +SYSCTL_UINT(_kern, KERN_NFORKS, nforks, CTLFLAG_RD, &nforks, 0, ""); > >If any, I think this should be long, otherwise on machines like web >servers the counter will overflow in a short time. On an i386, "long" and "int" are both 32 bits, hence "long" has a lower maximum count than "unsigned int". "unsigned long" might be a better choice (to give a greater range on the Alpha). In any case, at 1000 forks/sec, a 32-bit counter will still take nearly 50 days to wrap. Lots of other counters will have wrapped by this time. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 15:26:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from bilver.wjv.com (dhcp-1-130.n01.orldfl01.us.ra.verio.net [157.238.210.130]) by hub.freebsd.org (Postfix) with ESMTP id CD67237B6BB for ; Mon, 15 Jan 2001 15:26:16 -0800 (PST) Received: (from bill@localhost) by bilver.wjv.com (8.9.3/8.9.3) id SAA19641 for freebsd-current@freebsd.org; Mon, 15 Jan 2001 18:26:15 -0500 (EST) (envelope-from bill) Date: Mon, 15 Jan 2001 18:26:08 -0500 From: Bill Vermillion To: freebsd-current@freebsd.org Subject: Re: VXA tape drive Message-ID: <20010115182608.A19584@wjv.com> Reply-To: bv@bilver.wjv.com References: <01d901c07f23$e46ceaa0$931576d8@inethouston.net> <20010115142551.A17891@wjv.com> <025901c07f29$ccdb88a0$931576d8@inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <025901c07f29$ccdb88a0$931576d8@inethouston.net>; from dwcjr@inethouston.net on Mon, Jan 15, 2001 at 01:31:47PM -0600 Organization: W.J.Vermillion / Orlando - Winter Park Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 01:31:47PM -0600, David W. Chapman Jr. thus spoke: > thanks for the background, quite interesting. You're welcome. I'm currently writing a series of articles for the tape newbie that a friend coaxed me into. I've finished electrons, magnets, head design and QIC tape. Rotary heads are next. Don't know where I'll go from there. www.aplawrence.com. Go to Unix articles and you'll see them listed on the top right side of the page as I recall. If you are into audio tape - I wrote an article a jillion years ago that has widely propagated. goto www.bilver.com [note that it is not the same as this address] and go down to aligning your professional tape recoder. I was an audio recording engineer before computers came to dominate my life. Bill -- Bill Vermillion - bv @ wjv . 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 15 15:56:49 2001 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 9695B37B699 for ; Mon, 15 Jan 2001 15:56:30 -0800 (PST) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 449D42060; Tue, 16 Jan 2001 00:56:29 +0100 (CET) Date: Tue, 16 Jan 2001 00:56:28 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: make buildkernel broken Message-ID: <20010116005628.A92902@shadowmere.student.utwente.nl> Reply-To: daeron@shadowmere.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> wi make: don't know how to make /usr/src/sys/modules/wi/../../i386/isa/if_wi.c. Stop *** Error code 2 Stop in /usr/src/sys/modules. *** Error code 1 -- Pascal Hofstee < daeron @ shadowmere . student . utwente . nl > begin LOVE-LETTER-FOR-YOU.TXT.vbs I'm a signature virus. Please copy me and help me spread. end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 16: 1:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 5A61C37B401 for ; Mon, 15 Jan 2001 16:00:50 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0FNxM197262; Mon, 15 Jan 2001 15:59:22 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010116005628.A92902@shadowmere.student.utwente.nl> Date: Mon, 15 Jan 2001 16:00:56 -0800 (PST) From: John Baldwin To: Pascal Hofstee Subject: RE: make buildkernel broken Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Jan-01 Pascal Hofstee wrote: > ===> wi > make: don't know how to make > /usr/src/sys/modules/wi/../../i386/isa/if_wi.c. Stop > *** Error code 2 > > Stop in /usr/src/sys/modules. > *** Error code 1 Did you do a make depend? This was fixed a while ago. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 17:23:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from mgate06.so-net.ne.jp (mgate06.so-net.ne.jp [210.139.254.153]) by hub.freebsd.org (Postfix) with ESMTP id 16C7437B69E for ; Mon, 15 Jan 2001 17:23:16 -0800 (PST) Received: from mail.ya3.so-net.ne.jp (mspool11.so-net.ne.jp [210.139.248.11]) by mgate06.so-net.ne.jp (8.8.8+3.0Wbeta9/3.6W00122022) with ESMTP id KAA26663; Tue, 16 Jan 2001 10:23:14 +0900 (JST) Received: from localhost (p84e4a9.ykh2.ap.so-net.ne.jp [210.132.228.169]) by mail.ya3.so-net.ne.jp (8.9.3/3.7W99092111) with ESMTP id KAA07628; Tue, 16 Jan 2001 10:23:13 +0900 (JST) To: daeron@shadowmere.student.utwente.nl Cc: freebsd-current@freebsd.org Subject: Re: make buildkernel broken From: Yoshihiro Koya In-Reply-To: <20010116005628.A92902@shadowmere.student.utwente.nl> References: <20010116005628.A92902@shadowmere.student.utwente.nl> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010116102549S.ipfw@ya3.so-net.ne.jp> Date: Tue, 16 Jan 2001 10:25:49 +0900 X-Dispatcher: imput version 990905(IM130) Lines: 15 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, > ===> wi > make: don't know how to make > /usr/src/sys/modules/wi/../../i386/isa/if_wi.c. Stop > *** Error code 2 > > Stop in /usr/src/sys/modules. > *** Error code 1 I had same problem. Do you have /usr/src/sys/modules/wi/.depend ? If so, remove it and try make buildkernel again. koya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 15 17:39: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 7F80737B69E for ; Mon, 15 Jan 2001 17:38:45 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id F2E92177E9F; Mon, 15 Jan 2001 19:38:49 -0600 (CST) Message-ID: <005401c07f5d$12a0fb80$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Jordan Hubbard" Cc: References: <85139.979608186@winston.osd.bsdi.com> Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) Date: Mon, 15 Jan 2001 19:38:48 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was thinking about that. Of course my skills limit me to the idea :-P > Well, maybe if it would load automatically on first open.. :) We need > some stub loader technology... > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 1:47:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 8E35437B69C for ; Tue, 16 Jan 2001 01:47:20 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0G9lKs11014 for ; Tue, 16 Jan 2001 01:47:20 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101160947.f0G9lKs11014@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: current@freebsd.org Subject: HEADS UP: I386_CPU Date: Tue, 16 Jan 2001 01:47:20 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've requested a change for UPDATING: The kerrnel option I386_CPU is now mutually exclusive with the other cpu types. If you have an i386 system, be sure that it only had this line. Remove it for all other configurations. Note that this does not remove i386 support. The actual commit message follows: Modified files: sys/i386/conf NOTES sys/i386/i386 identcpu.c machdep.c pmap.c support.s sys/pc98/conf GENERIC sys/pc98/i386 machdep.c Log: Stop doing runtime checking on i386 cpus for cpu class. The cpu is slow enough as it is, without having to constantly check that it really is an i386 still. It was possible to compile out the conditionals for faster cpus by leaving out 'I386_CPU', but it was not possible to unconditionally compile for the i386. You got the runtime checking whether you wanted it or not. This change makes I386_CPU mutually exclusive with the other cpu types, and tidies things up a little in the process. Reviewed by: alfred, markm, phk, benno, jlemon, jhb, jake, grog, msmith, jasone, dcs, des (and a bunch more people who encouraged it) 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 16 2: 1:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from bajoran.xsinet.co.za (bajoran.xsinet.co.za [196.25.196.73]) by hub.freebsd.org (Postfix) with SMTP id 021FF37B69E for ; Tue, 16 Jan 2001 02:00:50 -0800 (PST) Received: (qmail 4760 invoked from network); 16 Jan 2001 10:08:56 -0000 Received: from unknown (HELO xsinet.co.za) (192.168.2.1) by 0 with SMTP; 16 Jan 2001 10:08:56 -0000 Message-ID: <3A62E6BA.780C4957@xsinet.co.za> Date: Mon, 15 Jan 2001 14:02:03 +0200 From: Patrick Reply-To: Patrick@xsinet.co.za Organization: XSInet X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------------------------------------------------------------ Get your own free Internet access at http://www.xsinet.co.za/ ------------------------------------------------------------ Internet communications are not secure and therefore the XSInet does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of XSInet. The XSInet e-mail facility may not be used for the distribution of chain letters or offensive e-mail. XSInet hereby distances itself from and accepts no liability for the unauthorized use of its e-mail facility or the sending of e-mail communications for other than strictly business purposes. Every possible precaution has been taken to ensure that this message is virus free, however XSInet cannot be held responsible for any virus infection occurring as a result of this e-mail 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 16 4:57:12 2001 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 E5A0F37B698; Tue, 16 Jan 2001 04:56:52 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id XAA04488; Tue, 16 Jan 2001 23:56:49 +1100 Date: Tue, 16 Jan 2001 23:56:53 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: Peter Jeremy , current@FreeBSD.ORG, Mark Murray Subject: Re: Atomic breakage? 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, 15 Jan 2001, John Baldwin wrote: > On 14-Jan-01 Peter Jeremy wrote: > > And for BDE's benefit - atomic.h is broken for IA32's with 64-bit > > longs. (I believe that can be fixed for Pentiums and above using > > CMPXCHG8B, but I can't test the code). > > The i386 with 64-bit longs doesn't boot from what I hear. Also, long in > machine/types.h is 32-bits long. I don't think we need to bother with 64-bit > longs. Adding 64-bit atomic ops will be expensive on <= 486. It has booted fine for several years. I last built it on 8 Oct 2000. I haven't committed all the bits so it probably doesn't even build in -current. Erm, long isn't in machine/types.h. In , only the long limits in and a few bogus typedefs depend on the size of a long. I bother with 64-bit longs whether I need to or not :-). They get used on i386's mainly in old code and interfaces that don't use typedefs. Hopefully 64-bit scalars will never need to be accessed atomically. 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 16 6:16:50 2001 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 82F5E37B404 for ; Tue, 16 Jan 2001 06:16:29 -0800 (PST) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA04936; Tue, 16 Jan 2001 09:16:15 -0500 (EST) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id JAA19703; Tue, 16 Jan 2001 09:16:14 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA19699; Tue, 16 Jan 2001 09:16:14 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Tue, 16 Jan 2001 09:16:14 -0500 (EST) From: Kenneth Wayne Culver To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: I386_CPU In-Reply-To: <200101160947.f0G9lKs11014@mobile.wemm.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 Wont this make installing using sysinstall a bit hard? I know the generic kernel includes all the CPU lines, so that all cpu's are recognized... so are you going to just take this line out of the generic kernel, and have a special kern.flp disk with a generic kernel that only has the i386 support in it? ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 16 Jan 2001, Peter Wemm wrote: > I've requested a change for UPDATING: > > The kerrnel option I386_CPU is now mutually exclusive with the > other cpu types. If you have an i386 system, be sure that it > only had this line. Remove it for all other configurations. > > Note that this does not remove i386 support. The actual commit message > follows: > > Modified files: > sys/i386/conf NOTES > sys/i386/i386 identcpu.c machdep.c pmap.c support.s > sys/pc98/conf GENERIC > sys/pc98/i386 machdep.c > Log: > Stop doing runtime checking on i386 cpus for cpu class. The cpu is > slow enough as it is, without having to constantly check that it really > is an i386 still. It was possible to compile out the conditionals for > faster cpus by leaving out 'I386_CPU', but it was not possible to > unconditionally compile for the i386. You got the runtime checking whether > you wanted it or not. This change makes I386_CPU mutually exclusive with > the other cpu types, and tidies things up a little in the process. > > Reviewed by: alfred, markm, phk, benno, jlemon, jhb, jake, grog, msmith, > jasone, dcs, des (and a bunch more people who encouraged it) > > Cheers, > -Peter > > > > 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 16 6:29: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 30A2A37B401 for ; Tue, 16 Jan 2001 06:28:45 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id 6C5D818F0; Tue, 16 Jan 2001 09:28:43 -0500 (EST) Date: Tue, 16 Jan 2001 09:28:43 -0500 From: Will Andrews To: Kenneth Wayne Culver Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: I386_CPU Message-ID: <20010116092843.A1858@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Kenneth Wayne Culver , Peter Wemm , current@FreeBSD.ORG References: <200101160947.f0G9lKs11014@mobile.wemm.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from culverk@wam.umd.edu on Tue, Jan 16, 2001 at 09:16:14AM -0500 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 16, 2001 at 09:16:14AM -0500, Kenneth Wayne Culver wrote: > Wont this make installing using sysinstall a bit hard? I know the generic > kernel includes all the CPU lines, so that all cpu's are recognized... so > are you going to just take this line out of the generic kernel, and have a > special kern.flp disk with a generic kernel that only has the i386 support > in it? I don't think it's worth the effort. By the time 5.0-RELEASE goes out, the 386 will have been around for over 10 years (actually I think it has already reached that point and gone beyond). There are not likely to be many more installs of FreeBSD on 386's, let alone 5.x installs. People who *really* want to install 5.x on a 386 can generate their own kernel and such. --=20 wca --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6ZFqaF47idPgWcsURAkv7AJwJjtjaVEIJsVt769ht4yoCa5TnLQCdFyj6 8p3NIR2VMzGehAQ4aTi+5qw= =KlZ0 -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 6:50:38 2001 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 E884437B698 for ; Tue, 16 Jan 2001 06:50:14 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id PAA37472; Tue, 16 Jan 2001 15:50:04 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Will Andrews Cc: Kenneth Wayne Culver , Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: I386_CPU References: <200101160947.f0G9lKs11014@mobile.wemm.org> <20010116092843.A1858@puck.firepipe.net> From: Dag-Erling Smorgrav Date: 16 Jan 2001 15:50:03 +0100 In-Reply-To: Will Andrews's message of "Tue, 16 Jan 2001 09:28:43 -0500" Message-ID: Lines: 12 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 Will Andrews writes: > I don't think it's worth the effort. By the time 5.0-RELEASE goes out, > the 386 will have been around for over 10 years (actually I think it has > already reached that point and gone beyond). It's already more than 15 years old - Intel introduced the 80386 in 1985, and Compaq started shipping 80386-based systems (to IBM's dismay) in 1986. DES -- Dag-Erling Smorgrav - des@ofug.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 16 8:23:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.clones.com (unknown [216.70.178.182]) by hub.freebsd.org (Postfix) with ESMTP id DC04A37B69B for ; Tue, 16 Jan 2001 08:22:51 -0800 (PST) Received: from localhost (gross@localhost) by mail.clones.com (8.9.3/8.9.3) with ESMTP id IAA30862; Tue, 16 Jan 2001 08:23:11 -0800 Date: Tue, 16 Jan 2001 08:23:11 -0800 (PST) From: Glendon Gross To: Will Andrews Cc: Kenneth Wayne Culver , Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: I386_CPU In-Reply-To: <20010116092843.A1858@puck.firepipe.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 OK, but it makes sense to me that for certain applications, it makes sense to utilize the old hardware since it is still readily available and cheap. In particular, why not install FreeBSD on i386 for use in routers? In many cases there is a negligible performance advantage from using faster CPU's. Sure, we can build our own kernels for such applications, but if there is an i386 kernel available, it's a plus for FreeBSD in my opinion. Otherwise I would be inclined to try to put together a "distribution" of FreeBSD optimized for low-end systems. But I suspect PicoBSD already fits that requirement. On Tue, 16 Jan 2001, Will Andrews wrote: > On Tue, Jan 16, 2001 at 09:16:14AM -0500, Kenneth Wayne Culver wrote: > > Wont this make installing using sysinstall a bit hard? I know the generic > > kernel includes all the CPU lines, so that all cpu's are recognized... so > > are you going to just take this line out of the generic kernel, and have a > > special kern.flp disk with a generic kernel that only has the i386 support > > in it? > > I don't think it's worth the effort. By the time 5.0-RELEASE goes out, > the 386 will have been around for over 10 years (actually I think it has > already reached that point and gone beyond). There are not likely to be > many more installs of FreeBSD on 386's, let alone 5.x installs. > > People who *really* want to install 5.x on a 386 can generate their own > kernel and such. > > -- > wca > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 8:35:14 2001 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 5C6CC37B401 for ; Tue, 16 Jan 2001 08:34:56 -0800 (PST) Received: from rac4.wam.umd.edu (IDENT:root@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id LAA14169; Tue, 16 Jan 2001 11:34:45 -0500 (EST) Received: from rac4.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id LAA05112; Tue, 16 Jan 2001 11:34:45 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id LAA05106; Tue, 16 Jan 2001 11:34:45 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Tue, 16 Jan 2001 11:34:45 -0500 (EST) From: Kenneth Wayne Culver To: Will Andrews Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: I386_CPU In-Reply-To: <20010116092843.A1858@puck.firepipe.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 OH ok, just curious how that was going to work. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 16 Jan 2001, Will Andrews wrote: > On Tue, Jan 16, 2001 at 09:16:14AM -0500, Kenneth Wayne Culver wrote: > > Wont this make installing using sysinstall a bit hard? I know the generic > > kernel includes all the CPU lines, so that all cpu's are recognized... so > > are you going to just take this line out of the generic kernel, and have a > > special kern.flp disk with a generic kernel that only has the i386 support > > in it? > > I don't think it's worth the effort. By the time 5.0-RELEASE goes out, > the 386 will have been around for over 10 years (actually I think it has > already reached that point and gone beyond). There are not likely to be > many more installs of FreeBSD on 386's, let alone 5.x installs. > > People who *really* want to install 5.x on a 386 can generate their own > kernel and such. > > -- > wca > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 9: 8: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.dsp.uiowa.edu (mail.dsp.uiowa.edu [128.255.242.147]) by hub.freebsd.org (Postfix) with ESMTP id 6F2FE37B400 for ; Tue, 16 Jan 2001 09:07:46 -0800 (PST) Received: from dsp42 (dsp42.dsp.uiowa.edu [128.255.242.42]) by mail.dsp.uiowa.edu (8.9.3/8.9.3) with ESMTP id LAA93801 for ; Tue, 16 Jan 2001 11:07:39 -0600 (CST) Message-Id: <4.2.0.58.20010116110625.00d438c0@dsp10.dsp.uiowa.edu> X-Sender: manjoine@dsp10.dsp.uiowa.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 16 Jan 2001 11:07:33 -0600 To: current@FreeBSD.org From: Chris Manjoine Subject: error while upgrading from 4.1.1 to 4.2 in buildworld 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 below is the last lines of code in the complier on my box while doing a clean upgrade from 4.1.1 that was installed just days ago. cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DTARGET_NAME=\"i386-unknown-freebsd\" -DIN_GCC -I/usr/obj/usr/src/i386/usr/include -c ../cc_tools/insn-attrtab.c -o insn-attrtab.o cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DTARGET_NAME=\"i386-unknown-freebsd\" -DIN_GCC -I/usr/obj/usr/src/i386/usr/include -c ../cc_tools/insn-emit.c -o insn-emit.o cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DTARGET_NAME=\"i386-unknown-freebsd\" -DIN_GCC -I/usr/obj/usr/src/i386/usr/include -c ../cc_tools/insn-extract.c -o insn-extract.o cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DTARGET_NAME=\"i386-unknown-freebsd\" -DIN_GCC -I/usr/obj/usr/src/i386/usr/include -c ../cc_tools/insn-opinit.c -o insn-opinit.o cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DTARGET_NAME=\"i386-unknown-freebsd\" -DIN_GCC -I/usr/obj/usr/src/i386/usr/include -c ../cc_tools/insn-output.c -o insn-output.o {standard input}: Assembler messages: {standard input}:5945: Error: Rest of line ignored. First ignored character valued 0xb. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** 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. =~=~=~=~=~=~=~=~=~=~=~=~=~=~= Christopher A. Manjoine Webmaster Vice-President for Research The University of Iowa 2 Gilmore Hall Iowa City, IA 52242 Voice: 319-335-3019 Fax: 319-335-2130 Email: chris-manjoine@uiowa.edu =~=~=~=~=~=~=~=~=~=~=~=~=~=~= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 9:16: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from flute.daconcepts.dyndns.org (wks-29-177-219.kscable.com [24.29.177.219]) by hub.freebsd.org (Postfix) with ESMTP id D4D0E37B401 for ; Tue, 16 Jan 2001 09:15:39 -0800 (PST) Received: from localhost (natedac@localhost) by flute.daconcepts.dyndns.org (8.11.1/8.11.1) with ESMTP id f0GHHG834060 for ; Tue, 16 Jan 2001 11:17:16 -0600 (CST) (envelope-from natedac@kscable.com) X-Authentication-Warning: flute.daconcepts.dyndns.org: natedac owned process doing -bs Date: Tue, 16 Jan 2001 11:17:13 -0600 (CST) From: Nate Dannenberg X-X-Sender: To: Subject: CVSup/buildworld failure 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 Tuesday, 16 Jan. 2001, about 7am or so, received the following error message(s) from buildworld, after performing a CVSup sometime during the previous day (mid-day or so), while tracking FreeBSD 5.0-CURRENT (output slightly reformatted to correct lines where just one or two characters wouldn't fit on a previous line): ----- Text Import Begin ----- ===> sys/boot/i386/btx ===> sys/boot/i386/btx/btx (cd /usr/src/sys/boot/i386/btx/btx; m4 btx.s) | as --defsym BTX_FLAGS=0x0 -o btx.o m4: not found ld -N -e start -Ttext 0x9000 -o btx.out btx.o /usr/obj/usr/src/i386/usr/libexec/elf/ld: warning: cannot find entry symbol start; defaulting to 00009000 objcopy -S -O binary btx.out btx ===> sys/boot/i386/btx/btxldr (cd /usr/src/sys/boot/i386/btx/btxldr; m4 -DLOADER_ADDRESS=0x200000 btxldr.s ) | as -o btxldr.o m4: not found ld -N -e start -Ttext 0x200000 -o btxldr.out btxldr.o /usr/obj/usr/src/i386/usr/libexec/elf/ld: warning: cannot find entry symbol start; defaulting to 00200000 objcopy -S -O binary btxldr.out btxldr ===> sys/boot/i386/btx/lib as -elf -o btxcsu.o /usr/src/sys/boot/i386/btx/lib/btxcsu.s as -elf -o btxsys.o /usr/src/sys/boot/i386/btx/lib/btxsys.s as -elf -o btxv86.o /usr/src/sys/boot/i386/btx/lib/btxv86.s ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o ===> sys/boot/i386/boot2 as --defsym FLAGS=0x80 /usr/src/sys/boot/i386/boot2/boot1.s -o boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Os -fno-builtin -fforce-addr -fdata-sections -malign-f nctions=0 -malign-jumps=0 -malign-loops=0 -mrtd -mpreferred-stack-boundary=2 -Wall -Waggregate-return -Wbad-f nction-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshado -Wstrict-prototypes -Wwrite-strings -mpreferred-stack-boundary=2 -I/usr/obj/usr/src/i386/usr/include -c /usr src/sys/boot/i386/boot2/boot2.c as --defsym SIOPRT=0x3f8 --defsym SIOFMT=0x3 --defsym SIOSPD=9600 /usr/src/sys/boot/i386/boot2/sio.s -o sioo ld -nostdlib -static -N -Ttext 0x1000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x1000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin btxld: /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx: Not a BTX kernel *** Error code 1 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 ----- Text Import End ----- Error Codes continued for a few more directory levels before they stopped. I have not been able to buildworld for the last week or so, each time receiving a different kind of error message (and each time after CVSup'ing the latest source). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 10: 9:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id D75F137B402; Tue, 16 Jan 2001 10:09:06 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id KAA19691; Tue, 16 Jan 2001 10:09:06 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id KAA09927; Tue, 16 Jan 2001 10:09:04 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200101161809.KAA09927@curve.dellroad.org> Subject: Re: HEADSUP! New netgraph code coming In-Reply-To: "from Dag-Erling Smorgrav at Jan 15, 2001 00:53:45 am" To: Dag-Erling Smorgrav Date: Tue, 16 Jan 2001 10:09:04 -0800 (PST) Cc: Julian Elischer , Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > Julian Elischer writes: > > > Something is terribly broken with ng_ether at the moment. It lacks a > > > MODULE_VERSION line. > > is this required for something to be a depency? > > Yes. > > > Where is it documented? > > It's not, AFAIK. UTSL (like the rest of us) I don't think Julian is at fault here. At some point in the past, MODULE_VERSION wasn't required. Whoever committed the checkin that made suddenly made MODULE_VERSION required should have added it to all affected files, or at least there should have been a HEADS UP, but I don't recall seeing one. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.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 16 10:13:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5035537B402 for ; Tue, 16 Jan 2001 10:13:24 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0GIDFs29904; Tue, 16 Jan 2001 11:13:17 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101161813.f0GIDFs29904@harmony.village.org> To: Peter Wemm Subject: Re: HEADS UP: I386_CPU Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 16 Jan 2001 01:47:20 PST." <200101160947.f0G9lKs11014@mobile.wemm.org> References: <200101160947.f0G9lKs11014@mobile.wemm.org> Date: Tue, 16 Jan 2001 11:13:15 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101160947.f0G9lKs11014@mobile.wemm.org> Peter Wemm writes: : I've requested a change for UPDATING: It is in my queue... I have a few other entries I need to dust off. I'll try to do that today. 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 16 10:23:48 2001 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 30DF037B698; Tue, 16 Jan 2001 10:23:27 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id TAA38341; Tue, 16 Jan 2001 19:23:19 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Archie Cobbs Cc: Julian Elischer , Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP! New netgraph code coming References: <200101161809.KAA09927@curve.dellroad.org> From: Dag-Erling Smorgrav Date: 16 Jan 2001 19:23:18 +0100 In-Reply-To: Archie Cobbs's message of "Tue, 16 Jan 2001 10:09:04 -0800 (PST)" Message-ID: Lines: 12 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 Archie Cobbs writes: > At some point in the past, MODULE_VERSION wasn't required. Whoever > committed the checkin that made suddenly made MODULE_VERSION required > should have added it to all affected files, or at least there should > have been a HEADS UP, but I don't recall seeing one. If I recall correctly, it was Mike, and the commit message was fairly explicit. DES -- Dag-Erling Smorgrav - des@ofug.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 16 10:33:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 7D52837B400; Tue, 16 Jan 2001 10:32:49 -0800 (PST) Received: from localhost (IDENT:NPYhR7m0/keB2l0njWmU5faYY4HyrdsiKCr1MctPmgOJOIBu0tBlainNO1EELuZc@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.2/8.11.2/peace) with ESMTP/inet6 id f0GIVMa01396; Wed, 17 Jan 2001 03:31:24 +0900 (JST) (envelope-from ume@FreeBSD.org) Date: Wed, 17 Jan 2001 03:31:19 +0900 (JST) Message-Id: <20010117.033119.41625993.ume@FreeBSD.org> To: current@freebsd.org, hackers@freebsd.org Subject: [CFR] number of processes forked since boot From: Hajimu UMEMOTO X-Mailer: Mew version 1.95b97 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Wed_Jan_17_03:31:19_2001_646)--" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Wed_Jan_17_03:31:19_2001_646)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I received the patch to add counter for fork() set from Paul. I've tested it on my -CURRENT and -STABLE boxes, and it seems fine for me. So, I post his patch for review. Thanks, Paul. ----Next_Part(Wed_Jan_17_03:31:19_2001_646)-- Content-Type: Application/Octet-Stream Content-Transfer-Encoding: base64 Content-Description: fork.patch.gz Content-Disposition: attachment; filename="fork.patch.gz" H4sICGLWYzoCA2ZvcmsucGF0Y2gAvVf7b9s2EP7Z/isOGTY4kR29bKeSlyJpEhdB8yicdMOAAYIs UYlgvUBSzGPr/z6Skm0pljKna2cYkkzyvu9E3n2+O0989GgDeSLqAuFEXpwgxYt9r3v43z/d2ckN BGGEbFDv0xipiceISrCnNjH2WRcjikPEwuQOML+RME1A37f0rh8GAQxyGGDxE6p+DgaDxhfoGJqm qbqhGibolj00bc3qSDBFUVotdJV/9TFohj0ybdPoHh3BYDzqj0Hh1wM4OurCT2HiRbmP4FcWqyx2 0CPlIPv37zenntMEyYmusp4S3CyOEbd6YSRmclIOd4FQl4YeXB5fXFyfOKdn0/Ors96lc3w7vZ59 6sOOS4XjO6sn8NwomrveYmd3Ih0f6dLzkT7u64XvHdgD9Ii8nIq9zVx6D5ErHAHohfyc/BAjj0ZP ECY0BeELxKmPdqWlyq/8pQRVL9P7kBl9CCL3jnA6pat0wgB68jccHkJvNp2efoS/YTb9PLs+2d2F v/iSjpfQfSYhiKJM6iOZe4cIKIccePA+c1hMMtdDg/ec0yfhMwKlYYaIGQH0FVBEELzmRPHw+ffj 81v5eHl2WfeLbTrGvptnFR68yYO/A48Imo66Vxzzh5QfboZTDxHCQV2MgCAKedaHJH0A7x55C7Fb bvIEUer67jxC4rDziK9+cBPaPV/LQxHORcz+D9pQo2sVhqFZE4ahCRUfl7pQg1qJgm6Cptn6ga2N OhJoKQobywtFGIEh5MAejWVimYYpEkvc9HdFYjGHpwzCOM+oE2CEnDhM+nByezG9OP7ozE778Etx 0E3LNJ7DImnh5o8bbuKcX932HHG0XAEIX0K8PlyfnzrHX26v+5zsGeHUEcHieGme0Bc83FDOyVXl giWDUjJ8qVOwuEqgdMoUbXyBckYgXuXxnEtEGoAUhV2pQORNPKydiDUysW+mwu1UuJEKfzPVKplb d7CcFYS/XUKR+G4QcPVFPsyfyg19+1a2s7JtaNk38OLXefE2vHjNy/8QA9C2zgUZ6rFLFi/IK+PL 4C8FLSd4fx4mPNEFZnn70bLWQtoqbqZVEzfTgpWfQtpa4AqB00b8C/rY1g5sXetIMCFwrxhVZW5k j6yi8NF0Wfnwm1WoXI+lob+bYS5iQW/nZysHkgb0Qfy5rHSN/JnwmoTkMT97MSuOtMGQYjerLhW/ W5ZyYaYoLtKwCv5ExJAI1QajmiRVrGSmt9iwFhv2mhFuMcJLo8ZXenAzmQZYXsOk9mJ8Mky2syTy 6vPtfwGQ3ZFtMdKcvqTnQ2UROdbfySAwXgkC8U8jwj5auoSRGEJ+BTV9DlK/xR/+hN2EhBTmUeot RCoIIAjcPKq5Vi5sC6mUuhFwfSnsgLoLVN0WUbzKmZaT3JSlMohehI9ctzUG28BgbwfBGyC4CgKt IKLIqB4DFQP/biE4fRfFaXX//O1t0WNI5TEuC9AKTFbCVOrLWk/04+vLGl2rBBv1xtPQYe3isrys IXV0y7Jkz2mBNrSNoT0UPaex7jnry6sN59A2Ldt8J1POMkTG8SsXZJlxuQh8YE6ZrKvKcQIA6h7w J0iKqqU4Box458b4SfAYkd0yior2bQm0WYROBNDKLlnVQOW5chxh6fFmsI4k7QliCKMJ7z2geAQf ZRGSTeYKY44i3nfQ+5DrAxUgiuhVFNGrTHkoqzIrVBnW4Ho0ZCF92pfzYumKT4jqpCOo1k7WtL6+ njUasHYD3GiA2w1WeTipmzTWOUtPN33cGoI1QeA3QeA1BHwtKi4fBeB8OptdnV3wNvIfJzXAthoS AAA= ----Next_Part(Wed_Jan_17_03:31:19_2001_646)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Description: My Signature Content-Disposition: inline; filename=".signature-world" Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ ----Next_Part(Wed_Jan_17_03:31:19_2001_646)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 11: 5:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5485537B6A4; Tue, 16 Jan 2001 11:05:09 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0GJ58s30294; Tue, 16 Jan 2001 12:05:08 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101161905.f0GJ58s30294@harmony.village.org> To: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld In-reply-to: Your message of "Thu, 11 Jan 2001 17:43:32 PST." <20010111174332.B74480@dragon.nuxi.com> References: <20010111174332.B74480@dragon.nuxi.com> <20010111220021.C79365@strontium.scientia.demon.co.uk> Date: Tue, 16 Jan 2001 12:05:08 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010111174332.B74480@dragon.nuxi.com> "David O'Brien" writes: : But disklabel/fdisk can't even accept MB's as a unit. Until they grow : the functionality of the NetBSD and OpenBSD versions of them, sysinstall : is really the only tolerable disk label manipulation tool our users have. : This includes those with a bummed /usr that needs to install a new disk : to get it back. I have patches in my tree from someone to do this the last time this issue came up. 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 16 11:13: 2 2001 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 5C8A137B69C; Tue, 16 Jan 2001 11:12:40 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0GJCeg19242; Tue, 16 Jan 2001 11:12:40 -0800 (PST) Date: Tue, 16 Jan 2001 11:12:40 -0800 From: Alfred Perlstein To: Hajimu UMEMOTO Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: [CFR] number of processes forked since boot Message-ID: <20010116111239.U7240@fw.wintelcom.net> References: <20010117.033119.41625993.ume@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010117.033119.41625993.ume@FreeBSD.org>; from ume@FreeBSD.ORG on Wed, Jan 17, 2001 at 03:31:19AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Hajimu UMEMOTO [010116 10:33] wrote: > Hi, > > I received the patch to add counter for fork() set from Paul. I've > tested it on my -CURRENT and -STABLE boxes, and it seems fine for me. > So, I post his patch for review. > > Thanks, Paul. I like this a lot. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 13: 0:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 6F49D37B400; Tue, 16 Jan 2001 13:00:28 -0800 (PST) Received: from victoria-074.budapest.interware.hu ([195.70.63.74] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14IdDI-0000J7-00; Tue, 16 Jan 2001 22:00:21 +0100 Message-ID: <3A64AA23.30035A1C@elischer.org> Date: Tue, 16 Jan 2001 12:08:03 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Bruce Evans Cc: John Baldwin , Peter Jeremy , current@FreeBSD.ORG, Mark Murray Subject: Re: Atomic breakage? References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > On Mon, 15 Jan 2001, John Baldwin wrote: > > > On 14-Jan-01 Peter Jeremy wrote: > > > And for BDE's benefit - atomic.h is broken for IA32's with 64-bit > > > longs. (I believe that can be fixed for Pentiums and above using > > > CMPXCHG8B, but I can't test the code). > > > > The i386 with 64-bit longs doesn't boot from what I hear. Also, long in > > machine/types.h is 32-bits long. I don't think we need to bother with 64-bit > > longs. Adding 64-bit atomic ops will be expensive on <= 486. > > It has booted fine for several years. I last built it on 8 Oct 2000. I > haven't committed all the bits so it probably doesn't even build in -current. > > Erm, long isn't in machine/types.h. In , only the long limits in > and a few bogus typedefs depend on the size of a long. > > I bother with 64-bit longs whether I need to or not :-). They get used on > i386's mainly in old code and interfaces that don't use typedefs. > Hopefully 64-bit scalars will never need to be accessed atomically. Too late. Many statistics in interfaces (i.e. bytes transmitted) are already 64 bit words. > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 13:24:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from web11001.mail.yahoo.com (web11001.mail.yahoo.com [216.136.131.51]) by hub.freebsd.org (Postfix) with SMTP id 29F7F37B401 for ; Tue, 16 Jan 2001 13:24:09 -0800 (PST) Message-ID: <20010116212409.88898.qmail@web11001.mail.yahoo.com> Received: from [212.37.166.161] by web11001.mail.yahoo.com; Tue, 16 Jan 2001 13:24:09 PST Date: Tue, 16 Jan 2001 13:24:09 -0800 (PST) From: jega uba Subject: confidential business relationship To: uba_jega_p@yahoo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FROM:DR.UBA JEGA. SATELLITE TEL.871-761-8888-31. SATELLITE FAX.871-761-8888-32. ATTN:PRESIDENT/CEO. STRICTLY CONFIDENTIAL & URGENT BUSINESS PROPOSAL. RE:TRANSFER OF U$21,500.000{TWENTY ONE MILLION FIVE HUNDRED THOUSAND US DOLLARS ONLY. I AM A MEMBER OF THE FEDERAL GOVERNMENT OF NIGERIA NATIONAL PETROLEUM CORPORATION(NNPC) SOMETIME AGO, A CONTRACT WAS AWARDED TO A FOREIGN FIRM IN THE PTF BY MY COMMITTEE. THIS CONTRACT WAS OVER INVOICED TO THE TUNE OF US$21.5M US DOLLARS. THIS WAS DONE DELIBRATELY. THE OVER- INVOICING WAS A DEAL BY MY COMMITTEE TO BENEFIT FROM THE PROJECT. WE NOW WANT TO TRANSFER THIS MONEY WHICH IS IN A SUSPENSE ACCOUNT WITH PTF INTO ANY OVERSEA ACCOUNT WHICH WE EXPECT YOU TO PROVIDE FOR US. SHARE: 60% WILL BE FOR MY PARTNERS AND ME. 30% OF THE MONEY WILL BE YOURS FOR PROVIDING THE ACCOUNT WHERE WE SHALL REMIT THE MONEY. 10% HAS BEEN MAPPED OUT FROM THE TOTAL SUM TO COVER ANY EXPENSES THAT MAY BE INCURRED BY US DURING THE COURSE OF THIS TRANSFER, BOTH LOCAL AND INTERNATIONAL EXPENSES. IT MAY INTEREST YOU TO KNOW THAT SIMILAR TRANSACTION WAS CARRIED OUT WITH ONE MR. PATRICE MILLER, PRESIDENT OF CRANE INTERNATIONAL TRADING CORP. OF 153 EAST 57TH ST; 28TH FLOOR, NY10022, TELEPHONE: 212-3087788 AND TELEX:6731689. THE DEAL WAS CONCLUDED AND ALL COVERING DOCUMENTS WERE FOWARDED TO MR. MILLER TO AUTHENTICATE THE CLAIM. ONCE THE FUNDS WERE TRANSFERRED, MR. MILLER PRESENTED HIS BANK WITH ALL THE LEGAL DOCUMENTS AND REMITTED THE WHOLE FUNDS TO ANOTHER BANK ACCOUNT AND DISAPPEARED COMPLETELY. MY COLLEAGUES WERE SHATTERED, SINCE SUCH OPPORTUNITIES ARE NOT EASY TO COME BY. AT THIS JUNCTURE, I WOULD LIKE TO LET YOU KNOW THAT IF YOU ARE INTERESTED IN ASSISTING US IN THIS DEAL, WE WOULD REQUIRE THE FOLLOWING INFORMATION FROM YOU, WHICH WOULD ENABLE US MAKE FORMAL APPLICATION TO THE VARIOUS MINISTRIES\PARASTATAL FOR THE RELEASE AND ONWARD TRANSFER OF THE MONEY TO YOUR ACCOUNT. THE INFORMATION WE REQUIRE ARE: YOUR NAME, COMPANY`S NAME, ADDRESS , TELEFAX NUMBER. YOUR BANK NAME ,ADDRESS, TELEFAX NUMBER. YOUR BANK ACCOUNT NUMBER AND BENEFICIARY NAME. WE HAVE STRONG RELIABLE CONNECTIONS AT THE CENTRAL BANK OF NIGERIA AND OTHER GOVERNMENT PARASTATALS TO ASSIST US IN THE DEAL, AND WHEN IT IS FINALLY CONCLUDED WE SHALL USE SAME CONTACTS TO WITHDRAW ALL DOCUMENTS USED TO AVOID ANY TRACE TO YOU OR US. IT MIGHT ALSO INTEREST YOU TO KNOW THAT WE ARE ORDINARY CIVIL SERVANTS WHO DO NOT WANT TO MISS THIS OPPORTUNITY, SINCE WE WANT THIS MONEY TRANSFERRED BEFORE THE NEWLY DEMOCRATICALLY ELECTED GOVERNMENT STARTS PROBING THE ACTIVITIES OF ALL PREVIOUS MILITARY GOVERNMENTS. PLEASE CONTACT ME THROUGH MY ABOVE TEL\FAX NUMBER WHETHER OR NOT YOU ARE INTRESTED IN THIS DEAL. IF YOU ARE NOT IT WILL ENABLE ME SCOUT FOR ANOTHER FOREIGN PARTNER TO ASSIST US. BUT IF YOU ARE INTRESTED PLEASE SEND THE REQUIRED INFORMATION IMMEDIATELY SO THAT WE CAN SWING INTO ACTION, SINCE TIME IS NOT ON OUR PART. I WAIT IN ANTICIPATION OF YOUR FULLEST CO-COPERATION. YOURS FAITHFULLY, DR.UBA JEGA. __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.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 16 13:38:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id BCAF237B698; Tue, 16 Jan 2001 13:38:27 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id NAA20825; Tue, 16 Jan 2001 13:38:20 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id NAA10547; Tue, 16 Jan 2001 13:38:14 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200101162138.NAA10547@curve.dellroad.org> Subject: Re: HEADSUP! New netgraph code coming In-Reply-To: "from Dag-Erling Smorgrav at Jan 16, 2001 07:23:18 pm" To: Dag-Erling Smorgrav Date: Tue, 16 Jan 2001 13:38:14 -0800 (PST) Cc: Archie Cobbs , Julian Elischer , Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > > At some point in the past, MODULE_VERSION wasn't required. Whoever > > committed the checkin that made suddenly made MODULE_VERSION required > > should have added it to all affected files, or at least there should > > have been a HEADS UP, but I don't recall seeing one. > > If I recall correctly, it was Mike, and the commit message was fairly > explicit. It seems like fairly explicit commit message wasn't sufficient then. Whatever.. developers should pay more attention and committers should be more explicit. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.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 16 13:56:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (Postfix) with ESMTP id 6C81F37B401 for ; Tue, 16 Jan 2001 13:56:31 -0800 (PST) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA04369 for ; Tue, 16 Jan 2001 13:56:27 -0800 (PST) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.9) with ESMTP id XAA06028 for ; Tue, 16 Jan 2001 23:56:07 +0200 (EET) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id XAA01821; Tue, 16 Jan 2001 23:56:05 +0200 (EET) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14948.50037.587296.913304@ultrahot.Finland.Sun.COM> Date: Tue, 16 Jan 2001 23:56:05 +0200 To: freebsd-current@freebsd.org Subject: modified ich sound driver for current? X-Mailer: VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mixer stuff was modified couple days ago. Does anyone have working ich driver? I got original driver from http://www.katsurajima.seya.yokohama.jp/ich/index.en.html but now this site is dead. Does author (Katsurajima Naoto) of this driver read FreeBSD mailing lists? Could someone include this driver to current so it get updated? -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 14: 0:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [171.66.112.163]) by hub.freebsd.org (Postfix) with ESMTP id D1FED37B400 for ; Tue, 16 Jan 2001 14:00:13 -0800 (PST) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id NAA59204; Tue, 16 Jan 2001 13:50:18 -0800 (PST) Date: Tue, 16 Jan 2001 13:50:18 -0800 (PST) From: Annelise Anderson To: Nate Dannenberg Cc: current@FreeBSD.ORG Subject: Re: CVSup/buildworld failure 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 -current with sources as of 1 a.m. PST 1/16/01 built okay for me, and runs fine. Annelise On Tue, 16 Jan 2001, Nate Dannenberg wrote: > > Tuesday, 16 Jan. 2001, about 7am or so, received the following error > message(s) from buildworld, after performing a CVSup sometime during the > previous day (mid-day or so), while tracking FreeBSD 5.0-CURRENT (output > slightly reformatted to correct lines where just one or two characters > wouldn't fit on a previous line): > > ----- Text Import Begin ----- > ===> sys/boot/i386/btx > ===> sys/boot/i386/btx/btx > (cd /usr/src/sys/boot/i386/btx/btx; m4 btx.s) | as --defsym BTX_FLAGS=0x0 -o btx.o > m4: not found > ld -N -e start -Ttext 0x9000 -o btx.out btx.o > /usr/obj/usr/src/i386/usr/libexec/elf/ld: warning: cannot find entry symbol start; defaulting to 00009000 > objcopy -S -O binary btx.out btx > ===> sys/boot/i386/btx/btxldr > (cd /usr/src/sys/boot/i386/btx/btxldr; m4 -DLOADER_ADDRESS=0x200000 btxldr.s ) | as -o btxldr.o > m4: not found > ld -N -e start -Ttext 0x200000 -o btxldr.out btxldr.o > /usr/obj/usr/src/i386/usr/libexec/elf/ld: warning: cannot find entry symbol start; defaulting to 00200000 > objcopy -S -O binary btxldr.out btxldr > ===> sys/boot/i386/btx/lib > as -elf -o btxcsu.o /usr/src/sys/boot/i386/btx/lib/btxcsu.s > as -elf -o btxsys.o /usr/src/sys/boot/i386/btx/lib/btxsys.s > as -elf -o btxv86.o /usr/src/sys/boot/i386/btx/lib/btxv86.s > ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o > ===> sys/boot/i386/boot2 > as --defsym FLAGS=0x80 /usr/src/sys/boot/i386/boot2/boot1.s -o boot1.o > ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o > objcopy -S -O binary boot1.out boot1 > dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null > cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Os -fno-builtin -fforce-addr -fdata-sections -malign-f > nctions=0 -malign-jumps=0 -malign-loops=0 -mrtd -mpreferred-stack-boundary=2 -Wall -Waggregate-return -Wbad-f > nction-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshado > -Wstrict-prototypes -Wwrite-strings -mpreferred-stack-boundary=2 -I/usr/obj/usr/src/i386/usr/include -c /usr > src/sys/boot/i386/boot2/boot2.c > as --defsym SIOPRT=0x3f8 --defsym SIOFMT=0x3 --defsym SIOSPD=9600 /usr/src/sys/boot/i386/boot2/sio.s -o sioo > ld -nostdlib -static -N -Ttext 0x1000 -o boot2.out > /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot.o sio.o > objcopy -S -O binary boot2.out boot2.bin > btxld -v -E 0x1000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o > boot2.ld -P 1 > boot2.bin > btxld: /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx: Not a BTX kernel > *** Error code 1 > > Stop in /usr/src/sys/boot/i386/boot2. > *** Error code 1 > ----- Text Import End ----- > > Error Codes continued for a few more directory levels before they stopped. > I have not been able to buildworld for the last week or so, each time > receiving a different kind of error message (and each time after CVSup'ing > the latest source). > > > > 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 16 14: 7: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id B0F1B37B402; Tue, 16 Jan 2001 14:06:33 -0800 (PST) Received: from husten.security.at12.de (dial-213-168-72-78.netcologne.de [213.168.72.78]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id XAA16748; Tue, 16 Jan 2001 23:06:30 +0100 (MET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.1/8.11.1) with ESMTP id f0GM6EV11755; Tue, 16 Jan 2001 23:06:14 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Tue, 16 Jan 2001 23:06:14 +0100 (CET) From: Paul Herman To: Hajimu UMEMOTO Cc: , Subject: Re: [CFR] number of processes forked since boot In-Reply-To: <20010117.033119.41625993.ume@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1518330454-979682654=:341" Content-ID: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1518330454-979682654=:341 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: On Wed, 17 Jan 2001, Hajimu UMEMOTO wrote: > I received the patch to add counter for fork() set from Paul. I've > tested it on my -CURRENT and -STABLE boxes, and it seems fine for me. > So, I post his patch for review. I do have a change (I knew I forgot something.) This is exactly the same patch, but counts kernel thread forks to boot. I've tested it on -CURRENT and seems fine for me as well. -Paul. --0-1518330454-979682654=:341 Content-Type: APPLICATION/OCTET-STREAM; NAME="fork_kthreads.patch.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="fork_kthreads.patch.gz" H4sICAXFZDoCA2Zvcmtfa3RocmVhZHMucGF0Y2gAvVj7b9s2EP7Z/isOGVY4 lR097KSzvBRJk7gImkfhphsGDBBkiUoE6wVSYh5b//cdKdmWbMmzs3aGIckk 7/uOvLtPpC8jlzyZwJ6ZOiM0khfLi+nswGkf//dPe3L2BTw/ICaoD3FI1Mjh TGXUUesYu7xNSUp9wv3oHijemB9HoB8M9bbrex70MuhR8RPKfvZ6vdoJtAxN 01TdUI0+6ENz0De1YUuCKYrSaKGr+NWPwNDNwcDU37VPTqB3dNg9AgWv7+Dk pA0/+ZETZC6BX3mo8tAiTymCHDy8X+96iSMiO9rKsktw8zAkaLViJHoyVjS3 gaV26jtwfXp1dXtmnV+ML28uOtfW6d34dvKpC3t2KhzfWzyBYwfB1HZme/sj 6fihLj0/1I+6hiZ9b8FbIE/EyVKxtomdPkBgC0cAOj7GyfUpcdLgGfwojUH4 AmHskn1pqeIVJyWoOonehcToghfY9wzplLbS8j3oyN9wfAydyXh8/hH+hsn4 8+T2bH8f/sIhLSdKD7iEYIoyqrYk9j1hoBwjcO99YvGQJbZDeu+R02X+CwGl poeJHgH0DUjACGxyIn/4/Pvp5Z18vL64rvrF1x3j39WzRBduvUlo7GgV5ln6 QIntVrmLxu/CXuKi67Ok32GWImVb6ts8yT7EmFpimoQxBLUpAUZSyJIuRPEj OA/EmYkVsaNnCGLbtacBEamWBTj60Y7S9uVSnCoV8+OVqULXKEtGVZYMHZYu zkWpgtTSh8OhVKQhaAPTGJgDoUjGUpGqw6tyZBhmfyiremiIosarnutRK7Ow WoFbIn5xlloeJcQK/WgEAOpbwCeIsnCKtZxHmBKsa05cwKBLLSVBXtxzILwS SrOkDIVAC7sCLfYKQIEjLB2UiiqStGeEE0pGmBuQP4JLkoBICVpgTEmAeZE+ +AySVIAoIpcUkUtjzE1V1qEq8xRsJ/W5nz4fyH4xdMEnMnvUElRLJ6Vg7Ut1 ZNXhvHY8bzagtQa02WBe16MNLk2fS1GozkWuzYrtb9fFktmeh2KN8UCAAnB9 dlsj8DoIuhMErYMoi9gOM6ksCnwbifek5xIPrE8Xk5uLK1SbkkLkr9u8cv6H vUuFrlEhBv2KQgz6UPJxLhEVqMWmRe+DpuH+w9QOWxJoLhFrw8sSMTC1gZSI vtEXGiFuhpGLRF1Vd+Hs7mp8dfrRmpx34U3+KqgbpuEeQ2wq4MsfX9DEury5 61hC/HGHwnAIc7pwe3lunX69u+0i2QuhsZQjy4mzKF3hQUPZJ0cVA+YMSsHw tUrBwzKB0ioqvXYCRY9AvKktuJ14eDMRr2Xir6aizVS0loq+mmouS7Vky87m NVzW585RkyXfGLmiVzBvkIfdQ9jMyreh5a/gpZt56Ta89BW8ZcXdFODtlroa aaHCoG0tBLLOQ5vNVvwotc8rv1DzjNGDqR+hygnM4vajNb2BtFHZcSdWVvb+ EBZ+Cl1vgMvVXTvEL+hHpvbO1LWWBBPqvsGofCrFo6yRn0o1XR5L8aYXh7sO j313P6Eo4V5n7+dhBiz20kex+V6oOvszwhMjy0LMA9ErYlpjmFI7KQ8VvxuG 4mspJWEuC2XwZyaaROLWGBXv9kJpwMEbZl3JfC5CDfYVMSqZSZ1ssOENNnyT EW0wonOj2iV5tBNZUPmW248qC4OdfrSdJZNXF8O3ApDcs20x8EiwSo9NxV8E R/ovMosMY0MWiRe1KJxg7hMloqkSr/jFi90Gh/CJ2hHzU5gGsTMTxSSAwLOz oOJbMbApJ+PUDsSmMbeD1J6R8rqI/yZkT0Mo1xWukoV5EmKBr2ehtNwatcjN lazcDYOvYfDdQegaCC2DQCOI2PmVg5uKhn+3EJyuTcLKErrb25InP5XJMf/f oASTFDD/ANTUkO+0FAAA --0-1518330454-979682654=:341-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 14: 8:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from vilnya.demon.co.uk (vilnya.demon.co.uk [158.152.19.238]) by hub.freebsd.org (Postfix) with ESMTP id 1454B37B400 for ; Tue, 16 Jan 2001 14:08:08 -0800 (PST) Received: from haveblue (haveblue.rings [10.2.4.5]) by vilnya.demon.co.uk (Postfix) with SMTP id DA6FED9B8; Tue, 16 Jan 2001 22:08:05 +0000 (GMT) Message-ID: <005401c08008$ec192b20$0504020a@haveblue> From: "Cameron Grant" To: , References: <14948.50037.587296.913304@ultrahot.Finland.Sun.COM> Subject: Re: modified ich sound driver for current? Date: Tue, 16 Jan 2001 22:08:57 -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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mixer stuff was modified couple days ago. Does anyone have working > ich driver? I got original driver from more than that, a couple of weeks would be closer. > http://www.katsurajima.seya.yokohama.jp/ich/index.en.html but now this > site is dead. Does author (Katsurajima Naoto) of this driver read > FreeBSD mailing lists? Could someone include this driver to current > so it get updated? i'm not happy with some of the things the driver does, so until i can modify it i won't commit it. this necessitates having hardware to test with, which i should be getting in the near future. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 14:22:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id 7E1D937B402 for ; Tue, 16 Jan 2001 14:22:24 -0800 (PST) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au with ESMTP id JAA45779 for ; Wed, 17 Jan 2001 09:22:16 +1100 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.5.1.R) for ; Wed, 17 Jan 2001 09:21:32 +1100 Reply-To: From: "Chris Knight" To: Cc: Subject: RE: modified ich sound driver for current? Date: Wed, 17 Jan 2001 09:21:31 +1100 Message-ID: <007c01c0800a$ae30b5b0$020aa8c0@aims.private> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <14948.50037.587296.913304@ultrahot.Finland.Sun.COM> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Return-Path: chris@aims.com.au X-MDaemon-Deliver-To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, I modified the mentioned driver when newpcm got kobjified and submitted the patches back to the author. I didn't get a reply. I haven't synced up my laptop to current since about the new year, so I don't know if it works with any changes made. Rather than send the patch to the list, I'll e-mail it to anyone that asks. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Tomi > Vainio - Sun > Finland - > Sent: Wednesday, 17 January 2001 8:56 > To: freebsd-current@FreeBSD.ORG > Subject: modified ich sound driver for current? > > > Mixer stuff was modified couple days ago. Does anyone have working > ich driver? I got original driver from > http://www.katsurajima.seya.yokohama.jp/ich/index.en.html but now this > site is dead. Does author (Katsurajima Naoto) of this driver read > FreeBSD mailing lists? Could someone include this driver to current > so it get updated? > > -- > SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 > ESPOO, Finland > Tomi Vainio (System Support Engineer) +358 9 52556300 hotline > email: Tomi.Vainio@Sun.COM +358 9 52556252 fax > > > 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 16 14:36:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A0EA737B698 for ; Tue, 16 Jan 2001 14:36:03 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id f0GMa1822504 for freebsd-current@FreeBSD.ORG; Tue, 16 Jan 2001 23:36:01 +0100 (CET) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.1/8.11.0) with SMTP id f0GMZrm14246 for ; Tue, 16 Jan 2001 23:35:54 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <009a01c0800c$b63ba920$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: References: <20010116212409.88898.qmail@web11001.mail.yahoo.com> Subject: Scam warning, was Re: confidential business relationship Date: Tue, 16 Jan 2001 23:36:02 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hope I don't offend anyones intelligence... This is a typical Nigerian 4-1-9 scam. To read more, just do a search on google: http://www.google.com/search?q=nigeria+scam+4+1+9 Leif ----- Original Message ----- From: "jega uba" To: Sent: Tuesday, January 16, 2001 10:24 PM Subject: confidential business relationship > FROM:DR.UBA JEGA. > SATELLITE TEL.871-761-8888-31. > SATELLITE FAX.871-761-8888-32. > > ATTN:PRESIDENT/CEO. > > STRICTLY CONFIDENTIAL & URGENT BUSINESS PROPOSAL. > > RE:TRANSFER OF U$21,500.000{TWENTY ONE MILLION FIVE > HUNDRED THOUSAND US DOLLARS ONLY. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 15: 1: 6 2001 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 69F3437B404; Tue, 16 Jan 2001 15:00:46 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0GN0cm26181; Tue, 16 Jan 2001 15:00:38 -0800 (PST) Date: Tue, 16 Jan 2001 15:00:38 -0800 From: Alfred Perlstein To: Archie Cobbs Cc: Dag-Erling Smorgrav , Julian Elischer , Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP! New netgraph code coming Message-ID: <20010116150038.X7240@fw.wintelcom.net> References: <200101162138.NAA10547@curve.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101162138.NAA10547@curve.dellroad.org>; from archie@dellroad.org on Tue, Jan 16, 2001 at 01:38:14PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Archie Cobbs [010116 13:39] wrote: > Dag-Erling Smorgrav writes: > > > At some point in the past, MODULE_VERSION wasn't required. Whoever > > > committed the checkin that made suddenly made MODULE_VERSION required > > > should have added it to all affected files, or at least there should > > > have been a HEADS UP, but I don't recall seeing one. > > > > If I recall correctly, it was Mike, and the commit message was fairly > > explicit. > > It seems like fairly explicit commit message wasn't sufficient then. > Whatever.. developers should pay more attention and committers should > be more explicit. ~ % man 9 module No entry for module in section 9 of the manual ~ % man 9 MODULE No entry for MODULE in section 9 of the manual ~ % man 9 MODULE_VERSION No entry for MODULE_VERSION in section 9 of the manual ? This ought to be documented. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 17:11:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from VL-MS-MR003.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 8CD1D37B69C for ; Tue, 16 Jan 2001 17:11:12 -0800 (PST) Received: from jehovah ([24.201.144.31]) by VL-MS-MR003.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G7A8MN00.I8A; Tue, 16 Jan 2001 20:11:11 -0500 Message-ID: <00b001c08022$95a18d90$1f90c918@jehovah> From: "Bosko Milekic" To: "Peter Wemm" , "Warner Losh" Cc: References: <200101160947.f0G9lKs11014@mobile.wemm.org> <200101161813.f0GIDFs29904@harmony.village.org> Subject: Re: HEADS UP: I386_CPU Date: Tue, 16 Jan 2001 20:12:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sorry guys, I haven't been really "up-to-date" on this thread, but I was wondering: can config be made to define I386_CPU 0 if any other cpus are defined (or the inverse behavior)? (Maybe this was already done?) In the sysinstall case, I think it's safe to just exclude all other processors and use the slower I386_CPU kernel. Since the GENERIC kernel config file may contain all of the different CPU types, the config hack may ensure that we're excluding I386_CPU code. Cheers, Bosko. Warner wrote: > In message <200101160947.f0G9lKs11014@mobile.wemm.org> Peter Wemm writes: > : I've requested a change for UPDATING: > > It is in my queue... I have a few other entries I need to dust off. > I'll try to do that today. > > Warner > > > 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 16 19: 3:33 2001 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 96B3D37B401; Tue, 16 Jan 2001 19:03:13 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id OAA30207; Wed, 17 Jan 2001 14:03:06 +1100 Date: Wed, 17 Jan 2001 14:03:14 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Julian Elischer Cc: John Baldwin , Peter Jeremy , current@FreeBSD.ORG, Mark Murray Subject: Re: Atomic breakage? In-Reply-To: <3A64AA23.30035A1C@elischer.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, 16 Jan 2001, Julian Elischer wrote: > Bruce Evans wrote: > > I bother with 64-bit longs whether I need to or not :-). They get used on > > i386's mainly in old code and interfaces that don't use typedefs. > > Hopefully 64-bit scalars will never need to be accessed atomically. > > Too late. > > Many statistics in interfaces (i.e. bytes transmitted) are already 64 bit > words. These don't use atomic operations (hint: no 64-bit atomic operations are implemented on i386's). If they need to be atomic, then they must use locks. 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 16 19:10:30 2001 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 9F81237B401; Tue, 16 Jan 2001 19:10:13 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0H3AAc03611; Tue, 16 Jan 2001 19:10:10 -0800 (PST) Date: Tue, 16 Jan 2001 19:10:10 -0800 From: Alfred Perlstein To: Bruce Evans Cc: Julian Elischer , John Baldwin , Peter Jeremy , current@FreeBSD.ORG, Mark Murray Subject: Re: Atomic breakage? Message-ID: <20010116191009.E7240@fw.wintelcom.net> References: <3A64AA23.30035A1C@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Wed, Jan 17, 2001 at 02:03:14PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Bruce Evans [010116 19:03] wrote: > On Tue, 16 Jan 2001, Julian Elischer wrote: > > > Bruce Evans wrote: > > > I bother with 64-bit longs whether I need to or not :-). They get used on > > > i386's mainly in old code and interfaces that don't use typedefs. > > > Hopefully 64-bit scalars will never need to be accessed atomically. > > > > Too late. > > > > Many statistics in interfaces (i.e. bytes transmitted) are already 64 bit > > words. > > These don't use atomic operations (hint: no 64-bit atomic operations are > implemented on i386's). If they need to be atomic, then they must use > locks. Just wondering, can't you use 'LOCK addl' and then use 'LOCK addc'? add longword, add longword with carry? I know it would be pretty ugly, but it should work, no? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 19:28: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 6553737B401; Tue, 16 Jan 2001 19:27:43 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id OAA20864; Wed, 17 Jan 2001 14:27:02 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01JZ0MHXAABKGKTS96@cim.alcatel.com.au>; Wed, 17 Jan 2001 14:27:02 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id f0H3Qs399271; Wed, 17 Jan 2001 14:26:54 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Wed, 17 Jan 2001 14:26:54 +1100 From: Peter Jeremy Subject: Re: Atomic breakage? In-reply-to: <20010116191009.E7240@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Jan 16, 2001 at 07:10:10PM -0800 To: Alfred Perlstein Cc: Bruce Evans , Julian Elischer , John Baldwin , current@FreeBSD.ORG, Mark Murray Mail-followup-to: Alfred Perlstein , Bruce Evans , Julian Elischer , John Baldwin , current@FreeBSD.ORG, Mark Murray Message-id: <20010117142654.A98607@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <3A64AA23.30035A1C@elischer.org> <20010116191009.E7240@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-16 19:10:10 -0800, Alfred Perlstein wrote: >* Bruce Evans [010116 19:03] wrote: >> These don't use atomic operations (hint: no 64-bit atomic operations are >> implemented on i386's). If they need to be atomic, then they must use >> locks. > >Just wondering, can't you use 'LOCK addl' and then use 'LOCK addc'? >add longword, add longword with carry? I know it would be pretty >ugly, but it should work, no? It's not an atomic update because each longword is being updated independently: A reader can access the object between the low word and high word being updated and see an inconsistent result. If you don't need to support multiple bus masters, then the best you can achieve is: "di; addl; adcl; ei" - you don't need the lock prefixes. To support multiple masters, you need proper locks. Since SMP isn't supported on the 80386, as long as you don't to DMA to/from 64-bit objects you can get away with the "di; addl; adcl; ei" sequence. 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 16 23:30: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from mx1.techconcepts.co.za (ns1.techconcepts.co.za [196.34.2.130]) by hub.freebsd.org (Postfix) with ESMTP id C396837B400 for ; Tue, 16 Jan 2001 23:29:38 -0800 (PST) Received: from aerasmus ([10.0.1.80]) by mx1.techconcepts.co.za (8.9.3/8.9.1) with SMTP id JAA04208 for ; Wed, 17 Jan 2001 09:30:27 +0200 Message-ID: <004601c08056$984a1ab0$5001000a@jhba.techconcepts.co.za> From: "Adriaan Erasmus" To: "FreeBSD Mailing List" Subject: Thanks to everyone Date: Wed, 17 Jan 2001 09:24:56 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0043_01C08067.5AF0C810" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0043_01C08067.5AF0C810 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all I managed to compile my kernel and include the pcm device with no = hang-ups. Thanks for all the responses I got from all of you ! I just refreshed my source tree with the latest STABLE and recompiled it = without all the stuff I don't need but including my pcm device ------- = and it WORKED !!!! Now I can play MP3's while coding :) Thanks all Adriaan ----------- I would change the world,=20 but God would never give=20 me the source code. ------=_NextPart_000_0043_01C08067.5AF0C810 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi all
 
I managed to compile my kernel and = include the pcm=20 device with no hang-ups.
 
Thanks for all the responses I got from = all of you=20 !
 
I just refreshed my source tree with = the latest=20 STABLE and recompiled it without all the stuff I don't need but = including my pcm=20 device ------- and it WORKED !!!!
 
Now I can play MP3's while coding = :)
 
Thanks all
 
Adriaan
-----------
 
I would change the world,
but God = would never=20 give
me the source code.
------=_NextPart_000_0043_01C08067.5AF0C810-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 16 23:37:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by hub.freebsd.org (Postfix) with ESMTP id E129737B400 for ; Tue, 16 Jan 2001 23:37:17 -0800 (PST) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA16512; Tue, 16 Jan 2001 23:37:14 -0800 (PST) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.9) with ESMTP id JAA09246; Wed, 17 Jan 2001 09:37:10 +0200 (EET) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id JAA01954; Wed, 17 Jan 2001 09:37:06 +0200 (EET) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14949.19362.747339.859951@ultrahot.Finland.Sun.COM> Date: Wed, 17 Jan 2001 09:37:06 +0200 To: freebsd-current@FreeBSD.ORG Cc: "Cameron Grant" , Subject: Re: modified ich sound driver for current? In-Reply-To: <005401c08008$ec192b20$0504020a@haveblue> References: <14948.50037.587296.913304@ultrahot.Finland.Sun.COM> <005401c08008$ec192b20$0504020a@haveblue> X-Mailer: VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cameron Grant writes: > > i'm not happy with some of the things the driver does, so until i can modify > it i won't commit it. this necessitates having hardware to test with, which > i should be getting in the near future. > Nice to know that someone is even thinking about what to do with this driver. Chris Knight writes: > > I modified the mentioned driver when newpcm got kobjified and submitted the > patches back to the author. I didn't get a reply. I haven't synced up my > laptop to current since about the new year, so I don't know if it works with > any changes made. Rather than send the patch to the list, I'll e-mail it to > anyone that asks. > Your modification worked just fine and my laptop is back in business. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 3:16:38 2001 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 5659937B400; Wed, 17 Jan 2001 03:16:19 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0HBGJC14809; Wed, 17 Jan 2001 03:16:19 -0800 (PST) Date: Wed, 17 Jan 2001 03:16:19 -0800 From: Alfred Perlstein To: arch@freebsd.org, current@freebsd.org Subject: HEADS-UP: await/asleep removal imminent Message-ID: <20010117031618.K7240@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please trim cc's as appropriate. I have a patch here that removes await/asleep from the kernel API. http://people.freebsd.org/~alfred/noasleep.diff Matt Dillon implemented alseep/await quite some time ago and the only thing that's using it is ata. In order to clean up some of the schduler and vm system I'm removing support for it. Peter Wemm and I suspect that ata doesn't need it. Right now I'm running several make -j128 buildworlds and buildkernels with this patch to catch any ata problems. Now would be a good time to test this delta for stability reasons. I plan on applying the delta within a few days. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 3:39: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 038F637B400; Wed, 17 Jan 2001 03:38:38 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA11834; Wed, 17 Jan 2001 12:38:33 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101171138.MAA11834@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <20010117031618.K7240@fw.wintelcom.net> from Alfred Perlstein at "Jan 17, 2001 03:16:19 am" To: bright@wintelcom.net (Alfred Perlstein) Date: Wed, 17 Jan 2001 12:38:33 +0100 (CET) Cc: arch@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 Alfred Perlstein wrote: > Please trim cc's as appropriate. > > I have a patch here that removes await/asleep from the kernel API. > > http://people.freebsd.org/~alfred/noasleep.diff > > Matt Dillon implemented alseep/await quite some time ago and the > only thing that's using it is ata. In order to clean up some of > the schduler and vm system I'm removing support for it. > > Peter Wemm and I suspect that ata doesn't need it. Right now I'm > running several make -j128 buildworlds and buildkernels with this > patch to catch any ata problems. I'll commit the ata part as soon as I have it tested here.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 4:27:37 2001 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 019AB37B400; Wed, 17 Jan 2001 04:27:17 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id NAA42073; Wed, 17 Jan 2001 13:27:10 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Alfred Perlstein Cc: Archie Cobbs , Julian Elischer , Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP! New netgraph code coming References: <200101162138.NAA10547@curve.dellroad.org> <20010116150038.X7240@fw.wintelcom.net> From: Dag-Erling Smorgrav Date: 17 Jan 2001 13:27:09 +0100 In-Reply-To: Alfred Perlstein's message of "Tue, 16 Jan 2001 15:00:38 -0800" Message-ID: Lines: 10 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 Alfred Perlstein writes: > This ought to be documented. A good start would be to add example of MODULE_VERSION and MODULE_DEPEND usage to one of the templates in /usr/share/examples/kld/. DES -- Dag-Erling Smorgrav - des@ofug.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 17 5:37:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 5F3C637B400 for ; Wed, 17 Jan 2001 05:37:07 -0800 (PST) Received: by gw.nectar.com (Postfix, from userid 1001) id 31152193E3; Wed, 17 Jan 2001 07:37:06 -0600 (CST) Date: Wed, 17 Jan 2001 07:37:06 -0600 From: "Jacques A. Vidrine" To: "David W. Chapman Jr." Cc: freebsd-current@FreeBSD.ORG Subject: Re: VXA tape drive Message-ID: <20010117073706.A34522@spawn.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , "David W. Chapman Jr." , freebsd-current@FreeBSD.ORG References: <01d901c07f23$e46ceaa0$931576d8@inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01d901c07f23$e46ceaa0$931576d8@inethouston.net>; from dwcjr@inethouston.net on Mon, Jan 15, 2001 at 12:49:29PM -0600 X-Url: http://www.nectar.com/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 12:49:29PM -0600, David W. Chapman Jr. wrote: > I checked in current with little luck. Does -current support VXA-1 tape > drives by Ecrix. The site claims that freebsd does, but the only response > by someone that has one says that it won't successfully backup. I've been using an external VXA-1 drive since October 1999 (FreeBSD 3.3 or so). It is currently attached to a FreeBSD 4.1 machine. I really love it. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@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 17 6:10:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6203237B401 for ; Wed, 17 Jan 2001 06:10:21 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA47772 for current@freebsd.org; Wed, 17 Jan 2001 15:10:19 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101171410.PAA47772@freebsd.dk> Subject: WANTED: testers with VIA 82C686B southbridges!! To: current@freebsd.org Date: Wed, 17 Jan 2001 15:10:18 +0100 (CET) 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 I've committed support for the VIA 82c686B southbridge, but I lack testing with an ATA100 drive to make sure it works as it should. Could somebody try the following if they have this HW setup: for i in 1 2 3 4 do dd if=/dev/adN of=/dev/null bs=512k count=1 # N is you drive number done and mail me the resulting output together with a dmesg copy ? Thanks! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 7:29:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 449BC37B401 for ; Wed, 17 Jan 2001 07:29:29 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.11.1/8.11.1) id f0HFTJw46571 for current@freebsd.org; Wed, 17 Jan 2001 10:29:19 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200101171529.f0HFTJw46571@hda.hda.com> Subject: Re: Fan speed control sony vaio lx800 slimtop In-Reply-To: <200101141817.f0EIH3F34298@hda.hda.com> from Peter Dufault at "Jan 14, 2001 01:17:02 pm" To: current@freebsd.org Date: Wed, 17 Jan 2001 10:29:19 -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 I'm giving up on turning down the slimtop fan for now, the only way I can think of to figure out how Sony is turning down the fan is to boot windows, single step through the installation of the device drivers until I know which one is doing it, and then disassemble it to see what they're up to. If someone has any other ideas let me know. I might hook a scope up to the fan and boot windows just to see if it simply turning the fan down or is varying it. Maybe I'll add a voltage regulator and a few bits of control from the unused printer (it isn't run off the MB) and vary the fan speed brute force. I asked Sony support about the fan issue, they promptly replied that running the fan at high continuosly is fine, that no additional information is available, and that they will "record my interest in alternate operating systems". At least they have a polite way of saying they support nothing but Windows. So I'm going to roll this system back to 4.2 stable and start using it for work. If anyone wants me to try anything out with -current or ACPI then holler today. Two additional ACPI-APM things I did notice: 1. Putting APM into the config caused the keyboard switch to start working to turn the machine on. I'd taken it out at someones suggestion. This is weird, I can only guess APM does something as the machine powers off that ACPI doesn't. 2. Using APM to suspend the machine causes the LED on the power switch to turn amber, using "acpiconf -s 1" doesn't, the machine suspends but the LED stays green. If anyone has any little snippet they want me to try before going back to stable let me know. Anyway, if anyone buys one of these things then rubber bumpers on the base and Dynamat lining the plastic case makes it as quiet as a "normal" computer plus gives it a real solid feel. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 7:43:49 2001 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 36A9E37B404 for ; Wed, 17 Jan 2001 07:43:30 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA18055; Wed, 17 Jan 2001 10:43:10 -0500 (EST) (envelope-from wollman) Date: Wed, 17 Jan 2001 10:43:10 -0500 (EST) From: Garrett Wollman Message-Id: <200101171543.KAA18055@khavrinen.lcs.mit.edu> To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Atomic breakage? In-Reply-To: <20010117142654.A98607@gsmx07.alcatel.com.au> References: <3A64AA23.30035A1C@elischer.org> <20010116191009.E7240@fw.wintelcom.net> <20010117142654.A98607@gsmx07.alcatel.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > To support multiple masters, you need proper locks. On older processors, yes. On processors with the CX8 feature bit set, you can do it without any sort of locking (indeed, this is a primitive that semaphores can be built upon). Consider the following: atomic_increment: ; prologue ; get EA into %esi movl (%esi), %eax movl 4(%esi), %edx 1: movl %eax, %ebx movl %edx, %ecx incl %ebx adcl $0, %ecx cmpxchg8b (%esi) ; generates a locked bus cycle jne 1 ; epilogue On pre-Pentium processors (which lack the CX8 feature) this sort of sequence is impossible. OTOH, I don't think SMP works on any pre-Pentium processor, so again this degenerates to: pushfl cli incl (%esi) adcl $0, 4(%esi) popfl ...in the non-SMP case. -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 17 8:15:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 127FC37B400; Wed, 17 Jan 2001 08:14:56 -0800 (PST) Received: from jesup.eng.tvol.net ([10.32.2.26]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id CX5HP616; Wed, 17 Jan 2001 11:14:54 -0500 Reply-To: Randell Jesup To: Soren Schmidt Cc: bright@wintelcom.net (Alfred Perlstein), arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent References: <200101171138.MAA11834@freebsd.dk> From: Randell Jesup Date: 17 Jan 2001 11:17:29 -0500 In-Reply-To: Soren Schmidt's message of "Wed, 17 Jan 2001 12:38:33 +0100 (CET)" Message-ID: User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It seems Alfred Perlstein wrote: >> I have a patch here that removes await/asleep from the kernel API. >> >> http://people.freebsd.org/~alfred/noasleep.diff >> >> Matt Dillon implemented alseep/await quite some time ago and the >> only thing that's using it is ata. In order to clean up some of >> the schduler and vm system I'm removing support for it. >> >> Peter Wemm and I suspect that ata doesn't need it. Right now I'm >> running several make -j128 buildworlds and buildkernels with this >> patch to catch any ata problems. Ummmm... It seems to me from reading the man page for asleep/await that they have significant utility, and that the real issue would be one of code not using them, especially as people work to remove the Giant lock for SMP. Or is the discussion in the man page wrong in some way? -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.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 17 8:15:38 2001 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 1598837B69D for ; Wed, 17 Jan 2001 08:15:18 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA18224; Wed, 17 Jan 2001 11:14:49 -0500 (EST) (envelope-from wollman) Date: Wed, 17 Jan 2001 11:14:49 -0500 (EST) From: Garrett Wollman Message-Id: <200101171614.LAA18224@khavrinen.lcs.mit.edu> To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: Atomic breakage? In-Reply-To: <20010116191009.E7240@fw.wintelcom.net> References: <3A64AA23.30035A1C@elischer.org> <20010116191009.E7240@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Just wondering, can't you use 'LOCK addl' and then use 'LOCK addc'? > add longword, add longword with carry? I know it would be pretty > ugly, but it should work, no? The two bus cycles are independent, so there is a race condition. OTOH, it's a fairly *unlikely* race condition, and the worst thing that can happen is statistics that are obviously off by four billion. (The race only occurs when there is a carry out of the low-order longword, which is to say, once in every 2**32 operations.) -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 17 8:40:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 1BE5C37B6A1 for ; Wed, 17 Jan 2001 08:40:16 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0HGi8s65704; Wed, 17 Jan 2001 08:44:08 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101171543.KAA18055@khavrinen.lcs.mit.edu> Date: Wed, 17 Jan 2001 08:40:10 -0800 (PST) From: John Baldwin To: Garrett Wollman Subject: Re: Atomic breakage? Cc: current@FreeBSD.org, Peter Jeremy Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-01 Garrett Wollman wrote: > < said: > >> To support multiple masters, you need proper locks. > > On older processors, yes. On processors with the CX8 feature bit set, > you can do it without any sort of locking (indeed, this is a primitive > that semaphores can be built upon). Consider the following: > > atomic_increment: > ; prologue > ; get EA into %esi > movl (%esi), %eax > movl 4(%esi), %edx > 1: movl %eax, %ebx > movl %edx, %ecx > incl %ebx > adcl $0, %ecx > cmpxchg8b (%esi) ; generates a locked bus cycle > jne 1 > ; epilogue > > On pre-Pentium processors (which lack the CX8 feature) this sort of > sequence is impossible. OTOH, I don't think SMP works on any > pre-Pentium processor, so again this degenerates to: > > pushfl > cli > incl (%esi) > adcl $0, 4(%esi) > popfl > > ...in the non-SMP case. Early Pentiums (<= P90) don't support CX8 or so I've heard, which make this slightly more complicated, as for a pentium we would have to use a function pointer that we setup during probe. Also, during a SMP boot we would have to panic if CX8 wasn't enabled on all CPU's. > -GAWollman -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 8:44:32 2001 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 1DA9337B401; Wed, 17 Jan 2001 08:44:12 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0HGi5n22185; Wed, 17 Jan 2001 08:44:05 -0800 (PST) Date: Wed, 17 Jan 2001 08:44:05 -0800 From: Alfred Perlstein To: Dag-Erling Smorgrav Cc: Archie Cobbs , Julian Elischer , Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP! New netgraph code coming Message-ID: <20010117084404.L7240@fw.wintelcom.net> References: <200101162138.NAA10547@curve.dellroad.org> <20010116150038.X7240@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Wed, Jan 17, 2001 at 01:27:09PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dag-Erling Smorgrav [010117 04:27] wrote: > Alfred Perlstein writes: > > This ought to be documented. > > A good start would be to add example of MODULE_VERSION and > MODULE_DEPEND usage to one of the templates in > /usr/share/examples/kld/. Since I have no clue as to how they work, it'll have to wait until someone who knows how it works does it or I have the time to UTSL. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 8:51:25 2001 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 5A0E237B400; Wed, 17 Jan 2001 08:51:04 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA43088; Wed, 17 Jan 2001 17:51:00 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Alfred Perlstein Cc: Archie Cobbs , Julian Elischer , Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP! New netgraph code coming References: <200101162138.NAA10547@curve.dellroad.org> <20010116150038.X7240@fw.wintelcom.net> <20010117084404.L7240@fw.wintelcom.net> From: Dag-Erling Smorgrav Date: 17 Jan 2001 17:50:59 +0100 In-Reply-To: Alfred Perlstein's message of "Wed, 17 Jan 2001 08:44:05 -0800" Message-ID: Lines: 18 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 Alfred Perlstein writes: > Since I have no clue as to how they work, it'll have to wait until > someone who knows how it works does it or I have the time to UTSL. MODULE_VERSION(module, version); module is the name of your module. version is the integer version number of your module. MODULE_DEPEND(module, mdepend, vmin, vpref, vmax); mdpepend is the name of the module your module depends on. vmin, vpref, vmac are the minimum, maximum and preferred versions of the module your module depends on. DES -- Dag-Erling Smorgrav - des@ofug.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 17 9:23: 7 2001 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 EBF0237B402; Wed, 17 Jan 2001 09:22:29 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0HHL9A23321; Wed, 17 Jan 2001 09:21:09 -0800 (PST) Date: Wed, 17 Jan 2001 09:21:09 -0800 From: Alfred Perlstein To: Randell Jesup Cc: Soren Schmidt , arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent Message-ID: <20010117092109.O7240@fw.wintelcom.net> References: <200101171138.MAA11834@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rjesup@wgate.com on Wed, Jan 17, 2001 at 11:17:29AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Randell Jesup [010117 08:14] wrote: > >It seems Alfred Perlstein wrote: > >> I have a patch here that removes await/asleep from the kernel API. > >> > >> http://people.freebsd.org/~alfred/noasleep.diff > >> > >> Matt Dillon implemented alseep/await quite some time ago and the > >> only thing that's using it is ata. In order to clean up some of > >> the schduler and vm system I'm removing support for it. > >> > >> Peter Wemm and I suspect that ata doesn't need it. Right now I'm > >> running several make -j128 buildworlds and buildkernels with this > >> patch to catch any ata problems. > > Ummmm... > > It seems to me from reading the man page for asleep/await that > they have significant utility, and that the real issue would be one of > code not using them, especially as people work to remove the Giant > lock for SMP. > > Or is the discussion in the man page wrong in some way? The manpage is correct, but we've yet to see it used properly in the code with the exception of ata, and even with ata we're not sure if it's needed. Basically the idea is that at a certain depth into the kernel you start using the M_AWAIT parameter when requesting certain resources. Since that removes the possiblity of blocking you can feel safe holding a mutex over these lower parts of the code, then only releasing your mutex later. If a resource shortage is detected then you can call await and retry later. 1) from sleep(9): to actually wait for the previously queued wait condition. If asleep() is called several times, only the most recent call is effective. asleep() may be called with an ident value of NULL to remove any previ- ously queued condition. Basically, there's a chance you may clobber previous calls to asleep, this is somewhat unlikely since most shortages or blocking when some 'NOBLOCK' flag is passed in should immediately return. Somewhat of a concern, but it really is unlikely to be a problem. 2) most things you'd use mawait for would be under a lock already, since it's under a lock, you must context switch anyway, there's no "optimized out" sleep, because first the interrupt will block on your mutex, then you'll get to run, when you drop your mutex the interrupt will then run. If you do this with msleep or masleep the effect is the same. 3) no one uses it! :) 4) most anything you need asleep for could probably be done with mutex/cv's. I'm not going to axe it for a few days, this is a really amazing API that Matt added, the problem is utility and useage over code complexity. It's just a proposal. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 9:40:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from twister.domainfactory.de (twister.domainfactory.de [212.84.255.3]) by hub.freebsd.org (Postfix) with SMTP id 7EF0B37B400 for ; Wed, 17 Jan 2001 09:39:58 -0800 (PST) Received: (qmail 24388 invoked from network); 17 Jan 2001 17:39:35 -0000 Received: from blndi4-145-253-141-213.arcor-ip.net (HELO gizmo.quizbot.org) ([145.253.141.213]) (envelope-sender ) by twister.domainfactory.de (qmail-ldap-1.03) with SMTP for ; 17 Jan 2001 17:39:35 -0000 Message-ID: <3A65D810.6304785A@gizmo.quizbot.org> Date: Wed, 17 Jan 2001 18:36:16 +0100 From: Robert Drehmel X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: John Baldwin Cc: Garrett Wollman , current@FreeBSD.org, Peter Jeremy Subject: Re: Atomic breakage? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , John Baldwin wrote: > Early Pentiums (<= P90) don't support CX8 or so I've heard, which make this > slightly more complicated, as for a pentium we would have to use a function > pointer that we setup during probe. Also, during a SMP boot we would have to > panic if CX8 wasn't enabled on all CPU's. P75 (stepping 5): cmpxchg8 was actually introduced with the Pentium processors, as Mr. Wollman already wrote. -- Robert S. F. Drehmel Real hackers run -current from punchcards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 9:44:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 5FAE037B400; Wed, 17 Jan 2001 09:44:11 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0HHi4Z53514; Wed, 17 Jan 2001 18:44:04 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Drehmel Cc: John Baldwin , Garrett Wollman , current@FreeBSD.ORG, Peter Jeremy Subject: Re: Atomic breakage? In-Reply-To: Your message of "Wed, 17 Jan 2001 18:36:16 +0100." <3A65D810.6304785A@gizmo.quizbot.org> Date: Wed, 17 Jan 2001 18:44:04 +0100 Message-ID: <53512.979753444@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A65D810.6304785A@gizmo.quizbot.org>, Robert Drehmel writes: >In , John Baldwin wrote: >> Early Pentiums (<= P90) don't support CX8 or so I've heard, which make this >> slightly more complicated, as for a pentium we would have to use a function >> pointer that we setup during probe. Also, during a SMP boot we would have to >> panic if CX8 wasn't enabled on all CPU's. > >P75 (stepping 5): > >cmpxchg8 was actually introduced with the Pentium processors, >as Mr. Wollman already wrote. Either way, it's precense should be determined by looking at the CPUID feature bit. It's the only reliable way. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 10: 2:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DDBC637B699; Wed, 17 Jan 2001 10:02:12 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA02435; Wed, 17 Jan 2001 19:02:06 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101171802.TAA02435@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <20010117092109.O7240@fw.wintelcom.net> from Alfred Perlstein at "Jan 17, 2001 09:21:09 am" To: bright@wintelcom.net (Alfred Perlstein) Date: Wed, 17 Jan 2001 19:02:06 +0100 (CET) Cc: rjesup@wgate.com (Randell Jesup), arch@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 Alfred Perlstein wrote: > > >> Peter Wemm and I suspect that ata doesn't need it. Right now I'm > > >> running several make -j128 buildworlds and buildkernels with this > > >> patch to catch any ata problems. > > > > Ummmm... > > > > It seems to me from reading the man page for asleep/await that > > they have significant utility, and that the real issue would be one of > > code not using them, especially as people work to remove the Giant > > lock for SMP. > > > > Or is the discussion in the man page wrong in some way? > > The manpage is correct, but we've yet to see it used properly in > the code with the exception of ata, and even with ata we're not > sure if it's needed. Uhm, well I tried removing it here, and now -current (on SMP HW) fails in new "interesting" ways. The problem here is that -current is not stable on SMP HW so the question is if this change in behavior is to the better or to the worse... I suggest creative manpower is used to stabilize -current, instead of fine trimming which API's should stay or not... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 10: 5:47 2001 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 7658C37B404; Wed, 17 Jan 2001 10:05:18 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0HI5HD24831; Wed, 17 Jan 2001 10:05:17 -0800 (PST) Date: Wed, 17 Jan 2001 10:05:17 -0800 From: Alfred Perlstein To: Randell Jesup , dillon@freebsd.org Cc: Soren Schmidt , arch@freebsd.org, current@freebsd.org Subject: Re: HEADS-UP: await/asleep removal imminent Message-ID: <20010117100516.Q7240@fw.wintelcom.net> References: <200101171138.MAA11834@freebsd.dk> <20010117092109.O7240@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010117092109.O7240@fw.wintelcom.net>; from bright@wintelcom.net on Wed, Jan 17, 2001 at 09:21:09AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Alfred Perlstein [010117 09:24] wrote: > > I'm not going to axe it for a few days, this is a really amazing > API that Matt added, the problem is utility and useage over code > complexity. > > It's just a proposal. I found several places where it may be useful, but I'm not sure if the benefits outweigh the gains. In a copy of the tree I've locked down the socket layer (not the entire stack, just sockets :) ) there's code like this: SOCKBUF_UNLOCK(&so->so_snd, 0); if (top == 0) { MGETHDR(m, M_TRYWAIT, MT_DATA); if (m == NULL) { error = ENOBUFS; SOCKBUF_LOCK(&so->so_snd, 0); goto release; } mlen = MHLEN; ... SOCKBUF_LOCK(&so->so_snd, 0); /* XXX */ The lock must be unwound becasue we're calling MGETHDR with M_TRYWAIT. If wae used M_TRY'A'WAIT the code would probably look something like this: /* SOCKBUF_UNLOCK(&so->so_snd, 0); */ again: if (top == 0) { MGETHDR(m, M_TRYWAIT, MT_DATA); if (m == NULL) { error = mawait(&so->so_snd.sb_mtx, -1, -1); if (error) { if (error == EWOULDBLOCK) error = ENOBUFS; goto release; } goto again; /* SOCKBUF_LOCK(&so->so_snd, 0); */ } mlen = MHLEN; ... /* SOCKBUF_LOCK(&so->so_snd, 0); */ /* XXX */ Which means we don't have to drop the lock over the socket unless we'd block on allocation. Matt, is this what you intended for it to do? So far I've only seen it used to avoid races, but not to optimize out mutex aquire/release. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 10:15:24 2001 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 9C93C37B6C5; Wed, 17 Jan 2001 10:15:01 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0HIDgn25079; Wed, 17 Jan 2001 10:13:42 -0800 (PST) Date: Wed, 17 Jan 2001 10:13:42 -0800 From: Alfred Perlstein To: Soren Schmidt Cc: Randell Jesup , arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent Message-ID: <20010117101342.R7240@fw.wintelcom.net> References: <20010117092109.O7240@fw.wintelcom.net> <200101171802.TAA02435@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101171802.TAA02435@freebsd.dk>; from sos@freebsd.dk on Wed, Jan 17, 2001 at 07:02:06PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Soren Schmidt [010117 10:02] wrote: > It seems Alfred Perlstein wrote: > > > >> Peter Wemm and I suspect that ata doesn't need it. Right now I'm > > > >> running several make -j128 buildworlds and buildkernels with this > > > >> patch to catch any ata problems. > > > > > > Ummmm... > > > > > > It seems to me from reading the man page for asleep/await that > > > they have significant utility, and that the real issue would be one of > > > code not using them, especially as people work to remove the Giant > > > lock for SMP. > > > > > > Or is the discussion in the man page wrong in some way? > > > > The manpage is correct, but we've yet to see it used properly in > > the code with the exception of ata, and even with ata we're not > > sure if it's needed. > > Uhm, well I tried removing it here, and now -current (on SMP HW) > fails in new "interesting" ways. The problem here is that > -current is not stable on SMP HW so the question is if this > change in behavior is to the better or to the worse... > > I suggest creative manpower is used to stabilize -current, instead > of fine trimming which API's should stay or not... I started a loop of make -j128 buildworld and buildkernel last night, I still haven't seen anything odd happen on my hardware. You and Poul-Henning have to figure out what's going on, no one else is able to reproduce this instability you're talking about. There has to be a way for you guys to get us some reasonable tracebacks or diagnostics instead of just saying "it's broke". Perhaps you can explain how you're able to trigger this instability with a test script? Poul-Henning told me he just needed to do a make -j256 world, I did 10 of them without a problem... I'd also like to see what hardware you guys are running on and what kernel config. I'm pretty sure that running with a weird value for HZ causes lockups on -stable, dunno about current. Basically if you're expecting me or the SMP team to figure out what's going on without more info, you're pretty much out of luck. ...wondering if the box Paul Saab gave me is actually SMP... :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 10:26: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 0B16C37B6B7; Wed, 17 Jan 2001 10:25:39 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0HIPSZ53777; Wed, 17 Jan 2001 19:25:28 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Alfred Perlstein Cc: Soren Schmidt , Randell Jesup , arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: Your message of "Wed, 17 Jan 2001 10:13:42 PST." <20010117101342.R7240@fw.wintelcom.net> Date: Wed, 17 Jan 2001 19:25:28 +0100 Message-ID: <53775.979755928@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Perhaps you can explain how you're able to trigger this instability >with a test script? Poul-Henning told me he just needed to do a >make -j256 world, I did 10 of them without a problem... Then you misunderstood me, I don't have anything in the dept of SMP hw which can trigger it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 10:30:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3BEBD37B6C2 for ; Wed, 17 Jan 2001 10:29:47 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0HIQAL37735; Wed, 17 Jan 2001 10:26:10 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <53512.979753444@critter> Date: Wed, 17 Jan 2001 10:28:03 -0800 (PST) From: John Baldwin To: Poul-Henning Kamp Subject: Re: Atomic breakage? Cc: Peter Jeremy , current@FreeBSD.org, Garrett Wollman , Robert Drehmel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-01 Poul-Henning Kamp wrote: > In message <3A65D810.6304785A@gizmo.quizbot.org>, Robert Drehmel writes: >>In , John Baldwin wrote: >>> Early Pentiums (<= P90) don't support CX8 or so I've heard, which make this >>> slightly more complicated, as for a pentium we would have to use a function >>> pointer that we setup during probe. Also, during a SMP boot we would have >>> to >>> panic if CX8 wasn't enabled on all CPU's. >> >>P75 (stepping 5): >> >>cmpxchg8 was actually introduced with the Pentium processors, >>as Mr. Wollman already wrote. > > Either way, it's precense should be determined by looking at the CPUID > feature bit. It's the only reliable way. It's expensive though. Ok, after some digging I found out what this particular person was referring to: on Pentiums with stepping < 0xc, a cmpxchg8b that crosses a page boundary triggers an illegel opcode fault rather than a page fault if the second page is missing. Woo. :) So as long as we keep all atomically-accessed 64-bit integers within a single page we should be fine for CX8 on all pentiums should we even want 64-bit atomic ops. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 10:40: 7 2001 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 1C53437B698; Wed, 17 Jan 2001 10:39:45 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA19379; Wed, 17 Jan 2001 13:39:40 -0500 (EST) (envelope-from wollman) Date: Wed, 17 Jan 2001 13:39:40 -0500 (EST) From: Garrett Wollman Message-Id: <200101171839.NAA19379@khavrinen.lcs.mit.edu> To: John Baldwin Cc: current@FreeBSD.org Subject: Re: Atomic breakage? In-Reply-To: References: <53512.979753444@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > person was referring to: on Pentiums with stepping < 0xc, a cmpxchg8b that > crosses a page boundary triggers an illegel opcode fault rather than a page > fault if the second page is missing. This is (part of) the famous `F00F bug'. -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 17 10:43: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 77C3937B6CD; Wed, 17 Jan 2001 10:42:33 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA12276; Wed, 17 Jan 2001 19:42:27 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101171842.TAA12276@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <20010117101342.R7240@fw.wintelcom.net> from Alfred Perlstein at "Jan 17, 2001 10:13:42 am" To: bright@wintelcom.net (Alfred Perlstein) Date: Wed, 17 Jan 2001 19:42:26 +0100 (CET) Cc: rjesup@wgate.com (Randell Jesup), arch@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 Alfred Perlstein wrote: > > > > I suggest creative manpower is used to stabilize -current, instead > > of fine trimming which API's should stay or not... > > I started a loop of make -j128 buildworld and buildkernel last > night, I still haven't seen anything odd happen on my hardware. > > You and Poul-Henning have to figure out what's going on, no one > else is able to reproduce this instability you're talking about. Oohh you dont read the mailing lists then, there has been plenty of reports of hanging -current boxen since SMPng... > There has to be a way for you guys to get us some reasonable > tracebacks or diagnostics instead of just saying "it's broke". Its close to impossible, the two symptoms I see here are either spontanous reboots, or solid hangs where only a reset can get you out, so I cant say much other than "it's broke". > Perhaps you can explain how you're able to trigger this instability > with a test script? Poul-Henning told me he just needed to do a > make -j256 world, I did 10 of them without a problem... Hmm, with a -current kernel from today 1200 CET i just need to do a make depend on a GENERIC kernel, and wham it locks up. > I'd also like to see what hardware you guys are running on and what > kernel config. I'm pretty sure that running with a weird value > for HZ causes lockups on -stable, dunno about current. Nothing special, GENERIC kernel with SMP defined will do nicely, running without SMP improves matters but on the fastet machine I'm still getting lockups, but they are rare... Hardware it hangs on here include: 2*PPro@200 192MB FX chipset ATA disks on onboard controller (PIIX3) 2*PII@350 512MB BX chipset SCSI disks on NCR controller 2*PIII@1G 512MB ServerWorks chipset ATA disks on onboard + HPT controller. It seems the faster the machine the faster the lockup/hang.. Need I mention that they all work just fine(tm) under -stable and -current back on PRE_SMPNG... So, we (phk & I) are trying to figure out what is going on, but there is little to go on but hunch... So there is nothing special to it guys, you just have to try.. Oh btw using a ccd/vinum/ATA-raid thingy makes the problem worse, probably due to the higher interrupt rates. > Basically if you're expecting me or the SMP team to figure out > what's going on without more info, you're pretty much out of luck. See above, not really possible, we have been trying to find some (affordable) HW that could be used to preserve a log over a boot, but so far I havn't been able to find anything that works, and is fast enough to not effect the system too much... > ...wondering if the box Paul Saab gave me is actually SMP... :) Yup, that would explain things :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 10:47: 4 2001 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 C550A37B6C9; Wed, 17 Jan 2001 10:46:37 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0HIhIT26159; Wed, 17 Jan 2001 10:43:18 -0800 (PST) Date: Wed, 17 Jan 2001 10:43:18 -0800 From: Alfred Perlstein To: Poul-Henning Kamp Cc: Soren Schmidt , Randell Jesup , arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent Message-ID: <20010117104318.U7240@fw.wintelcom.net> References: <20010117101342.R7240@fw.wintelcom.net> <53775.979755928@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <53775.979755928@critter>; from phk@critter.freebsd.dk on Wed, Jan 17, 2001 at 07:25:28PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Poul-Henning Kamp [010117 10:25] wrote: > > >Perhaps you can explain how you're able to trigger this instability > >with a test script? Poul-Henning told me he just needed to do a > >make -j256 world, I did 10 of them without a problem... > > Then you misunderstood me, I don't have anything in the dept > of SMP hw which can trigger it. If you could be more vague it would assist me greatly in figuring out what's broken. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 10:53:42 2001 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 6915537B6B1; Wed, 17 Jan 2001 10:53:14 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0HIqQX26581; Wed, 17 Jan 2001 10:52:26 -0800 (PST) Date: Wed, 17 Jan 2001 10:52:26 -0800 From: Alfred Perlstein To: Soren Schmidt Cc: Randell Jesup , arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent Message-ID: <20010117105226.V7240@fw.wintelcom.net> References: <20010117101342.R7240@fw.wintelcom.net> <200101171842.TAA12276@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101171842.TAA12276@freebsd.dk>; from sos@freebsd.dk on Wed, Jan 17, 2001 at 07:42:26PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Soren Schmidt [010117 10:43] wrote: > It seems Alfred Perlstein wrote: > > > > > > I suggest creative manpower is used to stabilize -current, instead > > > of fine trimming which API's should stay or not... > > > > I started a loop of make -j128 buildworld and buildkernel last > > night, I still haven't seen anything odd happen on my hardware. > > > > You and Poul-Henning have to figure out what's going on, no one > > else is able to reproduce this instability you're talking about. > > Oohh you dont read the mailing lists then, there has been plenty > of reports of hanging -current boxen since SMPng... Yes, but none with anything useful. :( > > There has to be a way for you guys to get us some reasonable > > tracebacks or diagnostics instead of just saying "it's broke". > > Its close to impossible, the two symptoms I see here are either > spontanous reboots, or solid hangs where only a reset can get > you out, so I cant say much other than "it's broke". You probably have a much better understanding of low level programming than I do, you _should_ be able to figure out what's going on. > > Perhaps you can explain how you're able to trigger this instability > > with a test script? Poul-Henning told me he just needed to do a > > make -j256 world, I did 10 of them without a problem... > > Hmm, with a -current kernel from today 1200 CET i just need to > do a make depend on a GENERIC kernel, and wham it locks up. Odd, doesn't hang for me. > > I'd also like to see what hardware you guys are running on and what > > kernel config. I'm pretty sure that running with a weird value > > for HZ causes lockups on -stable, dunno about current. > > Nothing special, GENERIC kernel with SMP defined will do nicely, running > without SMP improves matters but on the fastet machine I'm still getting > lockups, but they are rare... > > Hardware it hangs on here include: > > 2*PPro@200 192MB FX chipset ATA disks on onboard controller (PIIX3) > > 2*PII@350 512MB BX chipset SCSI disks on NCR controller > > 2*PIII@1G 512MB ServerWorks chipset ATA disks on onboard + HPT controller. > > It seems the faster the machine the faster the lockup/hang.. > > Need I mention that they all work just fine(tm) under -stable and > -current back on PRE_SMPNG... > > So, we (phk & I) are trying to figure out what is going on, but > there is little to go on but hunch... > So there is nothing special to it guys, you just have to try.. > Oh btw using a ccd/vinum/ATA-raid thingy makes the problem worse, > probably due to the higher interrupt rates. I will try stacking a vinum over vn striped setup later tonight to see if this still locks up. You're still not telling me what combination of vn/vinum does this, so I guess I'll have to stumble around in the dark for a bit until I find the magic combination to find the Danish panic/lockup? I think phk just told me that you need a UP kernel to find this, but he's being pretty vague about it so I don't know. > > Basically if you're expecting me or the SMP team to figure out > > what's going on without more info, you're pretty much out of luck. > > See above, not really possible, we have been trying to find some > (affordable) HW that could be used to preserve a log over a boot, > but so far I havn't been able to find anything that works, and > is fast enough to not effect the system too much... > > > ...wondering if the box Paul Saab gave me is actually SMP... :) > > Yup, that would explain things :) Well, I do see processes migrating from CPU to CPU and there's the dmesg: 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: 4, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff start_init: trying /sbin/init Dual 750mhz, 1GB RAM, atapci0: dual disks: ad0: ATA-5 disk at ata0-master -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 10:56:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id B3DDE37B401; Wed, 17 Jan 2001 10:56:27 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0HIrFL38300; Wed, 17 Jan 2001 10:53:15 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101171842.TAA12276@freebsd.dk> Date: Wed, 17 Jan 2001 10:55:08 -0800 (PST) From: John Baldwin To: Soren Schmidt Subject: Re: HEADS-UP: await/asleep removal imminent Cc: current@FreeBSD.org, arch@FreeBSD.org, (Randell Jesup) , (Alfred Perlstein) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-01 Soren Schmidt wrote: > Nothing special, GENERIC kernel with SMP defined will do nicely, running > without SMP improves matters but on the fastet machine I'm still getting > lockups, but they are rare... AHA! Useful info!! GENERIC is quite close to bloated, so the fact that it is GENERIC + SMP maybe an edge case. I'll try and test this out now that you have actually provided some useful info. :-P If you want a stable box, try trimming the kernel config down to what you need. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 10:57:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id E060737B400; Wed, 17 Jan 2001 10:57:12 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0HIrGL38308; Wed, 17 Jan 2001 10:53:16 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <53775.979755928@critter> Date: Wed, 17 Jan 2001 10:55:09 -0800 (PST) From: John Baldwin To: Poul-Henning Kamp Subject: Re: HEADS-UP: await/asleep removal imminent Cc: current@FreeBSD.org, arch@FreeBSD.org, Randell Jesup , Soren Schmidt , Alfred Perlstein Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-01 Poul-Henning Kamp wrote: > >>Perhaps you can explain how you're able to trigger this instability >>with a test script? Poul-Henning told me he just needed to do a >>make -j256 world, I did 10 of them without a problem... > > Then you misunderstood me, I don't have anything in the dept > of SMP hw which can trigger it. Ok, what _does_ trigger this then? And what kernel config are you using: GENERIC? GENERIC is rather plagued with problems right now due to its bloated size. There have been reports of people not being able to boot a freshly installed system because of the kernel bloat, so you really probably want to be using a custom kernel until that bug is found and uncovered. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 11: 6:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 592E937B6CA; Wed, 17 Jan 2001 11:05:48 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA18132; Wed, 17 Jan 2001 20:05:39 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101171905.UAA18132@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <20010117105226.V7240@fw.wintelcom.net> from Alfred Perlstein at "Jan 17, 2001 10:52:26 am" To: bright@wintelcom.net (Alfred Perlstein) Date: Wed, 17 Jan 2001 20:05:38 +0100 (CET) Cc: rjesup@wgate.com (Randell Jesup), arch@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 Alfred Perlstein wrote: > > > > > > You and Poul-Henning have to figure out what's going on, no one > > > else is able to reproduce this instability you're talking about. > > > > Oohh you dont read the mailing lists then, there has been plenty > > of reports of hanging -current boxen since SMPng... > > Yes, but none with anything useful. :( Check, but thats because the breakage is the way it is, there *IS* no useful info to pass on, other than it locks up, is that so hard to understand ?? > > > There has to be a way for you guys to get us some reasonable > > > tracebacks or diagnostics instead of just saying "it's broke". > > > > Its close to impossible, the two symptoms I see here are either > > spontanous reboots, or solid hangs where only a reset can get > > you out, so I cant say much other than "it's broke". > > You probably have a much better understanding of low level programming > than I do, you _should_ be able to figure out what's going on. Ohh, thanks for the roses, but I havn't been following the SMP work that closely I thought it was in good hands, thats why I have told you guys that its broken for the last couble of months :) > > So there is nothing special to it guys, you just have to try.. > > Oh btw using a ccd/vinum/ATA-raid thingy makes the problem worse, > > probably due to the higher interrupt rates. > > I will try stacking a vinum over vn striped setup later tonight > to see if this still locks up. > > You're still not telling me what combination of vn/vinum does this, > so I guess I'll have to stumble around in the dark for a bit until > I find the magic combination to find the Danish panic/lockup? I didn't mention vn above, I use the ata-raid thingy with src & obj put on two striped disks each. The main point here being that this changes the way IO's are done... > I think phk just told me that you need a UP kernel to find this, > but he's being pretty vague about it so I don't know. You need sleep :) I said that SMP lockups quickly, UP runs pretty well and only hangs on rare occasions... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 11: 8: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 926F837B6CF; Wed, 17 Jan 2001 11:07:32 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0HJ7Qe48680; Wed, 17 Jan 2001 11:07:26 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Jan 2001 11:07:26 -0800 (PST) From: Matt Dillon Message-Id: <200101171907.f0HJ7Qe48680@earth.backplane.com> To: Alfred Perlstein Cc: Randell Jesup , Soren Schmidt , arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent References: <200101171138.MAA11834@freebsd.dk> <20010117092109.O7240@fw.wintelcom.net> <20010117100516.Q7240@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :* Alfred Perlstein [010117 09:24] wrote: :> :> I'm not going to axe it for a few days, this is a really amazing :> API that Matt added, the problem is utility and useage over code :> complexity. :> :> It's just a proposal. : :I found several places where it may be useful, but I'm not sure if the :benefits outweigh the gains. :... : :The lock must be unwound becasue we're calling MGETHDR with M_TRYWAIT. :If wae used M_TRY'A'WAIT the code would probably look something like :this: The basic premis of using asleep()/await() is to allow you to propogate a 'blocking condition' back up to a higher level rather then blocking deep in side the kernel. The original reasoning was to deal with memory allocation blockages. For example, lets say you have three subsystem layers calling each other. The top layer wishes to implement a non-blocking API but the bottom layer might do an allocation that could block. The bottom layer could do a non-blocking allocation and return NULL, but how does the top layer (or an even higher layer) know when to try again? The original idea with asleep()/await() was for the bottom layer to call asleep() on the resource that would block and then return NULL. NULL would tell the higher layer(s) that someone down below couldn't get some resource and that an asleep() has been setup. The higher layers can then decide what to do with the situation.. they can abort the operation entirely, they can do the blocking (await() call) themselves, or they can propogate the condition to their own callers. This way you can hold more then one lock (now mutex) through a number of program layers without having to worry about them blocking on you. -- For the c urrent SMP system, asleep()/await() could be used to deal with complex situations where you (A) do not want to release a mutex through a call to another subsystem (like the memory allocator), or (B) do not know if the code calling you is already holding some mutex X and you want to hold mutex Y while you make a call to another subsystem. So, in that regard, you example: : /* SOCKBUF_UNLOCK(&so->so_snd, 0); */ :again: : if (top == 0) { : MGETHDR(m, M_TRYWAIT, MT_DATA); : if (m == NULL) { : error = mawait(&so->so_snd.sb_mtx, -1, -1); : if (error) { : if (error == EWOULDBLOCK) : error = ENOBUFS; : goto release; : } : goto again; : /* SOCKBUF_LOCK(&so->so_snd, 0); */ : } : mlen = MHLEN; :... : /* SOCKBUF_LOCK(&so->so_snd, 0); */ /* XXX */ : :Which means we don't have to drop the lock over the socket unless :we'd block on allocation. Works exactly as I originally intended. :Matt, is this what you intended for it to do? So far I've only :seen it used to avoid races, but not to optimize out mutex :aquire/release. : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] I've never liked the BSDI mutex rules, because subsystems have to have major knowledge as to how other systems operate (in reagrds to whether they can block or not), and the callee must have intimate knowledge of the callers to know that it can hold a mutex and that be the only mutex it is holding. This makes for extremely fragile and complex coding. So, this said... I'm still on the fence as to whether await()/asleep() can be used effectively. As you said, there are not too many cases at the moment and await()/asleep() does introduce significant code complexity to the scheduler, and for it to really shine it needs to be optimized to not require any sort of mutex at all in the calls to asleep(). In order to get rid of the overhead, asleep() needs to simply initialize the curproc fields and not try to actually queue the process to the sleep queue. Right now asleep() queues the process to the sleep queue (see kern/kern_synch.c) in order to support the ability for the system to asynchronously 'wake the process up again' before it actually goes to sleep (which causes the later await() to become a NOP). i.e. the situation that caused the potential blockage might be resolved before the process has a chance to sleep. Traditionally we have used SPL levels (and now mutexes) to prevent the possibility of a condition being satisfied between the test and the tsleep(). ---- Proposal Revamp asleep/await to be based on state variables rather then tsleep's traditionaln 'fake' addresses. Rather then have a traditional sleep/wakeup we instead have a state variable that asleep/await operate on. For example lets say we have a memory allocator. When the memory allocator finds it would block, it utilizes a global state structure representing the blockage and clears the state (blah.state = 0;). Then it calls asleep(&blah). asleep simply stores the pointer to &blah in the process structure, it does not try to queue it or do anything else. Thus no locking or mutexes or interrupt disablement is required *at all*. The routine is entirely passive and safe to call from anywhere. Later, some event makes more memory available for allocation. That even is asynchronous and simply sets the state variable to 1 and wakes up anybody on the sleep queue for that condition variable. This event will NOT catch the guy in the previous paragraph who has not yet called await(), however, since the call to asleep() does not actually enqueue the process (which would require a mutex). Later, the process that called asleep() finally decides to try to go to sleep for real. await() checks p_state->state and if it is zero await() places the process on the sleep queue for real and actually goes to sleep. If p_state->state is non-zero, await() simply clears the pointer (proc->p_state = NULL;) and returns (without sleeping). I believe that this conforms to the state of the SMP system much much better then my original asleep()/await() implementation, and has the advantage of extremely *LOW* overhead (virtually none in many cases). You could then use it to give the 'power of blocking' to the caller rather then the callee. This in turn gives you much greater flexibility in regards to who can hold mutexes when and who can hold mutexes through procedure calls to other subsystems. -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 17 11:10:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id ACB6E37B6A8; Wed, 17 Jan 2001 11:10:00 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA19215; Wed, 17 Jan 2001 20:09:59 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101171909.UAA19215@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: from John Baldwin at "Jan 17, 2001 10:55:08 am" To: jhb@FreeBSD.org (John Baldwin) Date: Wed, 17 Jan 2001 20:09:59 +0100 (CET) Cc: current@FreeBSD.org, arch@FreeBSD.org, rjesup@wgate.com, bright@wintelcom.net 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 John Baldwin wrote: > > On 17-Jan-01 Soren Schmidt wrote: > > Nothing special, GENERIC kernel with SMP defined will do nicely, running > > without SMP improves matters but on the fastet machine I'm still getting > > lockups, but they are rare... > > AHA! Useful info!! GENERIC is quite close to bloated, so the fact that it is > GENERIC + SMP maybe an edge case. I'll try and test this out now that you have > actually provided some useful info. :-P If you want a stable box, try > trimming the kernel config down to what you need. You read too much into that, I dont normally run a GENERIC kernel, I run one stripped down to what I need, I gave you guys a generic example of what fails, and what can easily be reproduced. Anyhow, I have asked before to have you guys supply me with a kernel that has been compiled "the right way" and I'll test it out here just to make sure I dont do anything stupid.. Just a bare bones kernel, fxp & ata drivers will do nicely for the serverworks thingy, give me an URL I can get it from or put it on ftp.freebsd.dk/incoming and give my a ping when its there... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 11:12:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 467C437B69E for ; Wed, 17 Jan 2001 11:12:34 -0800 (PST) Received: (qmail 21780 invoked by uid 1142); 17 Jan 2001 19:12:33 -0000 Date: 17 Jan 2001 11:12:33 -0800 Date: Wed, 17 Jan 2001 11:12:21 -0800 From: Jason Evans To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Debugging SMP instability (was Re: HEADS-UP: await/asleep removal imminent) Message-ID: <20010117111221.T61852@canonware.com> References: <20010117101342.R7240@fw.wintelcom.net> <200101171842.TAA12276@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101171842.TAA12276@freebsd.dk>; from sos@freebsd.dk on Wed, Jan 17, 2001 at 07:42:26PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 17, 2001 at 07:42:26PM +0100, Soren Schmidt wrote: > > Basically if you're expecting me or the SMP team to figure out > > what's going on without more info, you're pretty much out of luck. > > See above, not really possible, we have been trying to find some > (affordable) HW that could be used to preserve a log over a boot, > but so far I havn't been able to find anything that works, and > is fast enough to not effect the system too much... I did some research on this and am convinced that at least some video cards would work as memory buffers for KTR logs. Specifically, someone mentioned to me yesterday that their Matrox Millennium II flashes the X desktop during startup from a previous invocation across warm boots. (I pursued some alternatives and found the PCI RAM cards to be prohibitively expensive (more than $700), and sound cards to not have enough RAM except on old SoundBlaster AWE cards.) For someone with device driver experience, I expect it would be a few hours of effort to make it possible to use a second video card (or even the primary one for that matter) as a DMA region in which KTR logs can be saved, so that there is a way to debug even these spontaneous reboots you're having. Maybe I'll eventually get to implementing this myself, but to be honest, I don't have a driving need for it right now, whereas you do. =) You're experiencing a stability problem that none of us (SMPng people) can reproduce. We'd love to fix the problem, but without more information, your reports are only slightly more useful than the typical newbie "it's broken" reports, though certainly more frustrating. 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 17 11:21:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 51BD637B754; Wed, 17 Jan 2001 11:21:22 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0HJJML38924; Wed, 17 Jan 2001 11:19:22 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101171907.f0HJ7Qe48680@earth.backplane.com> Date: Wed, 17 Jan 2001 11:21:15 -0800 (PST) From: John Baldwin To: Matt Dillon Subject: Re: HEADS-UP: await/asleep removal imminent Cc: current@FreeBSD.org, arch@FreeBSD.org, Soren Schmidt , Randell Jesup , Alfred Perlstein Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-01 Matt Dillon wrote: >:* Alfred Perlstein [010117 09:24] wrote: >:> >:> I'm not going to axe it for a few days, this is a really amazing >:> API that Matt added, the problem is utility and useage over code >:> complexity. >:> >:> It's just a proposal. >: >:I found several places where it may be useful, but I'm not sure if the >:benefits outweigh the gains. >:... >: >:The lock must be unwound becasue we're calling MGETHDR with M_TRYWAIT. >:If wae used M_TRY'A'WAIT the code would probably look something like >:this: > > The basic premis of using asleep()/await() is to allow you to > propogate a 'blocking condition' back up to a higher level rather > then blocking deep in side the kernel. Gotcha. Given that, if we switch to using condition variables for this, why not have the low level code return a pointer to a cv to wait on? This would do the same thing using an existing API (now) and I think would serve the same purposes as your API. Returning NULL for a cv would mean that no sleep was required. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 11:22:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 07D6A37B698; Wed, 17 Jan 2001 11:22:12 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0HJJML38928; Wed, 17 Jan 2001 11:19:22 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101171909.UAA19215@freebsd.dk> Date: Wed, 17 Jan 2001 11:21:16 -0800 (PST) From: John Baldwin To: Soren Schmidt Subject: Re: HEADS-UP: await/asleep removal imminent Cc: bright@wintelcom.net, rjesup@wgate.com, arch@FreeBSD.org, current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-01 Soren Schmidt wrote: > It seems John Baldwin wrote: >> >> On 17-Jan-01 Soren Schmidt wrote: >> > Nothing special, GENERIC kernel with SMP defined will do nicely, running >> > without SMP improves matters but on the fastet machine I'm still getting >> > lockups, but they are rare... >> >> AHA! Useful info!! GENERIC is quite close to bloated, so the fact that it >> is >> GENERIC + SMP maybe an edge case. I'll try and test this out now that you >> have >> actually provided some useful info. :-P If you want a stable box, try >> trimming the kernel config down to what you need. > > You read too much into that, I dont normally run a GENERIC kernel, > I run one stripped down to what I need, I gave you guys a generic > example of what fails, and what can easily be reproduced. > > Anyhow, I have asked before to have you guys supply me with > a kernel that has been compiled "the right way" and I'll test > it out here just to make sure I dont do anything stupid.. > > Just a bare bones kernel, fxp & ata drivers will do nicely for the > serverworks thingy, give me an URL I can get it from or put it > on ftp.freebsd.dk/incoming and give my a ping when its there... Ok, will do. I'll even compile it on an SMP box. :-P I'm also adding in several debugging options that hopefully will casue it to have an informative panic rather than a hang or reboot. > -Søren -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 11:36: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id BAE3B37B6F0 for ; Wed, 17 Jan 2001 11:35:29 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA25627; Wed, 17 Jan 2001 20:35:24 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101171935.UAA25627@freebsd.dk> Subject: Re: Debugging SMP instability (was Re: HEADS-UP: await/asleep removal imminent) In-Reply-To: <20010117111221.T61852@canonware.com> from Jason Evans at "Jan 17, 2001 11:12:21 am" To: jasone@canonware.com (Jason Evans) Date: Wed, 17 Jan 2001 20:35:24 +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 Jason Evans wrote: > On Wed, Jan 17, 2001 at 07:42:26PM +0100, Soren Schmidt wrote: > > > Basically if you're expecting me or the SMP team to figure out > > > what's going on without more info, you're pretty much out of luck. > > > > See above, not really possible, we have been trying to find some > > (affordable) HW that could be used to preserve a log over a boot, > > but so far I havn't been able to find anything that works, and > > is fast enough to not effect the system too much... > > I did some research on this and am convinced that at least some video cards > would work as memory buffers for KTR logs. Specifically, someone mentioned > to me yesterday that their Matrox Millennium II flashes the X desktop > during startup from a previous invocation across warm boots. (I pursued > some alternatives and found the PCI RAM cards to be prohibitively expensive > (more than $700), and sound cards to not have enough RAM except on old > SoundBlaster AWE cards.) Hmm, I've been toying with this, but the el cheapo videocards I have all lose random amounts of their video RAM over a reset, probably due to the DRAM refresh being absent for too long... > For someone with device driver experience, I expect it would be a few hours > of effort to make it possible to use a second video card (or even the > primary one for that matter) as a DMA region in which KTR logs can be > saved, so that there is a way to debug even these spontaneous reboots > you're having. Maybe I'll eventually get to implementing this myself, but > to be honest, I don't have a driving need for it right now, whereas you > do. =) Do you need DMA ?? a simple ptr to the mem should do (and much easier to get to work)... > You're experiencing a stability problem that none of us (SMPng people) can > reproduce. We'd love to fix the problem, but without more information, > your reports are only slightly more useful than the typical newbie "it's > broken" reports, though certainly more frustrating. Well, I'm not alone thats for sure, and since this has been so for months I've almost gotten to the impression that something fundamental must be wrong, however until now I've just been told to go away :) I know these problems are a bitch to find, but we need to take this at least semi professionalistic and find out whats wrong, or 5.0 will be a disater when it hits the streets. I dont have the time to play around with SMP for the time being, but I do expect the SMPng group to take these problems seriously instead of the "it works here" attitude thats been hollering down the halls lately.. Again I'll offer to run any and all code or patches to -current you guys can come up with, but I simply dont have the time to sit down and analyze into details what you have been doing... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 11:41:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 919BE37B6A5; Wed, 17 Jan 2001 11:41:29 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0HJfIZ54249; Wed, 17 Jan 2001 20:41:18 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Alfred Perlstein Cc: Soren Schmidt , Randell Jesup , arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: Your message of "Wed, 17 Jan 2001 10:43:18 PST." <20010117104318.U7240@fw.wintelcom.net> Date: Wed, 17 Jan 2001 20:41:18 +0100 Message-ID: <54247.979760478@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010117104318.U7240@fw.wintelcom.net>, Alfred Perlstein writes: >* Poul-Henning Kamp [010117 10:25] wrote: >> >> >Perhaps you can explain how you're able to trigger this instability >> >with a test script? Poul-Henning told me he just needed to do a >> >make -j256 world, I did 10 of them without a problem... >> >> Then you misunderstood me, I don't have anything in the dept >> of SMP hw which can trigger it. > >If you could be more vague it would assist me greatly in figuring >out what's broken. I have been as clear as possible at all times, so if anything here has been vague, it gotta be in your end. The only reason why I'm in this fracas is to get people to take the anguished cries of sos seriously so that we don't loose our ATA maintainer... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 11:43:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id E385F37B6BA; Wed, 17 Jan 2001 11:43:21 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0HJe3L39648; Wed, 17 Jan 2001 11:40:03 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101171909.UAA19215@freebsd.dk> Date: Wed, 17 Jan 2001 11:41:56 -0800 (PST) From: John Baldwin To: Soren Schmidt Subject: Re: HEADS-UP: await/asleep removal imminent Cc: bright@wintelcom.net, rjesup@wgate.com, arch@FreeBSD.org, current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-01 Soren Schmidt wrote: > It seems John Baldwin wrote: >> >> On 17-Jan-01 Soren Schmidt wrote: >> > Nothing special, GENERIC kernel with SMP defined will do nicely, running >> > without SMP improves matters but on the fastet machine I'm still getting >> > lockups, but they are rare... >> >> AHA! Useful info!! GENERIC is quite close to bloated, so the fact that it >> is >> GENERIC + SMP maybe an edge case. I'll try and test this out now that you >> have >> actually provided some useful info. :-P If you want a stable box, try >> trimming the kernel config down to what you need. > > You read too much into that, I dont normally run a GENERIC kernel, > I run one stripped down to what I need, I gave you guys a generic > example of what fails, and what can easily be reproduced. > > Anyhow, I have asked before to have you guys supply me with > a kernel that has been compiled "the right way" and I'll test > it out here just to make sure I dont do anything stupid.. > > Just a bare bones kernel, fxp & ata drivers will do nicely for the > serverworks thingy, give me an URL I can get it from or put it > on ftp.freebsd.dk/incoming and give my a ping when its there... http://www.FreeBSD.org/~jhb/kernel.sos It was compiled wtih INCLUDE_CONFIG_FILE, so you can grab the config file from that. > -Søren -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 11:46:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id A295B37B6B0; Wed, 17 Jan 2001 11:46:10 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0HJk3Z54316; Wed, 17 Jan 2001 20:46:03 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Alfred Perlstein Cc: Soren Schmidt , Randell Jesup , arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: Your message of "Wed, 17 Jan 2001 10:52:26 PST." <20010117105226.V7240@fw.wintelcom.net> Date: Wed, 17 Jan 2001 20:46:03 +0100 Message-ID: <54314.979760763@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010117105226.V7240@fw.wintelcom.net>, Alfred Perlstein writes: >> > There has to be a way for you guys to get us some reasonable >> > tracebacks or diagnostics instead of just saying "it's broke". >> >> Its close to impossible, the two symptoms I see here are either >> spontanous reboots, or solid hangs where only a reset can get >> you out, so I cant say much other than "it's broke". > >You probably have a much better understanding of low level programming >than I do, you _should_ be able to figure out what's going on. Excuse me! There is no fucking way you guys can expect anybody else to be able to debug at the rate things are being changed right now. >> Hmm, with a -current kernel from today 1200 CET i just need to >> do a make depend on a GENERIC kernel, and wham it locks up. > >Odd, doesn't hang for me. "Absense of evidence is not evidence of absense". Remember that. >I think phk just told me that you need a UP kernel to find this, >but he's being pretty vague about it so I don't know. No I told you that I have not been able to reproduce this because my SMP boxes are too slow to matter. Or maybe because they have to few and too ancient disks. Or maybe because I don't have time to really give them a beating these days. I don't know. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 11:48:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 30E3037B402; Wed, 17 Jan 2001 11:47:51 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0HJlmZ54346; Wed, 17 Jan 2001 20:47:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: current@FreeBSD.org, arch@FreeBSD.org, Randell Jesup , Soren Schmidt , Alfred Perlstein Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: Your message of "Wed, 17 Jan 2001 10:55:09 PST." Date: Wed, 17 Jan 2001 20:47:48 +0100 Message-ID: <54340.979760868@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Baldwin writes: > >On 17-Jan-01 Poul-Henning Kamp wrote: >> >>>Perhaps you can explain how you're able to trigger this instability >>>with a test script? Poul-Henning told me he just needed to do a >>>make -j256 world, I did 10 of them without a problem... >> >> Then you misunderstood me, I don't have anything in the dept >> of SMP hw which can trigger it. > >Ok, what _does_ trigger this then? My theory is that it's related to disk-IO. My guess is that it may be related to calling a *_strategy() routine from an interrupt routine. That is what sets ccd, ata-raid and vinum apart from normal disk-IO. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 11:50:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id C450137B6EC; Wed, 17 Jan 2001 11:50:29 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0HJoT149144; Wed, 17 Jan 2001 11:50:29 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Jan 2001 11:50:29 -0800 (PST) From: Matt Dillon Message-Id: <200101171950.f0HJoT149144@earth.backplane.com> To: John Baldwin Cc: current@FreeBSD.org, arch@FreeBSD.org, Soren Schmidt , Randell Jesup , Alfred Perlstein Subject: Re: HEADS-UP: await/asleep removal imminent References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>:... :>: :>:The lock must be unwound becasue we're calling MGETHDR with M_TRYWAIT. :>:If wae used M_TRY'A'WAIT the code would probably look something like :>:this: :> :> The basic premis of using asleep()/await() is to allow you to :> propogate a 'blocking condition' back up to a higher level rather :> then blocking deep in side the kernel. : :Gotcha. Given that, if we switch to using condition variables for this, why :not have the low level code return a pointer to a cv to wait on? This would do :the same thing using an existing API (now) and I think would serve the same :purposes as your API. Returning NULL for a cv would mean that no sleep was :required. : :-- : :John Baldwin -- http://www.FreeBSD.org/~jhb/ You could but that would require massive changes to the API for many of the calls. It's probably easier for the low level code to passively install the pointer into the proc structure and return 'NULL' - which is more likely to already be supported or mostly supported by the API. Don't get me wrong, the caller needs to know what is going on, but there is something to be said for not passing yet another argument to half the procedures in the kernel :-) One of the best things about a passive pointer in the proc structure as per my proposal is that the caller can decide to ignore it, can NULL it out, can leave it in place and propogate the failure upwards, or can replace it with another condition pointer. This gives the caller an incredible amount of flexibility in how it decides to handle the blocking condition, all without introducing any overhead. -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 17 11:52:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 596D937B6F0; Wed, 17 Jan 2001 11:52:18 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0HJqFZ54517; Wed, 17 Jan 2001 20:52:15 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: Soren Schmidt , bright@wintelcom.net, rjesup@wgate.com, arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: Your message of "Wed, 17 Jan 2001 11:41:56 PST." Date: Wed, 17 Jan 2001 20:52:15 +0100 Message-ID: <54515.979761135@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John, It might be nice with a "How to provide useful info on SMPng problems." FAQ somewhere. I have no idea which of all the WITNESS and other options do what and when they are useful... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 11:55:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7C17737B699; Wed, 17 Jan 2001 11:55:30 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA30462; Wed, 17 Jan 2001 20:55:29 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101171955.UAA30462@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: from John Baldwin at "Jan 17, 2001 11:41:56 am" To: jhb@FreeBSD.ORG (John Baldwin) Date: Wed, 17 Jan 2001 20:55:28 +0100 (CET) Cc: bright@wintelcom.net, rjesup@wgate.com, arch@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 John Baldwin wrote: > > Anyhow, I have asked before to have you guys supply me with > > a kernel that has been compiled "the right way" and I'll test > > it out here just to make sure I dont do anything stupid.. > > > > Just a bare bones kernel, fxp & ata drivers will do nicely for the > > serverworks thingy, give me an URL I can get it from or put it > > on ftp.freebsd.dk/incoming and give my a ping when its there... > > http://www.FreeBSD.org/~jhb/kernel.sos > > It was compiled wtih INCLUDE_CONFIG_FILE, so you can grab the config file from > that. Roger, I'll put it on as soon as the box finishes what its doing now, I'll get back to you... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 12: 1:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 109B337B6AD; Wed, 17 Jan 2001 12:00:53 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0HJuqL40169; Wed, 17 Jan 2001 11:56:52 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <54515.979761135@critter> Date: Wed, 17 Jan 2001 11:58:46 -0800 (PST) From: John Baldwin To: Poul-Henning Kamp Subject: Re: HEADS-UP: await/asleep removal imminent Cc: current@FreeBSD.org, arch@FreeBSD.org, rjesup@wgate.com, bright@wintelcom.net, Soren Schmidt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-01 Poul-Henning Kamp wrote: > > John, > > It might be nice with a "How to provide useful info on SMPng > problems." FAQ somewhere. > > I have no idea which of all the WITNESS and other options > do what and when they are useful... Fair enough. One thing on my todo list is a ktr.9 manpage documenting its use as it is one of the things I've found useful so far. Some other general docco I'll try and come up with as well. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 12: 6:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id B317F37B6D6 for ; Wed, 17 Jan 2001 12:06:15 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA26390; Thu, 18 Jan 2001 07:06:12 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01JZ1LDPPANKEMY4F4@cim.alcatel.com.au>; Thu, 18 Jan 2001 07:06:11 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id f0HK69o12156; Thu, 18 Jan 2001 07:06:09 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Thu, 18 Jan 2001 07:06:09 +1100 From: Peter Jeremy Subject: Re: Atomic breakage? In-reply-to: <200101171543.KAA18055@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Wed, Jan 17, 2001 at 10:43:10AM -0500 To: Garrett Wollman Cc: current@FreeBSD.ORG Mail-followup-to: Garrett Wollman , current@FreeBSD.ORG Message-id: <20010118070608.D98607@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <3A64AA23.30035A1C@elischer.org> <20010116191009.E7240@fw.wintelcom.net> <20010117142654.A98607@gsmx07.alcatel.com.au> <200101171543.KAA18055@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-17 10:43:10 -0500, Garrett Wollman wrote: >< said: > >> To support multiple masters, you need proper locks. > >On older processors, yes. On processors with the CX8 feature bit set, >you can do it without any sort of locking (indeed, this is a primitive >that semaphores can be built upon). This particular sub-thread was specifically discussing the 80386 - as I thought was clear from the context. I am aware of the CMPXCHG8B insn, but it's not relevant to the 386 or 486. >On pre-Pentium processors (which lack the CX8 feature) this sort of >sequence is impossible. OTOH, I don't think SMP works on any >pre-Pentium processor, so again this degenerates to: There are SMP machines using both 386 and 486 processors. There is no support in FreeBSD for SMP on pre-Pentium processors. 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 17 12:18:14 2001 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 C8F5D37B6B2 for ; Wed, 17 Jan 2001 12:17:53 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id PAA20488; Wed, 17 Jan 2001 15:17:45 -0500 (EST) (envelope-from wollman) Date: Wed, 17 Jan 2001 15:17:45 -0500 (EST) From: Garrett Wollman Message-Id: <200101172017.PAA20488@khavrinen.lcs.mit.edu> To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Atomic breakage? In-Reply-To: <20010118070608.D98607@gsmx07.alcatel.com.au> References: <3A64AA23.30035A1C@elischer.org> <20010116191009.E7240@fw.wintelcom.net> <20010117142654.A98607@gsmx07.alcatel.com.au> <200101171543.KAA18055@khavrinen.lcs.mit.edu> <20010118070608.D98607@gsmx07.alcatel.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > There are SMP machines using both 386 and 486 processors. There is > no support in FreeBSD for SMP on pre-Pentium processors. Yes, I well recall the Sequent. I wish for it to remain a memory. -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 17 12:22:22 2001 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 09FBC37B404; Wed, 17 Jan 2001 12:22:00 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id VAA44246; Wed, 17 Jan 2001 21:19:50 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Poul-Henning Kamp Cc: John Baldwin , Soren Schmidt , bright@wintelcom.net, rjesup@wgate.com, arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent References: <54515.979761135@critter> From: Dag-Erling Smorgrav Date: 17 Jan 2001 21:19:49 +0100 In-Reply-To: Poul-Henning Kamp's message of "Wed, 17 Jan 2001 20:52:15 +0100" Message-ID: Lines: 14 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 Poul-Henning Kamp writes: > It might be nice with a "How to provide useful info on SMPng > problems." FAQ somewhere. I'd also like a "KTR for fun and profit" FAQ... > I have no idea which of all the WITNESS and other options > do what and when they are useful... WITNESS, at least, is fairly well documented in NOTES. DES -- Dag-Erling Smorgrav - des@ofug.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 17 12:26:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 2678137B698; Wed, 17 Jan 2001 12:25:57 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA27841; Thu, 18 Jan 2001 07:23:07 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01JZ1LYNYTNKEMY2IF@cim.alcatel.com.au>; Thu, 18 Jan 2001 07:23:05 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id f0HKN2212246; Thu, 18 Jan 2001 07:23:02 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Thu, 18 Jan 2001 07:23:02 +1100 From: Peter Jeremy Subject: Re: Atomic breakage? In-reply-to: ; from jhb@FreeBSD.ORG on Wed, Jan 17, 2001 at 10:28:03AM -0800 To: John Baldwin Cc: Poul-Henning Kamp , current@FreeBSD.ORG, Garrett Wollman , Robert Drehmel Mail-followup-to: John Baldwin , Poul-Henning Kamp , current@FreeBSD.ORG, Garrett Wollman , Robert Drehmel Message-id: <20010118072302.E98607@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <53512.979753444@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-17 10:28:03 -0800, John Baldwin wrote: > So as long as we keep all >atomically-accessed 64-bit integers within a single page we should be fine for >CX8 on all pentiums should we even want 64-bit atomic ops. This comes free of charge (along with better performance) if all 64-bit objects are aligned on 8-byte boundaries. By default our gcc only enforces long (4-byte) alignment (apparently, this is part of the IA32 ABI). We can get 8-byte alignment by adding "__attribute__((aligned(8)))" to the object definition. This is one area where I think we would be better off changing our gcc to default to aligning "long long" (and maybe "double") at 8-byte boundaries. We should at least have an alignment expansion in 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 17 12:33: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from mf1.time0.com (mf1.time0.com [208.147.100.72]) by hub.freebsd.org (Postfix) with ESMTP id B047837B6CE for ; Wed, 17 Jan 2001 12:32:42 -0800 (PST) Received: from time0.com (208-147-98-92.time0.com [208.147.98.92]) by mf1.time0.com (8.9.3/8.9.0) with ESMTP id PAA21437 for ; Wed, 17 Jan 2001 15:32:41 -0500 (EST) Message-ID: <3A660146.64A28161@time0.com> Date: Wed, 17 Jan 2001 15:32:06 -0500 From: Mark Ohlund Organization: Time0, Perot Systems X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: subscribe woody@woodwrecker.com Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe woody@woodwrecker.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 17 12:59:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id B3F0C37B6A6; Wed, 17 Jan 2001 12:59:35 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0HKxTN86984; Wed, 17 Jan 2001 12:59:29 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: current@freebsd.org Cc: ken@freebsd.org Subject: Zero-copy TCP patches - missing in action? Date: Wed, 17 Jan 2001 12:59:28 -0800 Message-ID: <86980.979765168@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Weren't the zero-copy patches supposed to make it into -current some time back? I recall a little grumbling over it since it made it necessary for some other projects to sync up their own work, but nobody seemed to object in principal and zero-copy TCP is a real marketing point if we can actually implement and use it constructively. Inquiring minds want to know, etc. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 13: 7: 5 2001 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 0211337B69D for ; Wed, 17 Jan 2001 13:06:39 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA19131; Wed, 17 Jan 2001 14:06:24 -0700 (MST) (envelope-from ken) Date: Wed, 17 Jan 2001 14:06:24 -0700 From: "Kenneth D. Merry" To: Jordan Hubbard Cc: current@freebsd.org Subject: Re: Zero-copy TCP patches - missing in action? Message-ID: <20010117140624.A19087@panzer.kdm.org> References: <86980.979765168@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <86980.979765168@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Wed, Jan 17, 2001 at 12:59:28PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 17, 2001 at 12:59:28 -0800, Jordan Hubbard wrote: > Weren't the zero-copy patches supposed to make it into -current some > time back? I recall a little grumbling over it since it made it > necessary for some other projects to sync up their own work, but > nobody seemed to object in principal and zero-copy TCP is a real > marketing point if we can actually implement and use it > constructively. Inquiring minds want to know, etc. Well, there are a few things that came up when I proposed putting it into -current (on the -arch list), and I haven't gotten around to fixing those yet. Part of the problem is that I have changed jobs, and no longer have access to the hardware I was using to test things out with. Drew Gallatin has supplied remotely accessible hardware that I can use to debug things, so the main thing I need at at the moment is time to fix the issues that Bosko, Matt Dillon and others had with the code. 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 Wed Jan 17 13:19:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 6129237B401; Wed, 17 Jan 2001 13:19:27 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0HLGwL42089; Wed, 17 Jan 2001 13:16:58 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 17 Jan 2001 13:18:53 -0800 (PST) From: John Baldwin To: Dag-Erling Smorgrav Subject: Re: HEADS-UP: await/asleep removal imminent Cc: current@FreeBSD.org, arch@FreeBSD.org, rjesup@wgate.com, bright@wintelcom.net, Soren Schmidt , Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-01 Dag-Erling Smorgrav wrote: > Poul-Henning Kamp writes: >> It might be nice with a "How to provide useful info on SMPng >> problems." FAQ somewhere. > > I'd also like a "KTR for fun and profit" FAQ... ktr.9 is next on my todo list of manpages to write. I have several sitting in the queue pending review right now, but that is the next one I can start writing, hopefully sometime this week. Now that my release build box is stable and reliable again, I'm testing out releases with debug options turned on by default in GENERIC. I'm also playing with having a kernel.debug in the kernel snap by default as well. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 13:35:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by hub.freebsd.org (Postfix) with ESMTP id CDA1B37B6E7; Wed, 17 Jan 2001 13:34:30 -0800 (PST) Received: from fwd03.sul.t-online.com by mailout02.sul.t-online.com with smtp id 14J0Dt-0007nN-07; Wed, 17 Jan 2001 22:34:29 +0100 Received: from server.rock.net (340029380333-0001@[62.226.181.116]) by fmrl03.sul.t-online.com with esmtp id 14J0Dk-0IAsQCC; Wed, 17 Jan 2001 22:34:20 +0100 Received: from t-online.de (server [172.23.7.1]) by server.rock.net (8.9.3+Sun/8.9.3/Rock) with ESMTP id WAA16369; Wed, 17 Jan 2001 22:34:20 +0100 (MET) Message-ID: <3A660FDC.ABAB10F5@t-online.de> Date: Wed, 17 Jan 2001 22:34:20 +0100 From: Daniel Rock X-Mailer: Mozilla 4.7 [de] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: Hajimu UMEMOTO Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: number of processes forked since boot References: <20010116.025742.74757685.ume@FreeBSD.org> Content-Type: multipart/mixed; boundary="------------ACBB2467DA3F232ACF48A671" X-Sender: 340029380333-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dies ist eine mehrteilige Nachricht im MIME-Format. --------------ACBB2467DA3F232ACF48A671 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hajimu UMEMOTO schrieb: > > Hi, > > I wish to obtain number of processes forked since boot from userland. > So, I made a patch to intend to commit. > Any comment? I have done a similar approach. I was inspired by the "vmstat -s" output of Solaris. Therefor my solution was integrated into the vmmeter structure. Adding sysctl variables would be trivial though. Warning: The diff is from a very old source tree. It may not apply cleanly. But the modifications are trivial and should be easily spotted. -- Daniel --------------ACBB2467DA3F232ACF48A671 Content-Type: text/plain; charset=us-ascii; name="src.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="src.diff" Index: sys/kern/kern_exec.c =================================================================== RCS file: /data/cvs/src/sys/kern/kern_exec.c,v retrieving revision 1.116 diff -u -r1.116 kern_exec.c --- sys/kern/kern_exec.c 2000/09/21 09:04:17 1.116 +++ sys/kern/kern_exec.c 2000/09/21 17:34:09 @@ -47,6 +47,7 @@ #include #include #include +#include #include #include @@ -374,7 +375,10 @@ } if (error == 0) + { + ++cnt.v_exec; return (0); + } exec_fail: if (imgp->vmspace_destroyed) { Index: sys/kern/kern_fork.c =================================================================== RCS file: /data/cvs/src/sys/kern/kern_fork.c,v retrieving revision 1.82 diff -u -r1.82 kern_fork.c --- sys/kern/kern_fork.c 2000/09/14 23:07:39 1.82 +++ sys/kern/kern_fork.c 2000/09/15 23:07:29 @@ -55,6 +55,7 @@ #include #include #include +#include #include #include @@ -105,6 +106,7 @@ if (error == 0) { p->p_retval[0] = p2->p_pid; p->p_retval[1] = 0; + ++cnt.v_fork; } return error; } @@ -122,6 +124,7 @@ if (error == 0) { p->p_retval[0] = p2->p_pid; p->p_retval[1] = 0; + ++cnt.v_vfork; } return error; } Index: sys/sys/vmmeter.h =================================================================== RCS file: /data/cvs/src/sys/sys/vmmeter.h,v retrieving revision 1.21 diff -u -r1.21 vmmeter.h --- sys/sys/vmmeter.h 1999/12/29 04:24:49 1.21 +++ sys/sys/vmmeter.h 1999/12/31 02:41:29 @@ -92,6 +92,9 @@ u_int v_pageout_free_min; /* min number pages reserved for kernel */ u_int v_interrupt_free_min; /* reserved number of pages for int code */ u_int v_free_severe; /* severe depletion of pages below this pt */ + u_int v_fork; + u_int v_vfork; + u_int v_exec; }; #ifdef _KERNEL Index: usr.bin/vmstat/vmstat.c =================================================================== RCS file: /data/cvs/src/usr.bin/vmstat/vmstat.c,v retrieving revision 1.39 diff -u -r1.39 vmstat.c --- usr.bin/vmstat/vmstat.c 2000/05/05 16:07:10 1.39 +++ usr.bin/vmstat/vmstat.c 2000/05/07 21:11:18 @@ -599,6 +599,12 @@ (void)printf("%9u cpu context switches\n", sum.v_swtch); (void)printf("%9u device interrupts\n", sum.v_intr); (void)printf("%9u software interrupts\n", sum.v_soft); + (void)printf("%9u forks\n", sum.v_fork); + (void)printf("%9u vforks\n", sum.v_vfork); + (void)printf("%9u execs\n", sum.v_exec); +#ifdef vax + (void)printf("%9u pseudo-dma dz interrupts\n", sum.v_pdma); +#endif (void)printf("%9u traps\n", sum.v_trap); (void)printf("%9u system calls\n", sum.v_syscall); (void)printf("%9u swap pager pageins\n", sum.v_swapin); @@ -731,7 +737,7 @@ errx(1, "malloc"); kread(X_INTRCNT, intrcnt, (size_t)nintr); kread(X_INTRNAMES, intrname, (size_t)inamlen); - (void)printf("interrupt total rate\n"); + (void)printf("interrupt total rate\n"); inttotal = 0; nintr /= sizeof(long); while (--nintr >= 0) { --------------ACBB2467DA3F232ACF48A671-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 14:35:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from VL-MS-MR002.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 857C837B401; Wed, 17 Jan 2001 14:35:22 -0800 (PST) Received: from jehovah ([24.201.144.31]) by VL-MS-MR002.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G7BW2W00.MIA; Wed, 17 Jan 2001 17:35:20 -0500 Message-ID: <012a01c080d5$fc532270$1f90c918@jehovah> From: "Bosko Milekic" To: "Alfred Perlstein" , "Randell Jesup" , Cc: "Soren Schmidt" , , References: <200101171138.MAA11834@freebsd.dk> <20010117092109.O7240@fw.wintelcom.net> <20010117100516.Q7240@fw.wintelcom.net> Subject: Re: HEADS-UP: await/asleep removal imminent Date: Wed, 17 Jan 2001 17:36:50 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > * Alfred Perlstein [010117 09:24] wrote: > > > > I'm not going to axe it for a few days, this is a really amazing > > API that Matt added, the problem is utility and useage over code > > complexity. > > > > It's just a proposal. > > I found several places where it may be useful, but I'm not sure if the > benefits outweigh the gains. > > In a copy of the tree I've locked down the socket layer (not the entire > stack, just sockets :) ) there's code like this: > > SOCKBUF_UNLOCK(&so->so_snd, 0); > if (top == 0) { > MGETHDR(m, M_TRYWAIT, MT_DATA); > if (m == NULL) { > error = ENOBUFS; > SOCKBUF_LOCK(&so->so_snd, 0); > goto release; > } > mlen = MHLEN; > ... > SOCKBUF_LOCK(&so->so_snd, 0); /* XXX */ > > The lock must be unwound becasue we're calling MGETHDR with M_TRYWAIT. > If wae used M_TRY'A'WAIT the code would probably look something like > this: > > /* SOCKBUF_UNLOCK(&so->so_snd, 0); */ > again: > if (top == 0) { > MGETHDR(m, M_TRYWAIT, MT_DATA); > if (m == NULL) { > error = mawait(&so->so_snd.sb_mtx, -1, -1); > if (error) { > if (error == EWOULDBLOCK) > error = ENOBUFS; > goto release; > } > goto again; > /* SOCKBUF_LOCK(&so->so_snd, 0); */ > } > mlen = MHLEN; > ... > /* SOCKBUF_LOCK(&so->so_snd, 0); */ /* XXX */ > > Which means we don't have to drop the lock over the socket unless > we'd block on allocation. No. You'd still have to drop it for now. Remember? (Last commit to uipc_mbuf.c). You have to drop it because of the problem you may have if Giant is gotten before your sockbuf/socket lock. In the allocation, you may be acquiring Giant again. I don't know the exact semantics, but if you at some point may grab the sockbuf/socket lock without already holding Giant and call the allocation routine, you're opening the door for deadlock. > Matt, is this what you intended for it to do? So far I've only > seen it used to avoid races, but not to optimize out mutex > aquire/release. I've only seen it to be useful to avoid races. If you're holding a lock and you need to sleep but if you drop the lock before you actually switch you may get woken up and never find out, thus still going to sleep. With the asleep you could hold the lock and place yourself on the sleep queue such that when you drop the lock and call await, you'll find out if you've gotten awoken (you'll be removed from the sleep queue). With the interlocking with sched_lock now down in msleep(), this "feature" of asleep/await is useless. > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." Regards, Bosko. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 15:23:13 2001 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 ECA8937B400; Wed, 17 Jan 2001 15:22:52 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0HNMoQ05449; Wed, 17 Jan 2001 15:22:50 -0800 (PST) Date: Wed, 17 Jan 2001 15:22:50 -0800 From: Alfred Perlstein To: Bosko Milekic Cc: Randell Jesup , dillon@FreeBSD.ORG, Soren Schmidt , arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent Message-ID: <20010117152250.D7240@fw.wintelcom.net> References: <200101171138.MAA11834@freebsd.dk> <20010117092109.O7240@fw.wintelcom.net> <20010117100516.Q7240@fw.wintelcom.net> <012a01c080d5$fc532270$1f90c918@jehovah> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <012a01c080d5$fc532270$1f90c918@jehovah>; from bmilekic@technokratis.com on Wed, Jan 17, 2001 at 05:36:50PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Bosko Milekic [010117 14:35] wrote: > > Alfred Perlstein wrote: > > > Which means we don't have to drop the lock over the socket unless > > we'd block on allocation. > > No. You'd still have to drop it for now. Remember? (Last commit to > uipc_mbuf.c). You have to drop it because of the problem you may have if > Giant is gotten before your sockbuf/socket lock. In the allocation, you may > be acquiring Giant again. I don't know the exact semantics, but if you at > some point may grab the sockbuf/socket lock without already holding Giant and > call the allocation routine, you're opening the door for deadlock. The rest of the patches unwind giant on entry into the socket layer so grabbing Giant shouldn't be a problem. > > Matt, is this what you intended for it to do? So far I've only > > seen it used to avoid races, but not to optimize out mutex > > aquire/release. > > I've only seen it to be useful to avoid races. If you're holding a lock > and you need to sleep but if you drop the lock before you actually switch you > may get woken up and never find out, thus still going to sleep. With the > asleep you could hold the lock and place yourself on the sleep queue such > that when you drop the lock and call await, you'll find out if you've gotten > awoken (you'll be removed from the sleep queue). With the interlocking with > sched_lock now down in msleep(), this "feature" of asleep/await is useless. Read the rest of my posts, the ones not cc'd to everyone, just Matt and -arch. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 16: 2:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from sydney.worldwide.lemis.com (unknown [129.94.172.186]) by hub.freebsd.org (Postfix) with ESMTP id D6EBE37B400 for ; Wed, 17 Jan 2001 16:02:03 -0800 (PST) Received: (from grog@localhost) by sydney.worldwide.lemis.com (8.11.1/8.9.3) id f0H5LG008382; Wed, 17 Jan 2001 16:21:16 +1100 (EST) (envelope-from grog) Date: Wed, 17 Jan 2001 16:21:15 +1100 From: Greg Lehey To: Will Andrews Cc: Kenneth Wayne Culver , Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: I386_CPU Message-ID: <20010117162115.C7752@sydney.worldwide.lemis.com> References: <200101160947.f0G9lKs11014@mobile.wemm.org> <20010116092843.A1858@puck.firepipe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010116092843.A1858@puck.firepipe.net>; from will@physics.purdue.edu on Tue, Jan 16, 2001 at 09:28:43AM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 16 January 2001 at 9:28:43 -0500, Will Andrews wrote: > On Tue, Jan 16, 2001 at 09:16:14AM -0500, Kenneth Wayne Culver wrote: >> Wont this make installing using sysinstall a bit hard? I know the generic >> kernel includes all the CPU lines, so that all cpu's are recognized... so >> are you going to just take this line out of the generic kernel, and have a >> special kern.flp disk with a generic kernel that only has the i386 support >> in it? > > I don't think it's worth the effort. By the time 5.0-RELEASE goes out, > the 386 will have been around for over 10 years (actually I think it has > already reached that point and gone beyond). There are not likely to be > many more installs of FreeBSD on 386's, let alone 5.x installs. > > People who *really* want to install 5.x on a 386 can generate their own > kernel and such. Don't forget that the i386 is still a popular CPU for embedded work. Of course, embedded people will have less of an issue with sysinstall. 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 Wed Jan 17 16:16:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 0129337B699 for ; Wed, 17 Jan 2001 16:16:29 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id 6716E19CA; Wed, 17 Jan 2001 19:16:18 -0500 (EST) Date: Wed, 17 Jan 2001 19:16:18 -0500 From: Will Andrews To: Greg Lehey Cc: Will Andrews , Kenneth Wayne Culver , Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: I386_CPU Message-ID: <20010117191618.K1761@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Greg Lehey , Kenneth Wayne Culver , Peter Wemm , current@FreeBSD.ORG References: <200101160947.f0G9lKs11014@mobile.wemm.org> <20010116092843.A1858@puck.firepipe.net> <20010117162115.C7752@sydney.worldwide.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="J2pR2RtFp0tAjF3C" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010117162115.C7752@sydney.worldwide.lemis.com>; from grog@lemis.com on Wed, Jan 17, 2001 at 04:21:15PM +1100 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --J2pR2RtFp0tAjF3C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 17, 2001 at 04:21:15PM +1100, Greg Lehey wrote: > Don't forget that the i386 is still a popular CPU for embedded work. > Of course, embedded people will have less of an issue with sysinstall. Of course. But of these people, which really need 5.x's features over 4.x? Plus they can still compile I386_CPU by itself, which I'm sure they already do to keep the kernel size as small as possible. --=20 wca --J2pR2RtFp0tAjF3C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6ZjXRF47idPgWcsURAoKAAJ9l2i7wPs1uzXH7+T1If+pBlzdOzwCfSWOz yJubord/YHofLDHRlVhq2zA= =2Q6c -----END PGP SIGNATURE----- --J2pR2RtFp0tAjF3C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 17: 2:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 42EBE37B402 for ; Wed, 17 Jan 2001 17:02:10 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0I11fY51675; Wed, 17 Jan 2001 17:01:41 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Jan 2001 17:01:41 -0800 (PST) From: Matt Dillon Message-Id: <200101180101.f0I11fY51675@earth.backplane.com> To: Jason Evans Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: Debugging SMP instability (was Re: HEADS-UP: await/asleep removal imminent) References: <20010117101342.R7240@fw.wintelcom.net> <200101171842.TAA12276@freebsd.dk> <20010117111221.T61852@canonware.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I did some research on this and am convinced that at least some video cards :would work as memory buffers for KTR logs. Specifically, someone mentioned :to me yesterday that their Matrox Millennium II flashes the X desktop :during startup from a previous invocation across warm boots. (I pursued :some alternatives and found the PCI RAM cards to be prohibitively expensive :(more than $700), and sound cards to not have enough RAM except on old :SoundBlaster AWE cards.) My Voodoo 3 2000 does the same thing... crash, reboot, bring up X, and the original pre-boot display flashes before X reinitializes the screen. -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 17 17:45:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from sydney.worldwide.lemis.com (unknown [129.94.172.186]) by hub.freebsd.org (Postfix) with ESMTP id 65E0D37B400 for ; Wed, 17 Jan 2001 17:45:04 -0800 (PST) Received: (from grog@localhost) by sydney.worldwide.lemis.com (8.11.1/8.9.3) id f0HCZdV10836; Wed, 17 Jan 2001 23:35:39 +1100 (EST) (envelope-from grog) Date: Wed, 17 Jan 2001 23:35:39 +1100 From: Greg Lehey To: Will Andrews Cc: Kenneth Wayne Culver , Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: I386_CPU Message-ID: <20010117233539.C9153@sydney.worldwide.lemis.com> References: <200101160947.f0G9lKs11014@mobile.wemm.org> <20010116092843.A1858@puck.firepipe.net> <20010117162115.C7752@sydney.worldwide.lemis.com> <20010117191618.K1761@puck.firepipe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010117191618.K1761@puck.firepipe.net>; from will@physics.purdue.edu on Wed, Jan 17, 2001 at 07:16:18PM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 17 January 2001 at 19:16:18 -0500, Will Andrews wrote: > On Wed, Jan 17, 2001 at 04:21:15PM +1100, Greg Lehey wrote: >> Don't forget that the i386 is still a popular CPU for embedded work. >> Of course, embedded people will have less of an issue with sysinstall. > > Of course. But of these people, which really need 5.x's features over > 4.x? I thought about that, too. I came to the conclusion "probably not", but 4.x won't be maintained for ever. > Plus they can still compile I386_CPU by itself, which I'm sure they > already do to keep the kernel size as small as possible. Sure. As I said, the installation would be much more specific anyway. 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 Wed Jan 17 19: 8: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 14A6437B400; Wed, 17 Jan 2001 19:07:39 -0800 (PST) Received: by relay.butya.kz (Postfix, from userid 1000) id 1CF5728811; Thu, 18 Jan 2001 09:07:32 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 0D76328804; Thu, 18 Jan 2001 09:07:32 +0600 (ALMT) Date: Thu, 18 Jan 2001 09:07:31 +0600 (ALMT) From: Boris Popov To: Alfred Perlstein Cc: arch@freebsd.org, current@freebsd.org Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <20010117031618.K7240@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 Wed, 17 Jan 2001, Alfred Perlstein wrote: > I have a patch here that removes await/asleep from the kernel API. > > http://people.freebsd.org/~alfred/noasleep.diff > > Matt Dillon implemented alseep/await quite some time ago and the > only thing that's using it is ata. In order to clean up some of > the schduler and vm system I'm removing support for it. Hmm, I've found this API usable for synchronization between two kernel threads/processes: alseep(&somewhere); wakeup(&anotherprocess); await(&somewhere); where 'anotherprocess' do some job and call wakeup(&somewhere). I suspect that this can be emulated with mutexes and/or conditional variables. So, it is possible to keep the API, but change its implementation to allow mentioned cleanup of scheduler ? P.S. it is already too hard to maintain external kernel modules even within various releng_4s, not to mention -current and releng_3... -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 22: 4:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id 67E3C37B401 for ; Wed, 17 Jan 2001 22:04:23 -0800 (PST) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id HAA11429; Thu, 18 Jan 2001 07:02:56 +0100 (CET) Message-Id: <200101180602.HAA11429@midten.fast.no> To: sos@freebsd.dk Cc: jasone@canonware.com, current@FreeBSD.ORG Subject: Re: Debugging SMP instability (was Re: HEADS-UP: await/asleep removal imminent) From: Tor.Egge@fast.no In-Reply-To: Your message of "Wed, 17 Jan 2001 20:35:24 +0100 (CET)" References: <200101171935.UAA25627@freebsd.dk> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Thu_Jan_18_07:01:01_2001)--" Content-Transfer-Encoding: 7bit Date: Thu, 18 Jan 2001 07:02:56 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Thu_Jan_18_07:01:01_2001)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Again I'll offer to run any and all code or patches to -current you > guys can come up with, but I simply dont have the time to sit down > and analyze into details what you have been doing... The enclosed patch implements a virtual NMI pushbutton by programming the IOAPIC to deliver an NMI when sio1 generates an interrupt. DDB should be defined in the kernel config file. getty should not run on ttyd1 when this patch is applied. A serial console on sio0 is recommended. If you still cannot break into the kernel debugger when the machine locks up then a rogue device is probably blocking the system (or the debugger is trying to obtain a mutex held by somebody else) - Tor Egge ----Next_Part(Thu_Jan_18_07:01:01_2001)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Index: sys/i386/i386/mpapic.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/mpapic.c,v retrieving revision 1.45 diff -u -r1.45 mpapic.c --- sys/i386/i386/mpapic.c 2001/01/10 04:43:46 1.45 +++ sys/i386/i386/mpapic.c 2001/01/18 05:44:30 @@ -269,6 +269,41 @@ /* return GOOD status */ return 0; } + + +void +enable_sio_NMI(int irq) +{ + u_char select; /* the select register is 8 bits */ + u_int32_t flags; /* the window register is 32 bits */ + u_int32_t target; /* the window register is 32 bits */ + u_int32_t vector; /* the window register is 32 bits */ + int apic; + int pin; + + if (irq < 0 || irq > 15) { + printf("Could not enable NMI for irq %d\n", irq); + return; + } + apic = int_to_apicintpin[irq].ioapic; + pin = int_to_apicintpin[irq].int_pin; + + target = CPU_TO_ID(0) << 24; + select = IOAPIC_REDTBL0 + (2 * pin); + vector = TPR_FAST_INTS + irq; + flags = ((u_int32_t) + (IOART_INTMCLR | + IOART_TRGREDG | + IOART_INTAHI | + IOART_DESTPHY | + IOART_DELNMI)); + + io_apic_write(apic, select, flags | vector); + io_apic_write(apic, select + 1, target); + printf("Enabled NMI for irq %d\n", irq); + printf("XXX IOAPIC #%d intpin %d ->irq %d vector 0x%x (Delivery mode NMI)\n", + apic, pin, irq, vector); +} #undef DEFAULT_ISA_FLAGS #undef DEFAULT_FLAGS Index: sys/i386/i386/trap.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/trap.c,v retrieving revision 1.164 diff -u -r1.164 trap.c --- sys/i386/i386/trap.c 2001/01/10 04:43:46 1.164 +++ sys/i386/i386/trap.c 2001/01/18 05:44:30 @@ -248,7 +248,8 @@ atomic_add_int(&cnt.v_trap, 1); - if ((frame.tf_eflags & PSL_I) == 0) { + if ((frame.tf_eflags & PSL_I) == 0 && + frame.tf_trapno != T_NMI) { /* * Buggy application or kernel code has disabled * interrupts and then trapped. Enabling interrupts @@ -285,8 +286,38 @@ enable_intr(); } - mtx_enter(&Giant, MTX_DEF); + if (frame.tf_trapno == T_NMI) { + /* If we can't get Giant then forward NMI to next CPU */ + if (mtx_try_enter(&Giant, MTX_DEF) == 0) { + u_long icr_lo; + u_long icr_hi; + int target; + + target = PCPU_GET(cpuid) + 1; + if (((1 << target) & PCPU_GET(other_cpus)) == 0) + target = 0; + + /* write the destination field for the target AP */ + icr_hi = (lapic.icr_hi & ~APIC_ID_MASK) | + (cpu_num_to_apic_id[target] << 24); + lapic.icr_hi = icr_hi; + + /* write command */ + icr_lo = (lapic.icr_lo & APIC_RESV2_MASK) | + APIC_DEST_DESTFLD | APIC_DELMODE_NMI | 0xff; + lapic.icr_lo = icr_lo; + + /* wait for pending status end */ + while (lapic.icr_lo & APIC_DELSTAT_MASK) + /* spin */ ; + __asm __volatile("int $0xff"); + + return; + } + } else + mtx_enter(&Giant, MTX_DEF); + #if defined(I586_CPU) && !defined(NO_F00F_HACK) restart: #endif @@ -388,6 +419,9 @@ */ if (ddb_on_nmi) { printf ("NMI ... going to debugger\n"); + sioEATintr(); + __asm __volatile("int $0xff"); + enable_intr(); kdb_trap (type, 0, &frame); } #endif /* DDB */ @@ -617,6 +651,9 @@ */ if (ddb_on_nmi) { printf ("NMI ... going to debugger\n"); + sioEATintr(); + __asm __volatile("int $0xff"); + enable_intr(); kdb_trap (type, 0, &frame); } #endif /* DDB */ Index: sys/isa/sio.c =================================================================== RCS file: /home/ncvs/src/sys/isa/sio.c,v retrieving revision 1.321 diff -u -r1.321 sio.c --- sys/isa/sio.c 2000/12/26 06:52:57 1.321 +++ sys/isa/sio.c 2001/01/18 05:44:30 @@ -439,6 +439,17 @@ { -1, -1 } }; +#define DDB_BREAK_MASK (IER_ERXRDY | IER_ETXRDY | IER_ERLS | IER_EMSC) +#define DDB_NMI + +#ifdef TRIPLE_BREAK_TO_DEBUGGER +#ifndef TRIPLE_BREAK_TIMEOUT +#define TRIPLE_BREAK_TIMEOUT 10 +#endif +int triple_break_count; /* number of breaks detected */ +int triple_break_time; /* time_second sampled at first break */ +#endif + #ifdef COM_ESP /* XXX configure this properly. */ static Port_t likely_com_ports[] = { 0x3f8, 0x2f8, 0x3e8, 0x2e8, }; @@ -1179,6 +1190,33 @@ com->lt_out.c_ispeed = com->lt_out.c_ospeed = com->lt_in.c_ispeed = com->lt_in.c_ospeed = com->it_in.c_ispeed = com->it_in.c_ospeed = comdefaultrate; +#if defined(DDB) && defined(BREAK_TO_DEBUGGER) && defined(DDB_BREAK_MASK) + outb(iobase + com_ier, DDB_BREAK_MASK); +#endif +#if defined(DDB) && defined(DDB_BREAK_MASK) && defined(DDB_NMI) + } else if (unit == 1) { + com->it_in.c_ispeed = com->it_in.c_ospeed = TTYDEF_SPEED; + com->it_in.c_iflag = TTYDEF_IFLAG; + com->it_in.c_oflag = TTYDEF_OFLAG; + com->it_in.c_cflag = TTYDEF_CFLAG | CLOCAL; + com->it_in.c_lflag = TTYDEF_LFLAG; + com->lt_out.c_cflag = com->lt_in.c_cflag = CLOCAL; + com->lt_out.c_ispeed = com->lt_out.c_ospeed = + com->lt_in.c_ispeed = com->lt_in.c_ospeed = + com->it_in.c_ispeed = com->it_in.c_ospeed = + comdefaultrate; + (void) inb(com->line_status_port); + (void) inb(com->data_port); + com->prev_modem_status = com->last_modem_status + = inb(com->modem_status_port); + if (COM_IIR_TXRDYBUG(com->flags)) { + outb(com->intr_ctl_port, IER_ERXRDY | IER_ERLS + | IER_EMSC); + } else { + outb(com->intr_ctl_port, IER_ERXRDY | IER_ETXRDY + | IER_ERLS | IER_EMSC); + } +#endif } else com->it_in.c_ispeed = com->it_in.c_ospeed = TTYDEF_SPEED; if (siosetwater(com, com->it_in.c_ispeed) != 0) { @@ -1355,10 +1393,56 @@ if (ret) device_printf(dev, "could not activate interrupt\n"); } +#if defined(DDB) && defined(DDB_BREAK_MASK) && defined(DDB_NMI) && defined(APIC_IO) + if (unit == 1) { + u_long xirq; + if (bus_get_resource(dev, SYS_RES_IRQ, 0, &xirq, NULL) == 0) { + printf("XXX: sio1 irq is %lu\n", xirq); + enable_sio_NMI(xirq); + } + } +#endif return (0); } + +void +sioEATintr(void) +{ + struct com_s *com; + u_char line_status; + u_char modem_status; + u_char recv_data; + u_char int_ctl; + u_char int_id; + + com = com_addr(1); + if (com == NULL) + return; + + int_id = inb(com->int_id_port); + int_ctl = inb(com->intr_ctl_port); + while (1) { + line_status = inb(com->line_status_port); + while (line_status & LSR_RCV_MASK) { + if ((line_status & LSR_RXRDY) == 0) + recv_data = 0; + else + recv_data = inb(com->data_port); + if ((line_status & + (LSR_BI | LSR_FE | LSR_PE)) != 0) { + } + line_status = inb(com->line_status_port); + } + modem_status = inb(com->modem_status_port); + int_id = inb(com->int_id_port); + if ((int_id & IIR_IMASK) == IIR_NOPEND) + break; + } +} + + static int sioopen(dev, flag, mode, p) dev_t dev; @@ -1596,7 +1680,12 @@ com->pps.ppsparam.mode = 0; sio_setreg(com, com_cfcr, com->cfcr_image &= ~CFCR_SBREAK); { - sio_setreg(com, com_ier, 0); +#if defined(DDB) && defined(BREAK_TO_DEBUGGER) && defined(DDB_BREAK_MASK) + if (com->unit == comconsole) + sio_setreg(com, com_ier, DDB_BREAK_MASK); + else +#endif + sio_setreg(com, com_ier, 0); tp = com->tp; if (tp->t_cflag & HUPCL /* @@ -1946,7 +2035,27 @@ if (line_status & LSR_BI) { #if defined(DDB) && defined(BREAK_TO_DEBUGGER) if (com->unit == comconsole) { +#ifdef TRIPLE_BREAK_TO_DEBUGGER + if (time_second > + triple_break_time + + TRIPLE_BREAK_TIMEOUT) + triple_break_count = 0; + triple_break_count++; + if (triple_break_count == 1) + triple_break_time = + time_second; + else if (triple_break_count + == 3) { + triple_break_count = 0; + mtx_exit(&sio_lock, MTX_SPIN); + breakpoint(); + mtx_enter(&sio_lock, MTX_SPIN); + } +#else + mtx_exit(&sio_lock, MTX_SPIN); breakpoint(); + mtx_enter(&sio_lock, MTX_SPIN); +#endif goto cont; } #endif ----Next_Part(Thu_Jan_18_07:01:01_2001)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 17 22:27:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id BBD3C37B401 for ; Wed, 17 Jan 2001 22:27:28 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0I6RJs43375; Wed, 17 Jan 2001 23:27:19 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101180627.f0I6RJs43375@harmony.village.org> To: Greg Lehey Subject: Re: HEADS UP: I386_CPU Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 17 Jan 2001 16:21:15 +1100." <20010117162115.C7752@sydney.worldwide.lemis.com> References: <20010117162115.C7752@sydney.worldwide.lemis.com> <200101160947.f0G9lKs11014@mobile.wemm.org> <20010116092843.A1858@puck.firepipe.net> Date: Wed, 17 Jan 2001 23:27:19 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010117162115.C7752@sydney.worldwide.lemis.com> Greg Lehey writes: : Don't forget that the i386 is still a popular CPU for embedded work. : Of course, embedded people will have less of an issue with sysinstall. We have basically an embedded environment and we don't use sysinstall at all for building our CF. And we're targeting 486 and 586 class processors that have enough juice to run sysinstall. It is easier to create the part and put it into the device than it is to create it in-suitu. 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 17 22:34:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id E8FFD37B401 for ; Wed, 17 Jan 2001 22:34:26 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0I6Y9s43405; Wed, 17 Jan 2001 23:34:10 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101180634.f0I6Y9s43405@harmony.village.org> To: Will Andrews Subject: Re: HEADS UP: I386_CPU Cc: Greg Lehey , Kenneth Wayne Culver , Peter Wemm , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 17 Jan 2001 19:16:18 EST." <20010117191618.K1761@puck.firepipe.net> References: <20010117191618.K1761@puck.firepipe.net> <200101160947.f0G9lKs11014@mobile.wemm.org> <20010116092843.A1858@puck.firepipe.net> <20010117162115.C7752@sydney.worldwide.lemis.com> Date: Wed, 17 Jan 2001 23:34:09 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010117191618.K1761@puck.firepipe.net> Will Andrews writes: : Of course. But of these people, which really need 5.x's features over : 4.x? Plus they can still compile I386_CPU by itself, which I'm sure : they already do to keep the kernel size as small as possible. That's a red herring. The new features thing is what I mean. If I were creating a product, I'd want one that is supported. So even if I don't *NEED* a feature in 5.x, I might migrate my product to 5.x so that I can continue to get bug fixes and leverage more support than I can get with an older rev. One of the 5.x features might well be a new compiler. I don't see that sort of thing being back ported to 4.x at this point. That's one of the big reasons that we're 4.x based right now rather than 3.x based, despite 4.x's slightly larger memory footprint. That and 4.x's much better c++ compiler. So it isn't as simple as you are trying to paint it. 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 17 22:36:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7D6C737B402 for ; Wed, 17 Jan 2001 22:36:04 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0I6Zws43427; Wed, 17 Jan 2001 23:35:58 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101180635.f0I6Zws43427@harmony.village.org> To: Greg Lehey Subject: Re: HEADS UP: I386_CPU Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 17 Jan 2001 23:35:39 +1100." <20010117233539.C9153@sydney.worldwide.lemis.com> References: <20010117233539.C9153@sydney.worldwide.lemis.com> <200101160947.f0G9lKs11014@mobile.wemm.org> <20010116092843.A1858@puck.firepipe.net> <20010117162115.C7752@sydney.worldwide.lemis.com> <20010117191618.K1761@puck.firepipe.net> Date: Wed, 17 Jan 2001 23:35:58 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010117233539.C9153@sydney.worldwide.lemis.com> Greg Lehey writes: : > Of course. But of these people, which really need 5.x's features over : > 4.x? : : I thought about that, too. I came to the conclusion "probably not", : but 4.x won't be maintained for ever. Compiler technology maybe? But maintainence and "mind share" with the main FreeBSD developer team are also issues that someone in this situation will need to consider. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 0: 3:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2D7F137B400; Thu, 18 Jan 2001 00:02:57 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA03496; Thu, 18 Jan 2001 09:02:55 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101180802.JAA03496@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: from John Baldwin at "Jan 17, 2001 11:41:56 am" To: jhb@FreeBSD.ORG (John Baldwin) Date: Thu, 18 Jan 2001 09:02:55 +0100 (CET) Cc: bright@wintelcom.net, rjesup@wgate.com, arch@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 John Baldwin wrote: > > Anyhow, I have asked before to have you guys supply me with > > a kernel that has been compiled "the right way" and I'll test > > it out here just to make sure I dont do anything stupid.. > > > > Just a bare bones kernel, fxp & ata drivers will do nicely for the > > serverworks thingy, give me an URL I can get it from or put it > > on ftp.freebsd.dk/incoming and give my a ping when its there... > > http://www.FreeBSD.org/~jhb/kernel.sos > > It was compiled wtih INCLUDE_CONFIG_FILE, so you can grab the config file from > that. Now this is "interesting", I booted on your kernel, and it has run through make world 4 times in a row... So I felt lucky, checked out a new fresh src/sys tree, and made a new kernel from the config file you used, reboot, starts test, and *HANG* Hmm!! Now I have tried a sys tree from today (0800 CET) two days ago and a week ago, and all 3 of them produces the lockup. So the only thing I can think of is that you guys have something in your src trees that cvs & I dont... Now what ? -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 18 0: 9: 3 2001 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 C705A37B402; Thu, 18 Jan 2001 00:08:38 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0I87M419862; Thu, 18 Jan 2001 00:07:22 -0800 (PST) Date: Thu, 18 Jan 2001 00:07:22 -0800 From: Alfred Perlstein To: Soren Schmidt Cc: John Baldwin , rjesup@wgate.com, arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent Message-ID: <20010118000721.M7240@fw.wintelcom.net> References: <200101180802.JAA03496@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101180802.JAA03496@freebsd.dk>; from sos@freebsd.dk on Thu, Jan 18, 2001 at 09:02:55AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Soren Schmidt [010118 00:03] wrote: > It seems John Baldwin wrote: > > > Anyhow, I have asked before to have you guys supply me with > > > a kernel that has been compiled "the right way" and I'll test > > > it out here just to make sure I dont do anything stupid.. > > > > > > Just a bare bones kernel, fxp & ata drivers will do nicely for the > > > serverworks thingy, give me an URL I can get it from or put it > > > on ftp.freebsd.dk/incoming and give my a ping when its there... > > > > http://www.FreeBSD.org/~jhb/kernel.sos > > > > It was compiled wtih INCLUDE_CONFIG_FILE, so you can grab the config file from > > that. > > Now this is "interesting", I booted on your kernel, and it has run > through make world 4 times in a row... > > So I felt lucky, checked out a new fresh src/sys tree, and made a new > kernel from the config file you used, reboot, starts test, and *HANG* > > Hmm!! > > Now I have tried a sys tree from today (0800 CET) two days ago and a > week ago, and all 3 of them produces the lockup. > > So the only thing I can think of is that you guys have something in > your src trees that cvs & I dont... > > Now what ? What are the compile flags you are using? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 0:16:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id CC10D37B402; Thu, 18 Jan 2001 00:15:47 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA06438; Thu, 18 Jan 2001 09:15:30 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101180815.JAA06438@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <20010118000721.M7240@fw.wintelcom.net> from Alfred Perlstein at "Jan 18, 2001 00:07:22 am" To: bright@wintelcom.net (Alfred Perlstein) Date: Thu, 18 Jan 2001 09:15:28 +0100 (CET) Cc: jhb@FreeBSD.ORG (John Baldwin), rjesup@wgate.com, arch@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 Alfred Perlstein wrote: > > Now this is "interesting", I booted on your kernel, and it has run > > through make world 4 times in a row... > > > > So I felt lucky, checked out a new fresh src/sys tree, and made a new > > kernel from the config file you used, reboot, starts test, and *HANG* > > > > Hmm!! > > > > Now I have tried a sys tree from today (0800 CET) two days ago and a > > week ago, and all 3 of them produces the lockup. > > > > So the only thing I can think of is that you guys have something in > > your src trees that cvs & I dont... > > > > Now what ? > > What are the compile flags you are using? Run of the mill std /etc/defaults/make.conf nothing else, just copied from /usr/src/defaults/make.conf... And a clean env also btw... -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 18 0:33:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 36FA537B400; Thu, 18 Jan 2001 00:33:33 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0I8bXs67198; Thu, 18 Jan 2001 00:37:33 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010118000721.M7240@fw.wintelcom.net> Date: Thu, 18 Jan 2001 00:33:30 -0800 (PST) From: John Baldwin To: Alfred Perlstein Subject: Re: HEADS-UP: await/asleep removal imminent Cc: current@FreeBSD.org, arch@FreeBSD.org, rjesup@wgate.com, Soren Schmidt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jan-01 Alfred Perlstein wrote: > * Soren Schmidt [010118 00:03] wrote: >> It seems John Baldwin wrote: >> > > Anyhow, I have asked before to have you guys supply me with >> > > a kernel that has been compiled "the right way" and I'll test >> > > it out here just to make sure I dont do anything stupid.. >> > > >> > > Just a bare bones kernel, fxp & ata drivers will do nicely for the >> > > serverworks thingy, give me an URL I can get it from or put it >> > > on ftp.freebsd.dk/incoming and give my a ping when its there... >> > >> > http://www.FreeBSD.org/~jhb/kernel.sos >> > >> > It was compiled wtih INCLUDE_CONFIG_FILE, so you can grab the config file >> > from >> > that. >> >> Now this is "interesting", I booted on your kernel, and it has run >> through make world 4 times in a row... >> >> So I felt lucky, checked out a new fresh src/sys tree, and made a new >> kernel from the config file you used, reboot, starts test, and *HANG* >> >> Hmm!! >> >> Now I have tried a sys tree from today (0800 CET) two days ago and a >> week ago, and all 3 of them produces the lockup. >> >> So the only thing I can think of is that you guys have something in >> your src trees that cvs & I dont... >> >> Now what ? > > What are the compile flags you are using? I actually used this: CFLAGS ?= -O -pipe -mcpu=i686 -march=i686 COPTFLAGS ?= -O -pipe -mcpu=i686 -march=i686 All the diffs in sys/ on the box I built this kernel on are at http://www.FreeBSD.org/~jhb/patches/sys-mutex.patch. One possibly notable patch I had forgotten about is the fix to forward_signal() to lock with sched_lock. I've just committed that though. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 0:43: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 489AF37B400; Thu, 18 Jan 2001 00:42:39 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA12751; Thu, 18 Jan 2001 09:42:37 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101180842.JAA12751@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: from John Baldwin at "Jan 18, 2001 00:33:30 am" To: jhb@FreeBSD.org (John Baldwin) Date: Thu, 18 Jan 2001 09:42:37 +0100 (CET) Cc: bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.org, arch@FreeBSD.org, rjesup@wgate.com 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 John Baldwin wrote: > >> > >> So the only thing I can think of is that you guys have something in > >> your src trees that cvs & I dont... > >> > >> Now what ? > > > > What are the compile flags you are using? > > I actually used this: > > CFLAGS ?= -O -pipe -mcpu=i686 -march=i686 > COPTFLAGS ?= -O -pipe -mcpu=i686 -march=i686 > > All the diffs in sys/ on the box I built this kernel on are at > http://www.FreeBSD.org/~jhb/patches/sys-mutex.patch. One possibly notable > patch I had forgotten about is the fix to forward_signal() to lock with > sched_lock. I've just committed that though. OK, I have installed those patches and will try out a kernel build on that asap.... -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 18 1:37:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 08EC537B69D for ; Thu, 18 Jan 2001 01:36:59 -0800 (PST) Received: from newsguy.com (p42-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.107]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id SAA27629; Thu, 18 Jan 2001 18:35:20 +0900 (JST) Message-ID: <3A66B475.1B3B1D28@newsguy.com> Date: Thu, 18 Jan 2001 18:16:37 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Tor.Egge@fast.no Cc: sos@freebsd.dk, jasone@canonware.com, current@FreeBSD.ORG Subject: Re: Debugging SMP instability (was Re: HEADS-UP: await/asleep removal imminent) References: <200101171935.UAA25627@freebsd.dk> <200101180602.HAA11429@midten.fast.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tor.Egge@fast.no wrote: > > The enclosed patch implements a virtual NMI pushbutton by programming > the IOAPIC to deliver an NMI when sio1 generates an interrupt. This would be a nice kernel option... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@a.crazy.bsdconspiracy.net "There is no spoon." -- Kiki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 1:57:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5FD4437B69E; Thu, 18 Jan 2001 01:57:10 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA33489; Thu, 18 Jan 2001 10:57:08 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101180957.KAA33489@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <200101180842.JAA12751@freebsd.dk> from Soren Schmidt at "Jan 18, 2001 09:42:37 am" To: sos@freebsd.dk (Soren Schmidt) Date: Thu, 18 Jan 2001 10:57:08 +0100 (CET) Cc: jhb@FreeBSD.ORG (John Baldwin), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com 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 Soren Schmidt wrote: > > I actually used this: > > > > CFLAGS ?= -O -pipe -mcpu=i686 -march=i686 > > COPTFLAGS ?= -O -pipe -mcpu=i686 -march=i686 > > > > All the diffs in sys/ on the box I built this kernel on are at > > http://www.FreeBSD.org/~jhb/patches/sys-mutex.patch. One possibly notable > > patch I had forgotten about is the fix to forward_signal() to lock with > > sched_lock. I've just committed that though. > > OK, I have installed those patches and will try out a kernel build on > that asap.... Hmm, now we are getting somewhere, it ran through a make world with that patch installed! I'll test some more, maybe you should get it all committed it seems to make a hell of a difference.... -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 18 2: 4: 2 2001 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 2BA5737B69E for ; Thu, 18 Jan 2001 02:03:44 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA08276; Thu, 18 Jan 2001 21:03:33 +1100 Date: Thu, 18 Jan 2001 21:03:45 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Garrett Wollman Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: Atomic breakage? In-Reply-To: <200101171614.LAA18224@khavrinen.lcs.mit.edu> 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, 17 Jan 2001, Garrett Wollman wrote: > < said: > > > Just wondering, can't you use 'LOCK addl' and then use 'LOCK addc'? > > add longword, add longword with carry? I know it would be pretty > > ugly, but it should work, no? > > The two bus cycles are independent, so there is a race condition. > > OTOH, it's a fairly *unlikely* race condition, and the worst thing > that can happen is statistics that are obviously off by four billion. > (The race only occurs when there is a carry out of the low-order > longword, which is to say, once in every 2**32 operations.) If they are obviously off by precisely four billion, then they can be corrected :-). I have thought of using special overflow handling methods to reduce the cost of keeping statistics. E.g.: --- uint32_t counter[2]; /* Low-level code increments only the lower 32 bits of counters. */ atomic_add_32(&counter[0]), 1); /* * Counter daemon adjusts counters before they get anywhere near * overflowing. It must run often enough to prevent overflow * (not very often). This also make the race in the adjustment * code harmless. */ KASSERT(counter[0] < 0xC0000000, "counter got near overflowing"); if (counter[0] & 0x80000000) { atomic_subtract_32(&counter[0], 0x80000000); ++counter[1]; } /* * Clients must use code like the following to convert counters * to values. More locking is required to load counter[0] and * counter[1] atomically, but this is not a new problem (e.g., * atomicity is mostly accidental for accesses via kmem). */ counter_value = ((uint64_t)counter[1] << 31) | counter[0]; --- Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 4: 6:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id BD8FB37B401; Thu, 18 Jan 2001 04:05:58 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0IC5rK13062; Thu, 18 Jan 2001 04:05:54 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101181205.f0IC5rK13062@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Soren Schmidt Cc: jhb@FreeBSD.ORG (John Baldwin), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <200101180957.KAA33489@freebsd.dk> Content-Transfer-Encoding: 8bit Date: Thu, 18 Jan 2001 04:05:53 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Soren Schmidt wrote: > > > I actually used this: > > > > > > CFLAGS ?= -O -pipe -mcpu=i686 -march=i686 > > > COPTFLAGS ?= -O -pipe -mcpu=i686 -march=i686 > > > > > > All the diffs in sys/ on the box I built this kernel on are at > > > http://www.FreeBSD.org/~jhb/patches/sys-mutex.patch. One possibly notabl e > > > patch I had forgotten about is the fix to forward_signal() to lock with > > > sched_lock. I've just committed that though. > > > > OK, I have installed those patches and will try out a kernel build on > > that asap.... > > Hmm, now we are getting somewhere, it ran through a make world with > that patch installed! > > I'll test some more, maybe you should get it all committed it seems to > make a hell of a difference.... Hmm. with the mp_machdep.c fix committed, that leaves the only other significant difference being the re-enable of HLT when a cpu goes idle in i386/i386/machdep.c. The refcount.[ch] stuff is not relevant to this problem. The kern/subr_prf.c change doesn't *appear* to be a likely candidate, unless you are printing lots of console messages during the buildworld.. The kern/vfs_aio.c are not relevant as VFS_AIO is not in GENERIC. The rest are comments, mtx_assert()'s or DDB activation related. Soren, can you retest a buildworld with the currently committed kernel with no other changes? Let us see if the forward_signal() stuff is the culprit, and if not, try adding just the i386/i386/machdep.c patch to HLT the idle CPU. (if *that* makes a difference then we have got trouble!) 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 18 4:21:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 4FC6637B400 for ; Thu, 18 Jan 2001 04:21:20 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id 21C4319C8; Thu, 18 Jan 2001 07:21:10 -0500 (EST) Date: Thu, 18 Jan 2001 07:21:10 -0500 From: Will Andrews To: Warner Losh Cc: FreeBSD Current Subject: Re: HEADS UP: I386_CPU Message-ID: <20010118072110.A431@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Warner Losh , FreeBSD Current References: <20010117191618.K1761@puck.firepipe.net> <200101160947.f0G9lKs11014@mobile.wemm.org> <20010116092843.A1858@puck.firepipe.net> <20010117162115.C7752@sydney.worldwide.lemis.com> <20010117191618.K1761@puck.firepipe.net> <200101180634.f0I6Y9s43405@harmony.village.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101180634.f0I6Y9s43405@harmony.village.org>; from imp@harmony.village.org on Wed, Jan 17, 2001 at 11:34:09PM -0700 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 17, 2001 at 11:34:09PM -0700, Warner Losh wrote: > That's a red herring. The new features thing is what I mean. If I > were creating a product, I'd want one that is supported. So even if I > don't *NEED* a feature in 5.x, I might migrate my product to 5.x so > that I can continue to get bug fixes and leverage more support than I > can get with an older rev. One of the 5.x features might well be a > new compiler. I don't see that sort of thing being back ported to 4.x > at this point. I see. I guess that makes sense, although I don't see support for 4.x dropping until sometime in 2003 (speaking in terms of the FreeBSD Project, not necessarily commercial shops like BSDI). > That's one of the big reasons that we're 4.x based right now rather > than 3.x based, despite 4.x's slightly larger memory footprint. That > and 4.x's much better c++ compiler. Well, Warner, I've never done embedded systems. So, tell me, do they actually use any C++ code in embedded systems? C++ has a rather high overhead as far as disk space & memory goes. I would imagine that 99%+ of embedded systems do not use C++ code except perhaps for a very small amount of the code. --=20 wca #include : Not speaking for FreeBSD, just myself. --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6Zt+1F47idPgWcsURAkRgAJ9nqRGf8E8yycWC0ULgGAQDfF2voQCeMGp/ Pr8Zu1SglXCRgFXmggAuOvU= =ioAU -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 5: 9:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 948E537B400; Thu, 18 Jan 2001 05:09:32 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA84777; Thu, 18 Jan 2001 14:09:21 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101181309.OAA84777@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <200101181205.f0IC5rK13062@mobile.wemm.org> from Peter Wemm at "Jan 18, 2001 04:05:53 am" To: peter@netplex.com.au (Peter Wemm) Date: Thu, 18 Jan 2001 14:09:21 +0100 (CET) Cc: jhb@FreeBSD.ORG (John Baldwin), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com 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 Peter Wemm wrote: > > Hmm. with the mp_machdep.c fix committed, that leaves the only other > significant difference being the re-enable of HLT when a cpu goes idle > in i386/i386/machdep.c. That still lockups, tried a freshly checked out sys... > The refcount.[ch] stuff is not relevant to this problem. > > The kern/subr_prf.c change doesn't *appear* to be a likely candidate, > unless you are printing lots of console messages during the buildworld.. > > The kern/vfs_aio.c are not relevant as VFS_AIO is not in GENERIC. > > The rest are comments, mtx_assert()'s or DDB activation related. > > Soren, can you retest a buildworld with the currently committed kernel > with no other changes? Let us see if the forward_signal() stuff is the > culprit, and if not, try adding just the i386/i386/machdep.c patch to HLT > the idle CPU. (if *that* makes a difference then we have got trouble!) I'll try adding the forward_signal stuff see if that helps... -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 18 5:39:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 50FC937B401; Thu, 18 Jan 2001 05:39:34 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0IDdUK14717; Thu, 18 Jan 2001 05:39:30 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101181339.f0IDdUK14717@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Soren Schmidt Cc: jhb@FreeBSD.ORG (John Baldwin), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <200101181309.OAA84777@freebsd.dk> Content-Transfer-Encoding: 8bit Date: Thu, 18 Jan 2001 05:39:30 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Peter Wemm wrote: > > > > Hmm. with the mp_machdep.c fix committed, that leaves the only other > > significant difference being the re-enable of HLT when a cpu goes idle > > in i386/i386/machdep.c. > > That still lockups, tried a freshly checked out sys... > > > The refcount.[ch] stuff is not relevant to this problem. > > > > The kern/subr_prf.c change doesn't *appear* to be a likely candidate, > > unless you are printing lots of console messages during the buildworld.. > > > > The kern/vfs_aio.c are not relevant as VFS_AIO is not in GENERIC. > > > > The rest are comments, mtx_assert()'s or DDB activation related. > > > > Soren, can you retest a buildworld with the currently committed kernel > > with no other changes? Let us see if the forward_signal() stuff is the > > culprit, and if not, try adding just the i386/i386/machdep.c patch to HLT > > the idle CPU. (if *that* makes a difference then we have got trouble!) > > I'll try adding the forward_signal stuff see if that helps... But John committed that! it should be in the fresh checkout you tried above.... Of course, that is assuming you cvsup'ed very recently.. > -Søren > 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 18 5:48:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.freebsd.org (Postfix) with ESMTP id A252D37B404 for ; Thu, 18 Jan 2001 05:48:18 -0800 (PST) Received: from fwd01.sul.t-online.com by mailout04.sul.t-online.com with smtp id 14JFQH-0003A7-00; Thu, 18 Jan 2001 14:48:17 +0100 Received: from neutron.cichlids.com (520050424122-0001@[62.225.193.235]) by fmrl01.sul.t-online.com with esmtp id 14JFQ3-1QMTNgC; Thu, 18 Jan 2001 14:48:03 +0100 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id B1118AB0C for ; Thu, 18 Jan 2001 14:49:41 +0100 (CET) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id E671514B0A; Thu, 18 Jan 2001 14:47:52 +0100 (CET) Date: Thu, 18 Jan 2001 14:47:52 +0100 To: current@freebsd.org Subject: panic: spin lock (null) held by 0x0 for > 5 seconds on 486 w/ ISA Message-ID: <20010118144752.A85031@cichlids.cichlids.com> Mail-Followup-To: alex@cichlids.cichlids.com, current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) X-Sender: 520050424122-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! This is an old 486 of mine which never ran FreeBSD before. It has only ISA and VL bus. When booting a trimmed down GENEIRC kernel from today, it shows the copyright lines and then this: panic: spin lock (null) held by 0x0 for > 5 seconds. This line repeats approx. every 30 seconds This is JFYI, I haven't tried a DDB kernel (since it has to fit on the floppy). The same kernel runs fine on a PIII and a K6-2, though. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 6: 9:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 9210F37B401; Thu, 18 Jan 2001 06:08:49 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA00170; Thu, 18 Jan 2001 15:08:42 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101181408.PAA00170@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <200101181339.f0IDdUK14717@mobile.wemm.org> from Peter Wemm at "Jan 18, 2001 05:39:30 am" To: peter@netplex.com.au (Peter Wemm) Date: Thu, 18 Jan 2001 15:08:42 +0100 (CET) Cc: jhb@FreeBSD.ORG (John Baldwin), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com 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 Peter Wemm wrote: > > I'll try adding the forward_signal stuff see if that helps... > > But John committed that! it should be in the fresh checkout you tried > above.... Of course, that is assuming you cvsup'ed very recently.. Sorry that was not what I meant, I meant this patch to machdep.c and so far it looks as thats the culprit it hasn't locked up yet at least, but its not finished a world yet.... Index: machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v retrieving revision 1.429 diff -u -r1.429 machdep.c --- machdep.c 2001/01/16 09:10:33 1.429 +++ machdep.c 2001/01/18 13:44:48 @@ -1005,6 +1005,10 @@ void cpu_idle(void) { +#ifdef SMP + /* first candidate for an interrupt */ + lapic.tpr = 0; +#endif #ifndef SMP if (cpu_idle_hlt) { disable_intr(); -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 18 6:13:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay1.bcs.zp.ua (bcs-marka.bcs.zp.ua [217.24.163.29]) by hub.freebsd.org (Postfix) with ESMTP id 1182737B402 for ; Thu, 18 Jan 2001 06:13:09 -0800 (PST) Received: (from eugen@localhost) by relay1.bcs.zp.ua (8.11.0/8.11.0) id f0IED3H22106; Thu, 18 Jan 2001 16:13:03 +0200 (EET) Date: Thu, 18 Jan 2001 16:13:03 +0200 (EET) Message-Id: <200101181413.f0IED3H22106@relay1.bcs.zp.ua> From: Eugene Polovnikov Subject: Re: HEADS UP: I386_CPU To: current@FreeBSD.ORG In-Reply-To: <20010117162115.C7752@sydney.worldwide.lemis.com> User-Agent: tin/1.5.6-20000803 ("Dust") (UNIX) (FreeBSD/4.2-RELEASE (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG how about to have in a distribution two version of GENERIC kernel (and modules of course) and let sysinstall choose right set ? In article <20010117162115.C7752@sydney.worldwide.lemis.com> you wrote: > On Tuesday, 16 January 2001 at 9:28:43 -0500, Will Andrews wrote: >> On Tue, Jan 16, 2001 at 09:16:14AM -0500, Kenneth Wayne Culver wrote: >>> Wont this make installing using sysinstall a bit hard? I know the generic >>> kernel includes all the CPU lines, so that all cpu's are recognized... so >>> are you going to just take this line out of the generic kernel, and have a >>> special kern.flp disk with a generic kernel that only has the i386 support >>> in it? >> >> I don't think it's worth the effort. By the time 5.0-RELEASE goes out, >> the 386 will have been around for over 10 years (actually I think it has >> already reached that point and gone beyond). There are not likely to be >> many more installs of FreeBSD on 386's, let alone 5.x installs. >> >> People who *really* want to install 5.x on a 386 can generate their own >> kernel and such. > Don't forget that the i386 is still a popular CPU for embedded work. > Of course, embedded people will have less of an issue with sysinstall. > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message -- end of forwarded 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 18 6:14:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5A3A337B699 for ; Thu, 18 Jan 2001 06:14:19 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0IEEGs45968; Thu, 18 Jan 2001 07:14:16 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101181414.f0IEEGs45968@harmony.village.org> To: Will Andrews Subject: Re: HEADS UP: I386_CPU Cc: FreeBSD Current In-reply-to: Your message of "Thu, 18 Jan 2001 07:21:10 EST." <20010118072110.A431@puck.firepipe.net> References: <20010118072110.A431@puck.firepipe.net> <20010117191618.K1761@puck.firepipe.net> <200101160947.f0G9lKs11014@mobile.wemm.org> <20010116092843.A1858@puck.firepipe.net> <20010117162115.C7752@sydney.worldwide.lemis.com> <20010117191618.K1761@puck.firepipe.net> <200101180634.f0I6Y9s43405@harmony.village.org> Date: Thu, 18 Jan 2001 07:14:16 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010118072110.A431@puck.firepipe.net> Will Andrews writes: : Well, Warner, I've never done embedded systems. So, tell me, do they : actually use any C++ code in embedded systems? C++ has a rather high : overhead as far as disk space & memory goes. I would imagine that 99%+ : of embedded systems do not use C++ code except perhaps for a very small : amount of the code. Yes, they do use C++. It doesn't matter what you imagine, c++ can and is used. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 6:17:54 2001 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 83E8037B699 for ; Thu, 18 Jan 2001 06:17:33 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id PAA47956; Thu, 18 Jan 2001 15:17:28 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Will Andrews Cc: Warner Losh , FreeBSD Current Subject: Re: HEADS UP: I386_CPU References: <20010117191618.K1761@puck.firepipe.net> <200101160947.f0G9lKs11014@mobile.wemm.org> <20010116092843.A1858@puck.firepipe.net> <20010117162115.C7752@sydney.worldwide.lemis.com> <20010117191618.K1761@puck.firepipe.net> <200101180634.f0I6Y9s43405@harmony.village.org> <20010118072110.A431@puck.firepipe.net> From: Dag-Erling Smorgrav Date: 18 Jan 2001 15:17:28 +0100 In-Reply-To: Will Andrews's message of "Thu, 18 Jan 2001 07:21:10 -0500" Message-ID: Lines: 16 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 Will Andrews writes: > Well, Warner, I've never done embedded systems. So, tell me, do they > actually use any C++ code in embedded systems? C++ has a rather high > overhead as far as disk space & memory goes. That's a myth. > I would imagine that 99%+ > of embedded systems do not use C++ code except perhaps for a very small > amount of the code. From experience, I would imagine the reverse. DES -- Dag-Erling Smorgrav - des@ofug.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 18 6:43:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from tfrsolcom.transfer-solutions.com (mail.transfer-solutions.com [195.109.218.250]) by hub.freebsd.org (Postfix) with ESMTP id 18CF637B699 for ; Thu, 18 Jan 2001 06:42:48 -0800 (PST) Received: by mail.transfer-solutions.com with Internet Mail Service (5.5.2650.21) id ; Thu, 18 Jan 2001 15:37:02 +0100 Received: from tfrsolcom.transfer-solutions.com (localhost [127.0.0.1]) by tfrsolcom.transfer-solutions.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id DAATSSJW; Thu, 18 Jan 2001 15:36:55 +0100 Received: from 193.100.100.198 by tfrsolcom.transfer-solutions.com (InterScan E-Mail VirusWall NT); Thu, 18 Jan 2001 15:36:54 +0100 (Romance Standard Time) From: Rogier Mulhuijzen To: freebsd-current@freebsd.org Message-Id: <5.0.2.1.0.20010118152851.00a52ec0@tfrsolcom> X-Sender: rmulhuij@tfrsolcom X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Thu, 18 Jan 2001 15:48:18 +0100 Subject: Panic w/crash dump (looks like atomic.h problem) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_189762640==_" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=====================_189762640==_ Content-Type: text/plain; charset="us-ascii"; format=flowed Got a nice crash while running XMMS under X11 and running a 'make world -j 128 -DNOCLEAN' on ttyv0 Current was cvsupped on the 17th in the morning (Central European Time) IIRC. Attached: script(1) output of gdb kernel trace Kernel config file dmesg(8) output I'm not an expert on tracing panics, I just followed the instructions in the FAQ, so feel free to ask me to look at stuff. DocWilco --=====================_189762640==_ Content-Type: text/plain; name="crash-trace2.txt"; x-mac-type="42494E41"; x-mac-creator="74747874" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="crash-trace2.txt" U2NyaXB0IHN0YXJ0ZWQgb24gVGh1IEphbiAxOCAxNjowOTo1OCAyMDAxClsgcm9vdEA6L3Vzci9z cmMvc3lzL2NvbXBpbGUvVkVOVVMgXSAjIGV4aXQICAgIZ2RiIC1rCAgICAgIG1sxUGxzIC1sCAgI CAhnZGIgLWsNCkdOVSBnZGIgNC4xOA0KQ29weXJpZ2h0IDE5OTggRnJlZSBTb2Z0d2FyZSBGb3Vu ZGF0aW9uLCBJbmMuDQpHREIgaXMgZnJlZSBzb2Z0d2FyZSwgY292ZXJlZCBieSB0aGUgR05VIEdl bmVyYWwgUHVibGljIExpY2Vuc2UsIGFuZCB5b3UgYXJlDQp3ZWxjb21lIHRvIGNoYW5nZSBpdCBh bmQvb3IgZGlzdHJpYnV0ZSBjb3BpZXMgb2YgaXQgdW5kZXIgY2VydGFpbiBjb25kaXRpb25zLg0K VHlwZSAic2hvdyBjb3B5aW5nIiB0byBzZWUgdGhlIGNvbmRpdGlvbnMuDQpUaGVyZSBpcyBhYnNv bHV0ZWx5IG5vIHdhcnJhbnR5IGZvciBHREIuICBUeXBlICJzaG93IHdhcnJhbnR5IiBmb3IgZGV0 YWlscy4NClRoaXMgR0RCIHdhcyBjb25maWd1cmVkIGFzICJpMzg2LXVua25vd24tZnJlZWJzZCIu DQooa2dkYikgc3ltb2wIIAgIIAhib2wwLQggCAggCC1maWxlIGtlcm5lbC5kZWJ1Zw0KUmVhZGlu ZyBzeW1ib2xzIGZyb20ga2VybmVsLmRlYnVnLi4uZG9uZS4NCihrZ2RiKSBleGVjLWZpbGUgL3Zh ci9jcmFzaC9rZXJuZWwuMA0KKGtnZGIpIGNvcmUtZmlsZSAvdmFyL2NyYXNoL3ZtY29yZS4wDQpJ ZGxlUFREIDUyNjc0NTYNCmluaXRpYWwgcGNiIGF0IDMxNWNlMA0KcGFuaWNzdHI6IGZyb20gZGVi dWdnZXINCnBhbmljIG1lc3NhZ2VzOg0KLS0tDQpGYXRhbCB0cmFwIDEyOiBwYWdlIGZhdWx0IHdo aWxlIGluIGtlcm5lbCBtb2RlDQpmYXVsdCB2aXJ0dWFsIGFkZHJlc3MJPSAweDZjDQpmYXVsdCBj b2RlCQk9IHN1cGVydmlzb3Igd3JpdGUsIHBhZ2Ugbm90IHByZXNlbnQNCmluc3RydWN0aW9uIHBv aW50ZXIJPSAweDg6MHhjMDFjMDU3Zg0Kc3RhY2sgcG9pbnRlcgkgICAgICAgID0gMHgxMDoweGM3 ZmYxZDU0DQpmcmFtZSBwb2ludGVyCSAgICAgICAgPSAweDEwOjB4YzdmZjFkNWMNCmNvZGUgc2Vn bWVudAkJPSBiYXNlIDB4MCwgbGltaXQgMHhmZmZmZiwgdHlwZSAweDFiDQoJCQk9IERQTCAwLCBw cmVzIDEsIGRlZjMyIDEsIGdyYW4gMQ0KcHJvY2Vzc29yIGVmbGFncwk9IGludGVycnVwdCBlbmFi bGVkLCByZXN1bWUsIElPUEwgPSAwDQpjdXJyZW50IHByb2Nlc3MJCT0gNDI3ICh4bW1zKQ0KcGFu aWM6IGZyb20gZGVidWdnZXINCnBhbmljOiBmcm9tIGRlYnVnZ2VyDQpVcHRpbWU6IDVtNTFzDQoN CmR1bXBpbmcgdG8gZGV2IGFkMHMyYiwgb2Zmc2V0IDI2MjE0NA0KZHVtcCBhdGEwOiByZXNldHRp bmcgZGV2aWNlcyAuLiBkb25lDQoxMjggMTI3IDEyNiAxMjUgMTI0IDEyMyAxMjIgMTIxIDEyMCAx MTkgMTE4IDExNyAxMTYgMTE1IDExNCAxMTMgMTEyIDExMSAxMTAgMTA5IDEwOCAxMDcgMTA2IDEw NSAxMDQgMTAzIDEwMiAxMDEgMTAwIDk5IDk4IDk3IDk2IDk1IDk0IDkzIDkyIDkxIDkwIDg5IDg4 IDg3IDg2IDg1IDg0IDgzIDgyIDgxIDgwIDc5IDc4IDc3IDc2IDc1IDc0IDczIDcyIDcxIDcwIDY5 IDY4IDY3IDY2IDY1IDY0IDYzIDYyIDYxIDYwIDU5IDU4IDU3IDU2IDU1IDU0IDUzIDUyIDUxIDUw IDQ5IDQ4IDQ3IDQ2IDQ1IDQ0IDQzIDQyIDQxIDQwIDM5IDM4IDM3IDM2IDM1IDM0IDMzIDMyIDMx IDMwIDI5IDI4IDI3IDI2IDI1IDI0IDIzIDIyIDIxIDIwIDE5IDE4IDE3IDE2IDE1IDE0IDEzIDEy IDExIDEwIDkgOCA3IDYgNSA0IDMgMiAxIA0KLS0tDQojMCAgZHVtcHN5cyAoKSBhdCAuLi8uLi9r ZXJuL2tlcm5fc2h1dGRvd24uYzo0NzcNCjQ3NwkJaWYgKGR1bXBpbmcrKykgew0KKGtnZGIpIHdo ZXJlDQojMCAgZHVtcHN5cyAoKSBhdCAuLi8uLi9rZXJuL2tlcm5fc2h1dGRvd24uYzo0NzcNCiMx ICAweGMwMTg2YzJhIGluIGJvb3QgKGhvd3RvPTI2MCkgYXQgLi4vLi4va2Vybi9rZXJuX3NodXRk b3duLmM6MzIwDQojMiAgMHhjMDE4NmZmOSBpbiBwYW5pYyAoZm10PTB4YzAyOWMzNzQgImZyb20g ZGVidWdnZXIiKQ0KICAgIGF0IC4uLy4uL2tlcm4va2Vybl9zaHV0ZG93bi5jOjU3MA0KIzMgIDB4 YzAxNDI0NTEgaW4gZGJfcGFuaWMgKGFkZHI9LTEwNzE5MDU0MDksIGhhdmVfYWRkcj0wLCBjb3Vu dD0tMSwgDQogICAgbW9kaWY9MHhjN2ZmMWJjNCAiIikgYXQgLi4vLi4vZGRiL2RiX2NvbW1hbmQu Yzo0MzMNCiM0ICAweGMwMTQyM2YxIGluIGRiX2NvbW1hbmQgKGxhc3RfY21kcD0weGMwMmRiZTM0 LCBjbWRfdGFibGU9MHhjMDJkYmM5NCwgDQogICAgYXV4X2NtZF90YWJsZXA9MHhjMDJmZjZkYykg YXQgLi4vLi4vZGRiL2RiX2NvbW1hbmQuYzozMzMNCiM1ICAweGMwMTQyNGI2IGluIGRiX2NvbW1h bmRfbG9vcCAoKSBhdCAuLi8uLi9kZGIvZGJfY29tbWFuZC5jOjQ1NQ0KIzYgIDB4YzAxNDQ2ODMg aW4gZGJfdHJhcCAodHlwZT0xMiwgY29kZT0wKSBhdCAuLi8uLi9kZGIvZGJfdHJhcC5jOjcxDQoj NyAgMHhjMDI3MmY3MiBpbiBrZGJfdHJhcCAodHlwZT0xMiwgY29kZT0wLCByZWdzPTB4YzdmZjFk MTQpDQogICAgYXQgLi4vLi4vaTM4Ni9pMzg2L2RiX2ludGVyZmFjZS5jOjE2NA0KIzggIDB4YzAy N2VjMGMgaW4gdHJhcF9mYXRhbCAoZnJhbWU9MHhjN2ZmMWQxNCwgZXZhPTEwOCkNCiAgICBhdCAu Li8uLi9pMzg2L2kzODYvdHJhcC5jOjk0OA0KIzkgIDB4YzAyN2U5NzUgaW4gdHJhcF9wZmF1bHQg KGZyYW1lPTB4YzdmZjFkMTQsIHVzZXJtb2RlPTAsIGV2YT0xMDgpDQogICAgYXQgLi4vLi4vaTM4 Ni9pMzg2L3RyYXAuYzo4NjcNCiMxMCAweGMwMjdlMTJjIGluIHRyYXAgKGZyYW1lPXt0Zl9mcyA9 IC05Mzk1ODk2MDgsIHRmX2VzID0gLTEwNzE5NzIzMzYsIA0KICAgICAgdGZfZHMgPSAtOTM5Nzg2 MjI0LCB0Zl9lZGkgPSAwLCB0Zl9lc2kgPSAwLCB0Zl9lYnAgPSAtOTM5NTgyMTE2LCANCiAgICAg IHRmX2lzcCA9IC05Mzk1ODIxNDQsIHRmX2VieCA9IDEwOCwgdGZfZWR4ID0gOCwgdGZfZWN4ID0g LTk0MDE3NDAxNiwgDQogICAgICB0Zl9lYXggPSA4LCB0Zl90cmFwbm8gPSAxMiwgdGZfZXJyID0g MiwgdGZfZWlwID0gLTEwNzE5MDU0MDksIHRmX2NzID0gOCwgDQogICAgICB0Zl9lZmxhZ3MgPSA2 NjExOCwgdGZfZXNwID0gMCwgdGZfc3MgPSAtMTA1NzUzMTM5Mn0pDQogICAgYXQgLi4vLi4vaTM4 Ni9pMzg2L3RyYXAuYzo0NDINCiMxMSAweGMwMWMwNTdmIGluIHZyZWYgKHZwPTB4MCkgYXQgbWFj aGluZS9hdG9taWMuaDozMzINCiMxMiAweGMwZjdhYTgyIGluID8/ICgpDQotLS1UeXBlIDxyZXR1 cm4+IHRvIGNvbnRpbnVlLCBvciBxIDxyZXR1cm4+IHRvIHF1aXQtLS0NCiMxMyAweGMwZjdiOTMz IGluID8/ICgpDQojMTQgMHhjMGY3ZGUxYyBpbiA/PyAoKQ0KIzE1IDB4YzBmN2FiYjUgaW4gPz8g KCkNCiMxNiAweGMwMWM4YWNjIGluIHZuX3JlYWQgKGZwPTB4YzEwNWU5YzAsIHVpbz0weGM3ZmYx ZWU0LCBjcmVkPTB4YzEwNDc2MDAsIA0KICAgIGZsYWdzPTAsIHA9MHhjN2Y2MTU0MCkgYXQgdm5v ZGVfaWYuaDoyNzkNCiMxNyAweGMwMTliOWJhIGluIGRvZmlsZXJlYWQgKHA9MHhjN2Y2MTU0MCwg ZnA9MHhjMTA1ZTljMCwgZmQ9OSwgDQogICAgYnVmPTB4ODIyM2MwMCwgbmJ5dGU9NTEyLCBvZmZz ZXQ9LTEsIGZsYWdzPTApIGF0IC4uLy4uL3N5cy9maWxlLmg6MTQxDQojMTggMHhjMDE5YjhjMiBp biByZWFkIChwPTB4YzdmNjE1NDAsIHVhcD0weGM3ZmYxZjgwKQ0KICAgIGF0IC4uLy4uL2tlcm4v c3lzX2dlbmVyaWMuYzoxMTgNCiMxOSAweGMwMjdmMTMxIGluIHN5c2NhbGwyIChmcmFtZT17dGZf ZnMgPSAtMTA3ODAwMTYxNywgdGZfZXMgPSAtMTA3ODAwMTYxNywgDQogICAgICB0Zl9kcyA9IC0x MDc4MDAxNjE3LCB0Zl9lZGkgPSA5LCB0Zl9lc2kgPSAwLCB0Zl9lYnAgPSAtMTA3OTE5ODExNiwg DQogICAgICB0Zl9pc3AgPSAtOTM5NTgxNDg0LCB0Zl9lYnggPSA2NzQ2ODQ4MTYsIHRmX2VkeCA9 IDEzNjQ3NjE2MCwgDQogICAgICB0Zl9lY3ggPSA2NzQ2NzY4MzIsIHRmX2VheCA9IDMsIHRmX3Ry YXBubyA9IDIyLCB0Zl9lcnIgPSAyLCANCiAgICAgIHRmX2VpcCA9IDY3NDM5NjQ0OCwgdGZfY3Mg PSAzMSwgdGZfZWZsYWdzID0gNjU5LCB0Zl9lc3AgPSAtMTA3OTE5ODE2MCwgDQogICAgICB0Zl9z cyA9IDQ3fSkgYXQgLi4vLi4vaTM4Ni9pMzg2L3RyYXAuYzoxMTUzDQojMjAgMHhjMDI3MzhlMyBp biBYaW50MHg4MF9zeXNjYWxsICgpDQojMjEgMHgyODM1ZGRmZSBpbiA/PyAoKQ0KIzIyIDB4Mjgz NGQ2NmUgaW4gPz8gKCkNCiMyMyAweDI4MzQ4YmY5IGluID8/ICgpDQojMjQgMHgyODViMDhkNiBp biA/PyAoKQ0KIzI1IDB4MCBpbiA/PyAoKQ0KKGtnZGIpIHVwIDEwDQojMTAgMHhjMDI3ZTEyYyBp biB0cmFwIChmcmFtZT17dGZfZnMgPSAtOTM5NTg5NjA4LCB0Zl9lcyA9IC0xMDcxOTcyMzM2LCAN CiAgICAgIHRmX2RzID0gLTkzOTc4NjIyNCwgdGZfZWRpID0gMCwgdGZfZXNpID0gMCwgdGZfZWJw ID0gLTkzOTU4MjExNiwgDQogICAgICB0Zl9pc3AgPSAtOTM5NTgyMTQ0LCB0Zl9lYnggPSAxMDgs IHRmX2VkeCA9IDgsIHRmX2VjeCA9IC05NDAxNzQwMTYsIA0KICAgICAgdGZfZWF4ID0gOCwgdGZf dHJhcG5vID0gMTIsIHRmX2VyciA9IDIsIHRmX2VpcCA9IC0xMDcxOTA1NDA5LCB0Zl9jcyA9IDgs IA0KICAgICAgdGZfZWZsYWdzID0gNjYxMTgsIHRmX2VzcCA9IDAsIHRmX3NzID0gLTEwNTc1MzEz OTJ9KQ0KICAgIGF0IC4uLy4uL2kzODYvaTM4Ni90cmFwLmM6NDQyDQo0NDIJCQkJKHZvaWQpIHRy YXBfcGZhdWx0KCZmcmFtZSwgRkFMU0UsIGV2YSk7DQooa2dkYikgZnJhbWUgZnJhbWUtPnRmX2Vi cCBmcmFtZS0+dGZfZWlwDQojMCAgMHhjMDFjMDU3ZiBpbiB2cmVmICh2cD0weDApIGF0IG1hY2hp bmUvYXRvbWljLmg6MzMyDQozMzIJCXJldHVybiAoYXRvbWljX2NtcHNldF9pbnQoKHZvbGF0aWxl IHVfaW50ICopZHN0LCAodV9pbnQpZXhwLA0KKGtnZGIpIGxpc3QNCjMyNwkjaWYgIWRlZmluZWQo V0FOVF9GVU5DVElPTlMpDQozMjgJc3RhdGljIF9faW5saW5lIGludA0KMzI5CWF0b21pY19jbXBz ZXRfcHRyKHZvbGF0aWxlIHZvaWQgKmRzdCwgdm9pZCAqZXhwLCB2b2lkICpzcmMpDQozMzAJew0K MzMxCQ0KMzMyCQlyZXR1cm4gKGF0b21pY19jbXBzZXRfaW50KCh2b2xhdGlsZSB1X2ludCAqKWRz dCwgKHVfaW50KWV4cCwNCjMzMwkJICAgICh1X2ludClzcmMpKTsNCjMzNAl9DQozMzUJDQozMzYJ c3RhdGljIF9faW5saW5lIHZvaWQgKg0KKGtnZGIpIHByaW50IGRzdA0KJDEgPSAodV9pbnQgKikg MHgyODM2ZGY5MA0KKGtnZGIpIHByaW50IGV4cA0KTm8gc3ltYm9sICJleHAiIGluIGN1cnJlbnQg Y29udGV4dC4NCihrZ2RiKSBwcmludCBzcmMNCiQyID0gMA0KKGtnZGIpIHVwDQojMSAgMHhjMGY3 YWE4MiBpbiA/PyAoKQ0KKGtnZGIpIHVwDQojMiAgMHhjMGY3YjkzMyBpbiA/PyAoKQ0KKGtnZGIp IHVwDQojMyAgMHhjMGY3ZGUxYyBpbiA/PyAoKQ0KKGtnZGIpIHVwDQojNCAgMHhjMGY3YWJiNSBp biA/PyAoKQ0KKGtnZGIpIHVwDQojNSAgMHhjMDFjOGFjYyBpbiB2bl9yZWFkIChmcD0weGMxMDVl OWMwLCB1aW89MHhjN2ZmMWVlNCwgY3JlZD0weGMxMDQ3NjAwLCANCiAgICBmbGFncz0wLCBwPTB4 YzdmNjE1NDApIGF0IHZub2RlX2lmLmg6Mjc5DQoyNzkJCXJjID0gVkNBTEwodnAsIFZPRkZTRVQo dm9wX3JlYWQpLCAmYSk7DQooa2dkYikgdXANCiM2ICAweGMwMTliOWJhIGluIGRvZmlsZXJlYWQg KHA9MHhjN2Y2MTU0MCwgZnA9MHhjMTA1ZTljMCwgZmQ9OSwgDQogICAgYnVmPTB4ODIyM2MwMCwg bmJ5dGU9NTEyLCBvZmZzZXQ9LTEsIGZsYWdzPTApIGF0IC4uLy4uL3N5cy9maWxlLmg6MTQxDQox NDEJCWVycm9yID0gKCpmcC0+Zl9vcHMtPmZvX3JlYWQpKGZwLCB1aW8sIGNyZWQsIGZsYWdzLCBw KTsNCihrZ2RiKSB1cA0KIzcgIDB4YzAxOWI4YzIgaW4gcmVhZCAocD0weGM3ZjYxNTQwLCB1YXA9 MHhjN2ZmMWY4MCkNCiAgICBhdCAuLi8uLi9rZXJuL3N5c19nZW5lcmljLmM6MTE4DQoxMTgJCWVy cm9yID0gZG9maWxlcmVhZChwLCBmcCwgdWFwLT5mZCwgdWFwLT5idWYsIHVhcC0+bmJ5dGUsIChv ZmZfdCktMSwgMCk7DQooa2dkYikgdXANCiM4ICAweGMwMjdmMTMxIGluIHN5c2NhbGwyIChmcmFt ZT17dGZfZnMgPSAtMTA3ODAwMTYxNywgdGZfZXMgPSAtMTA3ODAwMTYxNywgDQogICAgICB0Zl9k cyA9IC0xMDc4MDAxNjE3LCB0Zl9lZGkgPSA5LCB0Zl9lc2kgPSAwLCB0Zl9lYnAgPSAtMTA3OTE5 ODExNiwgDQogICAgICB0Zl9pc3AgPSAtOTM5NTgxNDg0LCB0Zl9lYnggPSA2NzQ2ODQ4MTYsIHRm X2VkeCA9IDEzNjQ3NjE2MCwgDQogICAgICB0Zl9lY3ggPSA2NzQ2NzY4MzIsIHRmX2VheCA9IDMs IHRmX3RyYXBubyA9IDIyLCB0Zl9lcnIgPSAyLCANCiAgICAgIHRmX2VpcCA9IDY3NDM5NjQ0OCwg dGZfY3MgPSAzMSwgdGZfZWZsYWdzID0gNjU5LCB0Zl9lc3AgPSAtMTA3OTE5ODE2MCwgDQogICAg ICB0Zl9zcyA9IDQ3fSkgYXQgLi4vLi4vaTM4Ni9pMzg2L3RyYXAuYzoxMTUzDQoxMTUzCQllcnJv ciA9ICgqY2FsbHAtPnN5X2NhbGwpKHAsIGFyZ3MpOw0KKGtnZGIpIHVwDQojOSAgMHhjMDI3Mzhl MyBpbiBYaW50MHg4MF9zeXNjYWxsICgpDQooa2dkYikgdXANCiMxMCAweDI4MzVkZGZlIGluID8/ ICgpDQooa2dkYikgdXANCiMxMSAweDI4MzRkNjZlIGluID8/ICgpDQooa2dkYikgdXANCiMxMiAw eDI4MzQ4YmY5IGluID8/ICgpDQooa2dkYikgdXANCiMxMyAweDI4NWIwOGQ2IGluID8/ICgpDQoo a2dkYikgdXANCiMxNCAweDAgaW4gPz8gKCkNCihrZ2RiKSB1cA0KSW5pdGlhbCBmcmFtZSBzZWxl Y3RlZDsgeW91IGNhbm5vdCBnbyB1cC4NCihrZ2RiKSBxdWl0DQpbIHJvb3RAOi91c3Ivc3JjL3N5 cy9jb21waWxlL1ZFTlVTIF0gIyBleGl0DQpleGl0DQoKU2NyaXB0IGRvbmUgb24gVGh1IEphbiAx OCAxNjoxNjozNSAyMDAxCg== --=====================_189762640==_ Content-Type: application/octet-stream; name="Venus" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Venus" bWFjaGluZQkJaTM4NgppZGVudAkJVkVOVVMKbWF4dXNlcnMJMzIKI21ha2VvcHRpb25zCUNPTkZf Q0ZMQUdTPSItZm5vLWJ1aWx0aW4gLW1jcHU9cGVudGl1bXBybyAtbWFyY2g9cGVudGl1bXBybyIK bWFrZW9wdGlvbnMJQ09ORl9DRkxBR1M9Ii1PIC1waXBlIgpvcHRpb25zIAlCTEtERVZfSU9TSVpF PTgxOTIKb3B0aW9ucyAJUFFfTk9PUFQKb3B0aW9ucyAJSU5DTFVERV9DT05GSUdfRklMRSAgICAg CmNwdQkJSTY4Nl9DUFUJCQpvcHRpb25zIAlOT19GMDBGX0hBQ0sJCQpvcHRpb25zIAlDT01QQVRf NDMKb3B0aW9ucyAJVVNFUl9MRFQJCQpvcHRpb25zIAlTWVNWU0hNCm9wdGlvbnMgCVNZU1ZTRU0K b3B0aW9ucyAJU1lTVk1TRwpvcHRpb25zIAlVQ09OU09MRQpvcHRpb25zIAlVU0VSQ09ORklHCQkK b3B0aW9ucyAJVklTVUFMX1VTRVJDT05GSUcJCm9wdGlvbnMgCUlORVQJCQkKb3B0aW9ucyAJSU5F VDYJCQkKb3B0aW9ucyAJSVBTRUMJCQkKb3B0aW9ucyAJSVBTRUNfRVNQCQkKb3B0aW9ucwkJTkVU R1JBUEgKZGV2aWNlCQlldGhlcgkJCQpkZXZpY2UJCXZsYW4JCQkKZGV2aWNlCQlsb29wCTEJCQpk ZXZpY2UJCWJwZgkJCQojZGV2aWNlCQl0YXAJCQkKI2RldmljZQkJdHVuCQkJCmRldmljZQkJZ2lm CQkJCmRldmljZQkJZmFpdGgJCQkKZGV2aWNlCQlzdGYJCQkKb3B0aW9ucyAJSVBGSVJFV0FMTAkJ Cm9wdGlvbnMgCUlQRklSRVdBTExfVkVSQk9TRQkKb3B0aW9ucyAJSVBGSVJFV0FMTF9GT1JXQVJE CQpvcHRpb25zIAlJUFY2RklSRVdBTEwJCQpvcHRpb25zIAlJUFY2RklSRVdBTExfVkVSQk9TRQpv cHRpb25zIAlJUERJVkVSVAkJCm9wdGlvbnMgCUlQU1RFQUxUSAkJCm9wdGlvbnMgCVRDUF9EUk9Q X1NZTkZJTgkJCm9wdGlvbnMgCVRDUF9SRVNUUklDVF9SU1QJCm9wdGlvbnMgCURVTU1ZTkVUCm9w dGlvbnMgCUJSSURHRQpvcHRpb25zIAlGRlMJCQkKb3B0aW9ucwkJREVWRlMKb3B0aW9ucyAJRkZT X1JPT1QJCQpvcHRpb25zCUZGU19FWFRBVFRSCm9wdGlvbnMgCUVOQUJMRV9WRlNfSU9PUFQKZGV2 aWNlCQlyYW5kb20Kb3B0aW9ucyAJUDEwMDNfMUIKb3B0aW9ucyAJX0tQT1NJWF9QUklPUklUWV9T Q0hFRFVMSU5HCm9wdGlvbnMgCV9LUE9TSVhfVkVSU0lPTj0xOTkzMDlMCm9wdGlvbnMgCUhaPTEw MApkZXZpY2UJCXB0eQkJCiNkZXZpY2UJCXZuCQkKb3B0aW9ucyAJTVNHQlVGX1NJWkU9NDA5NjAK ZGV2aWNlCQlpc2EKI29wdGlvbnMgCUNPTVBBVF9PTERJU0EJCm9wdGlvbnMgCUFVVE9fRU9JXzEK b3B0aW9ucyAJTUFYTUVNPSIoMTI4KjEwMjQpIgojb3B0aW9ucyAJTlRJTUVDT1VOVEVSPTIwCmRl dmljZQkJcGNpCiNvcHRpb25zIAlDT01QQVRfT0xEUENJCQpkZXZpY2UJCWF0a2JkYwkxCmRldmlj ZQkJYXRrYmQKZGV2aWNlCQlwc20Kb3B0aW9ucyAJUFNNX0hPT0tSRVNVTUUJCQpvcHRpb25zIAlQ U01fUkVTRVRBRlRFUlNVU1BFTkQJCmRldmljZQkJdmdhCm9wdGlvbnMgCVZHQV9BTFRfU0VRQUND RVNTCm9wdGlvbnMgCVZHQV9TTE9XX0lPQUNDRVNTCQpkZXZpY2UJCXNwbGFzaApkZXZpY2UJCXNj CTEKb3B0aW9ucyAJTUFYQ09OUz0xMgkJCmRldmljZQkJbnB4CmRldmljZQkJYXRhCmRldmljZQkJ YXRhZGlzawkJCmRldmljZQkJYXRhcGljZAkJCm9wdGlvbnMJCVNPRlRVUERBVEVTCm9wdGlvbnMg CUFUQV9TVEFUSUNfSUQKb3B0aW9ucyAJQVRBX0VOQUJMRV9BVEFQSV9ETUEKb3B0aW9ucyAJQVRB X0VOQUJMRV9UQUdTCmRldmljZQkJZmRjCmRldmljZQkJc2lvCmRldmljZQkJeGUKI2RldmljZQkJ cGNtCmRldmljZQkJbWlkaQojZGV2aWNlCQlzZXEKI2RldmljZQkJc2JjCmRldmljZQkJYXBtCmRl dmljZQkJcG10aW1lcgkJCQojYm90aCBORVdDQVJEIGFuZCBPTERDQVJECmRldmljZQkJcGNpYwoj anVzdCBPTERDQVJECmRldmljZQkJY2FyZAojanVzdCBORVdDQVJECiNkZXZpY2UJCXBjY2FyZAoj ZGV2aWNlCQljYXJkYnVzCiNkZXZpY2UJCXBjY2JiCiNyZXN1bWUgbm9ybWFsIHNjaHR1ZmYKb3B0 aW9ucyAJUENJQ19SRVNVTUVfUkVTRVQJCm9wdGlvbnMgCVBPV0VSRkFJTF9OTUkJCiNkZXZpY2UJ CXNtYnVzCQkKI2RldmljZQkJaW50cG0KI2RldmljZQkJaWNoc21iCiNkZXZpY2UJCXNtYgojZGV2 aWNlCQlpaWNidXMJCQojZGV2aWNlCQlpaWNiYgojZGV2aWNlCQlpYwojZGV2aWNlCQlpaWMKI2Rl dmljZQkJaWljc21iCQkKI2RldmljZQkJcGNmCm9wdGlvbnMJCVBQQ19QUk9CRV9DSElQU0VUIApv cHRpb25zIAlET05UUFJPQkVfMTI4NAkKZGV2aWNlCQlwcGMKZGV2aWNlCQlwcGJ1cwpkZXZpY2UJ CWxwdAojZGV2aWNlCQl1aGNpCiNkZXZpY2UJCXVzYgojZGV2aWNlCQl1ZGJwCiNkZXZpY2UJCXVn ZW4KI2RldmljZQkJdWhpZAojZGV2aWNlCQl1a2JkCiNkZXZpY2UJCXVscHQKI2RldmljZQkJdW1h c3MKI2RldmljZQkJdW1vZGVtCiNkZXZpY2UJCXVtcwojZGV2aWNlCQl1cmlvCiNkZXZpY2UJCWF1 ZQojZGV2aWNlCQljdWUKI2RldmljZQkJa3VlCmRldmljZSAgICAgICAgICBhY3BpY2EKI29wdGlv bnMgICAgICAgICBBQ1BJX0RFQlVHCm9wdGlvbnMJCURJQUdOT1NUSUMKb3B0aW9ucyAgICAgICAg IE1VVEVYX0RFQlVHCm9wdGlvbnMgICAgICAgICBXSVRORVNTCm9wdGlvbnMgICAgICAgICBXSVRO RVNTX0REQgojb3B0aW9ucyAgICAgICAgIFdJVE5FU1NfU0tJUFNQSU4Kb3B0aW9ucyAgICAgICAg IEREQiAgIAoK --=====================_189762640==_ Content-Type: application/octet-stream; name="dmesg" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="dmesg" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDEgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChj KSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAx OTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln aHRzIHJlc2VydmVkLgpGcmVlQlNEIDUuMC1DVVJSRU5UICMxOiBUaHUgSmFuIDE4IDEzOjU4OjI3 IENFVCAyMDAxCiAgICByb290QHZlbnVzLmRyd2lsY28ubmV0Oi91c3Ivc3JjL3N5cy9jb21waWxl L1ZFTlVTClRpbWVjb3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkzMTgyIEh6CkNQVTogUGVu dGl1bSBJSS9QZW50aXVtIElJIFhlb24vQ2VsZXJvbiAoMjMzLjI5LU1IeiA2ODYtY2xhc3MgQ1BV KQogIE9yaWdpbiA9ICJHZW51aW5lSW50ZWwiICBJZCA9IDB4NjUyICBTdGVwcGluZyA9IDIKICBG ZWF0dXJlcz0weDE4M2Y5ZmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixQQUUsTUNFLENYOCxTRVAs TVRSUixQR0UsTUNBLENNT1YsUEFULFBTRTM2LE1NWCxGWFNSPgpyZWFsIG1lbW9yeSAgPSAxMzQy MTc3MjggKDEzMTA3MksgYnl0ZXMpCmF2YWlsIG1lbW9yeSA9IDEyNTYxMjAzMiAoMTIyNjY4SyBi eXRlcykKUHJlbG9hZGVkIGVsZiBrZXJuZWwgImtlcm5lbCIgYXQgMHhjMDRlNjAwMC4KUHJlbG9h ZGVkIGVsZiBtb2R1bGUgInNwbGFzaF9ibXAua28iIGF0IDB4YzA0ZTYwOWMuClByZWxvYWRlZCBl bGYgbW9kdWxlICJ2ZXNhLmtvIiBhdCAweGMwNGU2MTQwLgpQcmVsb2FkZWQgc3BsYXNoX2ltYWdl X2RhdGEgIi9ib290L21vZHVsZXMvc2F0dXJuODAwLmJtcCIgYXQgMHhjMDRlNjFkYy4KUHJlbG9h ZGVkIGVsZiBtb2R1bGUgInVtcy5rbyIgYXQgMHhjMDRlNjIzNC4KUHJlbG9hZGVkIGVsZiBtb2R1 bGUgInVzYi5rbyIgYXQgMHhjMDRlNjJkMC4KUHJlbG9hZGVkIGVsZiBtb2R1bGUgInNuZF9kcml2 ZXIua28iIGF0IDB4YzA0ZTYzNmMuClByZWxvYWRlZCBlbGYgbW9kdWxlICJzbmRfdmlhODJjNjg2 LmtvIiBhdCAweGMwNGU2NDEwLgpQcmVsb2FkZWQgZWxmIG1vZHVsZSAic25kX3BjbS5rbyIgYXQg MHhjMDRlNjRiOC4KUHJlbG9hZGVkIGVsZiBtb2R1bGUgInNuZF90NGR3YXZlLmtvIiBhdCAweGMw NGU2NTU4LgpQcmVsb2FkZWQgZWxmIG1vZHVsZSAic25kX3NvbG8ua28iIGF0IDB4YzA0ZTY1ZmMu ClByZWxvYWRlZCBlbGYgbW9kdWxlICJzbmRfc2JjLmtvIiBhdCAweGMwNGU2NjljLgpQcmVsb2Fk ZWQgZWxmIG1vZHVsZSAic25kX3NiMTYua28iIGF0IDB4YzA0ZTY3M2MuClByZWxvYWRlZCBlbGYg bW9kdWxlICJzbmRfc2I4LmtvIiBhdCAweGMwNGU2N2RjLgpQcmVsb2FkZWQgZWxmIG1vZHVsZSAi c25kX25lb21hZ2ljLmtvIiBhdCAweGMwNGU2ODdjLgpQcmVsb2FkZWQgZWxmIG1vZHVsZSAic25k X21zcy5rbyIgYXQgMHhjMDRlNjkyMC4KUHJlbG9hZGVkIGVsZiBtb2R1bGUgInNuZF9tYWVzdHJv LmtvIiBhdCAweGMwNGU2OWMwLgpQcmVsb2FkZWQgZWxmIG1vZHVsZSAic25kX2d1c2Mua28iIGF0 IDB4YzA0ZTZhNjQuClByZWxvYWRlZCBlbGYgbW9kdWxlICJzbmRfZXNzLmtvIiBhdCAweGMwNGU2 YjA0LgpQcmVsb2FkZWQgZWxmIG1vZHVsZSAic25kX2VzMTg4OC5rbyIgYXQgMHhjMDRlNmJhNC4K UHJlbG9hZGVkIGVsZiBtb2R1bGUgInNuZF9lczEzN3gua28iIGF0IDB4YzA0ZTZjNDguClByZWxv YWRlZCBlbGYgbW9kdWxlICJzbmRfZW11MTBrMS5rbyIgYXQgMHhjMDRlNmNlYy4KUHJlbG9hZGVk IGVsZiBtb2R1bGUgInNuZF9kczEua28iIGF0IDB4YzA0ZTZkOTAuClByZWxvYWRlZCBlbGYgbW9k dWxlICJzbmRfY3NhcGNtLmtvIiBhdCAweGMwNGU2ZTMwLgpQcmVsb2FkZWQgZWxmIG1vZHVsZSAi c25kX2NzYS5rbyIgYXQgMHhjMDRlNmVkNC4KUHJlbG9hZGVkIGVsZiBtb2R1bGUgInNuZF9hZDE4 MTYua28iIGF0IDB4YzA0ZTZmNzQuCktMRCBmaWxlIHNuZF9kcml2ZXIua28gaXMgbWlzc2luZyBk ZXBlbmRlbmNpZXMKUGVudGl1bSBQcm8gTVRSUiBzdXBwb3J0IGVuYWJsZWQKVkVTQTogdjIuMCwg MjQ5NmsgbWVtb3J5LCBmbGFnczoweDAsIG1vZGUgdGFibGU6MHhjMDNiODJlMiAoMTAwMDAyMikK VkVTQTogTWFnaWNHcmFwaCAyNTYgQVYgNDRLIFBSRUxJTUlOQVJZCiAgICBBQ1BJLTAyOTk6ICoq KiBXYXJuaW5nOiBJbnZhbGlkIHRhYmxlIHNpZ25hdHVyZSBmb3VuZAogICAgQUNQSS0wMTcwOiAq KiogRXJyb3I6IEFjcGlMb2FkVGFibGVzOiBDb3VsZCBub3QgbG9hZCBSU0RUOiBBRV9CQURfU0lH TkFUVVJFCiAgICBBQ1BJLTAyMDI6ICoqKiBFcnJvcjogQWNwaUxvYWRUYWJsZXM6IENvdWxkIG5v dCBsb2FkIHRhYmxlczogQUVfQkFEX1NJR05BVFVSRQpBQ1BJOiB0YWJsZSBsb2FkIGZhaWxlZDog QUVfQkFEX1NJR05BVFVSRQpVc2luZyAkUElSIHRhYmxlLCA2IGVudHJpZXMgYXQgMHhjMDBmMGY4 MAphcG0wOiA8QVBNIEJJT1M+IG9uIG1vdGhlcmJvYXJkCmFwbTA6IGZvdW5kIEFQTSBCSU9TIHYx LjIsIGNvbm5lY3RlZCBhdCB2MS4yCm5weDA6IDxtYXRoIHByb2Nlc3Nvcj4gb24gbW90aGVyYm9h cmQKbnB4MDogSU5UIDE2IGludGVyZmFjZQpwY2liMDogPEludGVsIDgyNDQzQlggaG9zdCB0byBQ Q0kgYnJpZGdlIChBR1AgZGlzYWJsZWQpPiBhdCBwY2lidXMgMCBvbiBtb3RoZXJib2FyZApwY2kw OiA8UENJIGJ1cz4gb24gcGNpYjAKcGNpMDogPGRpc3BsYXksIFZHQT4gYXQgNC4wIChubyBkcml2 ZXIgYXR0YWNoZWQpCmlzYWIwOiA8UENJLUlTQSBicmlkZ2U+IGF0IGRldmljZSA1LjAgb24gcGNp MAppc2EwOiA8SVNBIGJ1cz4gb24gaXNhYjAKYXRhcGNpMDogPEludGVsIFBJSVg0IEFUQTMzIGNv bnRyb2xsZXI+IHBvcnQgMHhmZTYwLTB4ZmU2ZiBhdCBkZXZpY2UgNS4xIG9uIHBjaTAKYXRhMDog YXQgMHgxZjAgaXJxIDE0IG9uIGF0YXBjaTAKYXRhMTogYXQgMHgxNzAgaXJxIDE1IG9uIGF0YXBj aTAKdWhjaTA6IDxJbnRlbCA4MjM3MUFCL0VCIChQSUlYNCkgVVNCIGNvbnRyb2xsZXI+IHBvcnQg MHhmZmUwLTB4ZmZmZiBpcnEgMTEgYXQgZGV2aWNlIDUuMiBvbiBwY2kwCnVzYjA6IDxJbnRlbCA4 MjM3MUFCL0VCIChQSUlYNCkgVVNCIGNvbnRyb2xsZXI+IG9uIHVoY2kwCnVzYjA6IFVTQiByZXZp c2lvbiAxLjAKdWh1YjA6IEludGVsIFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAv MS4wMCwgYWRkciAxCnVodWIwOiAyIHBvcnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJl ZAp1bXMwOiBMb2dpdGVjaCBVU0IgTW91c2UsIHJldiAxLjEwLzYuMTAsIGFkZHIgMiwgaWNsYXNz IDMvMQp1bXMwOiA0IGJ1dHRvbnMgYW5kIFogZGlyLgpwY2kwOiA8YnJpZGdlLCBQQ0ktdW5rbm93 bj4gYXQgNS4zIChubyBkcml2ZXIgYXR0YWNoZWQpCnBjaTA6IDxzaW1wbGUgY29tbXM+IGF0IDku MCAobm8gZHJpdmVyIGF0dGFjaGVkKQpwY2ljLXBjaTA6IDxUb3NoaWJhIFRvUElDOTcgUENJLUNh cmRCdXMgQnJpZGdlPiBhdCBkZXZpY2UgMTEuMCBvbiBwY2kwCnBjaWMtcGNpMTogPFRvc2hpYmEg VG9QSUM5NyBQQ0ktQ2FyZEJ1cyBCcmlkZ2U+IGF0IGRldmljZSAxMS4xIG9uIHBjaTAKYXRrYmRj MDogPEtleWJvYXJkIGNvbnRyb2xsZXIgKGk4MDQyKT4gYXQgcG9ydCAweDYwLDB4NjQgb24gaXNh MAphdGtiZDA6IDxBVCBLZXlib2FyZD4gZmxhZ3MgMHgxIGlycSAxIG9uIGF0a2JkYzAKcHNtMDog PFBTLzIgTW91c2U+IGlycSAxMiBvbiBhdGtiZGMwCnBzbTA6IG1vZGVsIEdsaWRlUG9pbnQsIGRl dmljZSBJRCAwCmZkYzA6IDxORUMgNzY1IG9yIGNsb25lPiBhdCBwb3J0IDB4M2YwLTB4M2Y1LDB4 M2Y3IGlycSA2IGRycSAyIG9uIGlzYTAKcGNpYzA6IDxJbnRlbCBpODIzNjU+IGF0IHBvcnQgMHgz ZTAgaW9tZW0gMHhkMDAwMCBvbiBpc2EwCnBjaWMwOiBQb2xsaW5nIG1vZGUKcGNjYXJkMDogPFBD IENhcmQgYnVzIC0tIGtsdWRnZSB2ZXJzaW9uPiBvbiBwY2ljMApwY2NhcmQxOiA8UEMgQ2FyZCBi dXMgLS0ga2x1ZGdlIHZlcnNpb24+IG9uIHBjaWMwCnBjbTA6IDxPUEwzLVNBeCAoWU1GNzE5KT4g YXQgcG9ydCAweDUzMC0weDUzNywweDUzOC0weDUzOSBpcnEgNSBkcnEgMSBmbGFncyAweGMxMTAg b24gaXNhMApwbXRpbWVyMCBvbiBpc2EwCnBwYzA6IDxQYXJhbGxlbCBwb3J0PiBhdCBwb3J0IDB4 Mzc4LTB4MzdmIGlycSA3IGRycSAzIG9uIGlzYTAKcHBjMDogR2VuZXJpYyBjaGlwc2V0IChFQ1Av UFMyL05JQkJMRSkgaW4gQ09NUEFUSUJMRSBtb2RlCnBwYzA6IEZJRk8gd2l0aCAxNi8xNi8xNiBi eXRlcyB0aHJlc2hvbGQKbHB0MDogPFByaW50ZXI+IG9uIHBwYnVzMApscHQwOiBJbnRlcnJ1cHQt ZHJpdmVuIHBvcnQKc2JjMDogPFNvdW5kQmxhc3RlciBQcm8+IGF0IHBvcnQgMHgyMjAtMHgyMmYg aXJxIDUgZHJxIDAgb24gaXNhMApzYmMwOiBhbGxvY19yZXNvdXJjZQpkZXZpY2VfcHJvYmVfYW5k X2F0dGFjaDogc2JjMCBhdHRhY2ggcmV0dXJuZWQgNgpzYzA6IDxTeXN0ZW0gY29uc29sZT4gYXQg ZmxhZ3MgMHgxMDAgb24gaXNhMApzYzA6IFZHQSA8MTIgdmlydHVhbCBjb25zb2xlcywgZmxhZ3M9 MHgzMDA+CnNpbzAgYXQgcG9ydCAweDNmOC0weDNmZiBpcnEgNCBmbGFncyAweDEwIG9uIGlzYTAK c2lvMDogdHlwZSAxNjU1MEEKdmdhMDogPEdlbmVyaWMgSVNBIFZHQT4gYXQgcG9ydCAweDNjMC0w eDNkZiBpb21lbSAweGEwMDAwLTB4YmZmZmYgb24gaXNhMApEVU1NWU5FVCBpbml0aWFsaXplZCAo MDEwMTE2KQpJUHY2IHBhY2tldCBmaWx0ZXJpbmcgaW5pdGlhbGl6ZWQsIHVubGltaXRlZCBsb2dn aW5nCklQIHBhY2tldCBmaWx0ZXJpbmcgaW5pdGlhbGl6ZWQsIGRpdmVydCBlbmFibGVkLCBydWxl LWJhc2VkIGZvcndhcmRpbmcgZW5hYmxlZCwgZGVmYXVsdCB0byBkZW55LCB1bmxpbWl0ZWQgbG9n Z2luZwpCUklER0UgOTkwODEwLCBoYXZlIDUgaW50ZXJmYWNlcwpJUHNlYzogSW5pdGlhbGl6ZWQg U2VjdXJpdHkgQXNzb2NpYXRpb24gUHJvY2Vzc2luZy4KcGNjYXJkOiBjYXJkIGluc2VydGVkLCBz bG90IDAKYXRhMS1zbGF2ZTogYXRhX2NvbW1hbmQ6IHRpbWVvdXQgd2FpdGluZyBmb3IgaW50cgph dGExLXNsYXZlOiBpZGVudGlmeSBmYWlsZWQKYWQwOiA0MTI2TUIgPFRPU0hJQkEgTUs0MzEwTUFU PiBbODk0NC8xNS82M10gYXQgYXRhMC1tYXN0ZXIgVURNQTMzCmFjZDA6IENEUk9NIDxDRC0yMjRF PiBhdCBhdGExLW1hc3RlciB1c2luZyBXRE1BMgpNb3VudGluZyByb290IGZyb20gdWZzOi9kZXYv YWQwczJhCnBpZCAyNjEgKGxkY29uZmlnKSwgdWlkIDA6IGV4aXRlZCBvbiBzaWduYWwgMTEgKGNv cmUgZHVtcGVkKQp4ZTAgYXQgcG9ydCAweDJlOC0weDJlZiBpb21lbSAweGQwMDAwLTB4ZDBmZmYg aXJxIDEwIHNsb3QgMCBvbiBwY2NhcmQwCnhlMDogWGlyY29tIENFTTU2LCBib25kaW5nIHZlcnNp b24gMHg1NSwgMTAwTWJwcyBjYXBhYmxlLCB3aXRoIG1vZGVtCnhlMDogRGluZ29JRCA9IDB4NDQ0 YiwgUmV2aXNpb25JRCA9IDB4MSwgVmVuZG9ySUQgPSAwCnhlMDogRXRoZXJuZXQgYWRkcmVzcyAw MDoxMDphNDpiNDplNDpiNQpCUklER0UgOTkwODEwLCBoYXZlIDYgaW50ZXJmYWNlcwotLSBpbmRl eCA2ICB0eXBlIDYgcGh5IDAgYWRkcmwgNiBhZGRyIDAwLjEwLmE0LmI0LmU0LmI1CnhlMDogd2F0 Y2hkb2cgdGltZW91dDsgcmVzZXR0aW5nIGNhcmQK --=====================_189762640==_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 6:49:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from tfrsolcom.transfer-solutions.com (mail.transfer-solutions.com [195.109.218.250]) by hub.freebsd.org (Postfix) with ESMTP id A60F637B400 for ; Thu, 18 Jan 2001 06:49:19 -0800 (PST) Received: by mail.transfer-solutions.com with Internet Mail Service (5.5.2650.21) id ; Thu, 18 Jan 2001 15:43:33 +0100 Received: from tfrsolcom.transfer-solutions.com (localhost [127.0.0.1]) by tfrsolcom.transfer-solutions.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id DAATSSJY; Thu, 18 Jan 2001 15:43:28 +0100 Received: from 193.100.100.198 by tfrsolcom.transfer-solutions.com (InterScan E-Mail VirusWall NT); Thu, 18 Jan 2001 15:43:28 +0100 (Romance Standard Time) From: Rogier Mulhuijzen To: freebsd-current@freebsd.org Message-Id: <5.0.2.1.0.20010118154821.00a60d80@tfrsolcom> X-Sender: rmulhuij@tfrsolcom X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Thu, 18 Jan 2001 15:54:49 +0100 Subject: ACPI problem? 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 After enabling ACPI in my kernel I get these messages in dmesg: ---snip--- VESA: v2.0, 2496k memory, flags:0x0, mode table:0xc03b82e2 (1000022) VESA: MagicGraph 256 AV 44K PRELIMINARY ACPI-0299: *** Warning: Invalid table signature found ACPI-0170: *** Error: AcpiLoadTables: Could not load RSDT: AE_BAD_SIGNATURE ACPI-0202: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATURE ACPI: table load failed: AE_BAD_SIGNATURE Using $PIR table, 6 entries at 0xc00f0f80 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 ---snip--- (Of course the VESA and apm messages were there before...) I have a Toshiba Tecra8000 as hardware and acpidump gives me: ---snip--- RSD PTR: Checksum=18, OEMID=TOSHIB, RsdtAddress=0x07ff0000 acpidump: RSDT is corrupted ---snip--- Drop me a line if you want me to dig deeper at stuff. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 7: 5:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id C394337B402 for ; Thu, 18 Jan 2001 07:05:32 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.11.1/8.11.1) id f0IF1PK50877; Thu, 18 Jan 2001 10:01:25 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200101181501.f0IF1PK50877@hda.hda.com> Subject: Re: HEADS UP: I386_CPU In-Reply-To: from Dag-Erling Smorgrav at "Jan 18, 2001 03:17:28 pm" To: Dag-Erling Smorgrav Date: Thu, 18 Jan 2001 10:01:25 -0500 (EST) Cc: Will Andrews , Warner Losh , FreeBSD Current 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 > Will Andrews writes: > > Well, Warner, I've never done embedded systems. So, tell me, do they > > actually use any C++ code in embedded systems? C++ has a rather high > > overhead as far as disk space & memory goes. > > That's a myth. > > > I would imagine that 99%+ > > of embedded systems do not use C++ code except perhaps for a very small > > amount of the code. > > >From experience, I would imagine the reverse. OK, I'll pipe up. 1. I can't agree with you about the reverse, that 99% is C++ and 1% C, much more can and should be done in C++, and 2. When you know what you're doing there is no additional overhead in time and space using C++ versus C. Also, you won't be screwing around creating large amounts of messy "class code" housekeeping in C. I think the kernel could benefit from restricted C++ support. However, 3. Far too many people don't know at all what they're doing. One of the first things I noticed on a recent project was I couldn't compile and run it in simulation without running out of swap because objects representing the system memory map were being accidentally created but not referenced. C is much more forgiving of ignorance. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 7:26:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E62AF37B402; Thu, 18 Jan 2001 07:26:00 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id QAA21260; Thu, 18 Jan 2001 16:25:52 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101181525.QAA21260@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <200101181205.f0IC5rK13062@mobile.wemm.org> from Peter Wemm at "Jan 18, 2001 04:05:53 am" To: peter@netplex.com.au (Peter Wemm) Date: Thu, 18 Jan 2001 16:25:52 +0100 (CET) Cc: jhb@FreeBSD.ORG (John Baldwin), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com 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 Peter Wemm wrote: > > Soren, can you retest a buildworld with the currently committed kernel > with no other changes? Let us see if the forward_signal() stuff is the > culprit, and if not, try adding just the i386/i386/machdep.c patch to HLT > the idle CPU. (if *that* makes a difference then we have got trouble!) It seems that the HLT thing is exactly the patch that makes it work! So we have trouble, I said that all along .5 :) -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 18 9:58:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id A94F437B400 for ; Thu, 18 Jan 2001 09:58:28 -0800 (PST) Received: from timbuktu-50.budapest.interware.hu ([195.70.51.242] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14JJKD-0004rK-00; Thu, 18 Jan 2001 18:58:17 +0100 Message-ID: <3A67131B.8C50EE00@elischer.org> Date: Thu, 18 Jan 2001 08:00:27 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Tor.Egge@fast.no Cc: sos@freebsd.dk, jasone@canonware.com, current@FreeBSD.ORG Subject: Re: Debugging SMP instability (was Re: HEADS-UP: await/asleep removal imminent) References: <200101171935.UAA25627@freebsd.dk> <200101180602.HAA11429@midten.fast.no> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tor.Egge@fast.no wrote: > > > Again I'll offer to run any and all code or patches to -current you > > guys can come up with, but I simply dont have the time to sit down > > and analyze into details what you have been doing... > > The enclosed patch implements a virtual NMI pushbutton by programming > the IOAPIC to deliver an NMI when sio1 generates an interrupt. > > DDB should be defined in the kernel config file. > > getty should not run on ttyd1 when this patch is applied. > > A serial console on sio0 is recommended. > > If you still cannot break into the kernel debugger when the machine > locks up then a rogue device is probably blocking the system > (or the debugger is trying to obtain a mutex held by somebody else) > > - Tor Egge cool. What are the instructions for using this? should something have sio1 open? can a paperclip be used to generat the interupt by connecting pins 2 and 3? etc. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 10:13:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id 25E0D37B401 for ; Thu, 18 Jan 2001 10:13:30 -0800 (PST) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id TAA43871; Thu, 18 Jan 2001 19:12:00 +0100 (CET) Message-Id: <200101181812.TAA43871@midten.fast.no> To: julian@elischer.org Cc: sos@freebsd.dk, jasone@canonware.com, current@FreeBSD.ORG Subject: Re: Debugging SMP instability (was Re: HEADS-UP: await/asleep removal imminent) From: Tor.Egge@fast.no In-Reply-To: Your message of "Thu, 18 Jan 2001 08:00:27 -0800" References: <3A67131B.8C50EE00@elischer.org> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 18 Jan 2001 19:11:59 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > cool. > What are the instructions for using this? > should something have sio1 open? I use conserver conserver conserver host null-modem serial cables test machine label test port AA ------------------------- sio0 serial console testnmi port BB ------------------------- sio1 NMI I start two conserver sessions, one using test (for the console access) and one using port testnmi (for NMI). When I need an NMI, I just press return or space in the session using port BB. This only works when the test machine runs an SMP kernel with DDB and the virtual NMI pushbutton patch. No programs on the test machine should open sio1, since that could cause interrupts (which are now NMIs). > can a paperclip be used to generat the interupt by connecting pins 2 and 3? I haven't tried that. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 10:25:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 4F04737B400; Thu, 18 Jan 2001 10:25:06 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0IISFs68402; Thu, 18 Jan 2001 10:28:15 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101180957.KAA33489@freebsd.dk> Date: Thu, 18 Jan 2001 10:24:08 -0800 (PST) From: John Baldwin To: Soren Schmidt Subject: Re: HEADS-UP: await/asleep removal imminent Cc: rjesup@wgate.com, arch@FreeBSD.org, current@FreeBSD.org, (Alfred Perlstein) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jan-01 Soren Schmidt wrote: > It seems Soren Schmidt wrote: >> > I actually used this: >> > >> > CFLAGS ?= -O -pipe -mcpu=i686 -march=i686 >> > COPTFLAGS ?= -O -pipe -mcpu=i686 -march=i686 >> > >> > All the diffs in sys/ on the box I built this kernel on are at >> > http://www.FreeBSD.org/~jhb/patches/sys-mutex.patch. One possibly notable >> > patch I had forgotten about is the fix to forward_signal() to lock with >> > sched_lock. I've just committed that though. >> >> OK, I have installed those patches and will try out a kernel build on >> that asap.... > > Hmm, now we are getting somewhere, it ran through a make world with > that patch installed! > > I'll test some more, maybe you should get it all committed it seems to > make a hell of a difference.... The refcount.h stuff isn't used anywhere, and is still in a bikeshed mode. The rest of the patches are a bogus SMP HLT implementation that isnt' done yet, some proc lock fixes in svr4, some weird kernel printf patch I got from someone else at some point in time, and the forward_signal() patch I committed. > -Søren -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 10:26: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 58FF137B401; Thu, 18 Jan 2001 10:25:35 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0IISFs68406; Thu, 18 Jan 2001 10:28:15 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101181408.PAA00170@freebsd.dk> Date: Thu, 18 Jan 2001 10:24:09 -0800 (PST) From: John Baldwin To: Soren Schmidt Subject: Re: HEADS-UP: await/asleep removal imminent Cc: rjesup@wgate.com, arch@FreeBSD.org, current@FreeBSD.org, (Alfred Perlstein) , (Peter Wemm) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jan-01 Soren Schmidt wrote: > It seems Peter Wemm wrote: >> > I'll try adding the forward_signal stuff see if that helps... >> >> But John committed that! it should be in the fresh checkout you tried >> above.... Of course, that is assuming you cvsup'ed very recently.. > > Sorry that was not what I meant, I meant this patch to machdep.c > and so far it looks as thats the culprit it hasn't locked up yet > at least, but its not finished a world yet.... > > Index: machdep.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v > retrieving revision 1.429 > diff -u -r1.429 machdep.c > --- machdep.c 2001/01/16 09:10:33 1.429 > +++ machdep.c 2001/01/18 13:44:48 > @@ -1005,6 +1005,10 @@ > void > cpu_idle(void) > { > +#ifdef SMP > + /* first candidate for an interrupt */ > + lapic.tpr = 0; > +#endif > #ifndef SMP > if (cpu_idle_hlt) { > disable_intr(); Hmmmmmmmmmmmmmmmmmm. Since cpl is dead, this is supposed to be a nop, since the tpr is always at 0 now (AFAIK). I'll look at this today. Weird. Peter? > -Søren -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 10:31:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 6AAC237B401; Thu, 18 Jan 2001 10:31:15 -0800 (PST) Received: from marakesh-16.budapest.interware.hu ([195.70.50.144] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14JJq1-0008E5-00; Thu, 18 Jan 2001 19:31:09 +0100 Message-ID: <3A6732EF.C83945CA@elischer.org> Date: Thu, 18 Jan 2001 10:16:15 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Soren Schmidt Cc: Peter Wemm , John Baldwin , Alfred Perlstein , current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com Subject: Re: HEADS-UP: await/asleep removal imminent References: <200101181525.QAA21260@freebsd.dk> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > It seems Peter Wemm wrote: > > > > Soren, can you retest a buildworld with the currently committed kernel > > with no other changes? Let us see if the forward_signal() stuff is the > > culprit, and if not, try adding just the i386/i386/machdep.c patch to HLT > > the idle CPU. (if *that* makes a difference then we have got trouble!) > > It seems that the HLT thing is exactly the patch that makes it work! > > So we have trouble, I said that all along .5 :) I don't know about your system but mine gets a LOT warmer when HALT is disabled. > > -Søren > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 10:42: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id AD97337B699 for ; Thu, 18 Jan 2001 10:41:41 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0IIjYs68443; Thu, 18 Jan 2001 10:45:35 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <5.0.2.1.0.20010118152851.00a52ec0@tfrsolcom> Date: Thu, 18 Jan 2001 10:41:28 -0800 (PST) From: John Baldwin To: Rogier Mulhuijzen Subject: RE: Panic w/crash dump (looks like atomic.h problem) Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jan-01 Rogier Mulhuijzen wrote: > Got a nice crash while running XMMS under X11 and running a 'make world -j > 128 -DNOCLEAN' on ttyv0 > > Current was cvsupped on the 17th in the morning (Central European Time) IIRC. > > Attached: script(1) output of gdb kernel trace > Kernel config file > dmesg(8) output > > I'm not an expert on tracing panics, I just followed the instructions in > the FAQ, so feel free to ask me to look at stuff. > > DocWilco If you look at the traceback, vref() was called with a NULL vnode as its parameter, so the panic is due to dereferencing a NULL pointer, not a bug in the atomic ops. :) As to why the kernel was vref()'ing a NULL pointer, I have no idea. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 10:42: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id D145537B402; Thu, 18 Jan 2001 10:41:35 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0IIjZs68447; Thu, 18 Jan 2001 10:45:35 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A6732EF.C83945CA@elischer.org> Date: Thu, 18 Jan 2001 10:41:30 -0800 (PST) From: John Baldwin To: Julian Elischer Subject: Re: HEADS-UP: await/asleep removal imminent Cc: rjesup@wgate.com, arch@FreeBSD.org, current@FreeBSD.org, Alfred Perlstein , Peter Wemm , Soren Schmidt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jan-01 Julian Elischer wrote: > Soren Schmidt wrote: >> >> It seems Peter Wemm wrote: >> > >> > Soren, can you retest a buildworld with the currently committed kernel >> > with no other changes? Let us see if the forward_signal() stuff is the >> > culprit, and if not, try adding just the i386/i386/machdep.c patch to HLT >> > the idle CPU. (if *that* makes a difference then we have got trouble!) >> >> It seems that the HLT thing is exactly the patch that makes it work! >> >> So we have trouble, I said that all along .5 :) > > I don't know about your system but mine gets a LOT warmer > when HALT is disabled. We don't IPI a hlt'd CPU in setrunqueue() right now, so once a CPU is HLT'd it stays idle until the I/O APIC sends it an interrupt to handle. I've watched top(1) during a buildworld with this enabled and have seen it with 8 processes in SRUN, but one CPU idle. :( Also, FWIW, the quad xeon doesn't use this patch and has run fine for several days now. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 11: 9:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from tfrsolcom.transfer-solutions.com (mail.transfer-solutions.com [195.109.218.250]) by hub.freebsd.org (Postfix) with ESMTP id 9611C37B400; Thu, 18 Jan 2001 11:09:29 -0800 (PST) Received: by mail.transfer-solutions.com with Internet Mail Service (5.5.2650.21) id ; Thu, 18 Jan 2001 20:03:42 +0100 Received: from tfrsolcom.transfer-solutions.com (localhost [127.0.0.1]) by tfrsolcom.transfer-solutions.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id DAATSSNQ; Thu, 18 Jan 2001 20:03:29 +0100 Received: from 193.100.100.198 by tfrsolcom.transfer-solutions.com (InterScan E-Mail VirusWall NT); Thu, 18 Jan 2001 20:03:29 +0100 (Romance Standard Time) From: Rogier Mulhuijzen To: John Baldwin , Rogier Mulhuijzen Cc: freebsd-current@FreeBSD.org Message-Id: <5.0.2.1.0.20010118201134.00a542c0@tfrsolcom> X-Sender: rmulhuij@tfrsolcom X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Thu, 18 Jan 2001 20:14:54 +0100 Subject: RE: Panic w/crash dump (looks like atomic.h problem) In-Reply-To: References: <5.0.2.1.0.20010118152851.00a52ec0@tfrsolcom> 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 >If you look at the traceback, vref() was called with a NULL vnode as its >parameter, so the panic is due to dereferencing a NULL pointer, not a bug in >the atomic ops. :) As to why the kernel was vref()'ing a NULL pointer, I have >no idea. #11 0xc01c057f in vref (vp=0x0) at machine/atomic.h:332 #12 0xc0f7aa82 in ?? () #13 0xc0f7b933 in ?? () #14 0xc0f7de1c in ?? () #15 0xc0f7abb5 in ?? () #16 0xc01c8acc in vn_read (fp=0xc105e9c0, uio=0xc7ff1ee4, cred=0xc1047600, flags=0, p=0xc7f61540) at vnode_if.h:279 #17 0xc019b9ba in dofileread (p=0xc7f61540, fp=0xc105e9c0, fd=9, buf=0x8223c00, nbyte=512, offset=-1, flags=0) at ../../sys/file.h:141 Yup, looks like you're right. Totally overlooked that. (Can you tell reading this is new to me? =) ) My next question is, where are those ??'s from in #12 - #15? Could they be addresses in kernel modules? If so, how do I readable output from that, save compiling everything into the kernel statically? DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 11:30: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (unknown [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id F2C3837B400 for ; Thu, 18 Jan 2001 11:29:42 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0IJiIQ00677; Thu, 18 Jan 2001 11:44:19 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101181944.f0IJiIQ00677@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Will Andrews Cc: FreeBSD Current Subject: Re: HEADS UP: I386_CPU In-reply-to: Your message of "Thu, 18 Jan 2001 07:21:10 EST." <20010118072110.A431@puck.firepipe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Jan 2001 11:44:18 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That's one of the big reasons that we're 4.x based right now rather > > than 3.x based, despite 4.x's slightly larger memory footprint. That > > and 4.x's much better c++ compiler. > > Well, Warner, I've never done embedded systems. So, tell me, do they > actually use any C++ code in embedded systems? C++ has a rather high > overhead as far as disk space & memory goes. I would imagine that 99%+ > of embedded systems do not use C++ code except perhaps for a very small > amount of the code. You have a very vivid imagination. Unfortunately, imagination isn't very helpful here; the whole idea is to do stuff that's actually useful, not just what we'd imagine might be useful. And in that regard, a *lot* of application programming (which includes programming for embedded systems) is done using c++ compilers. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 11:40:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from stox.sa.enteract.com (stox.sa.enteract.com [207.229.132.161]) by hub.freebsd.org (Postfix) with ESMTP id 0C6B437B400 for ; Thu, 18 Jan 2001 11:40:18 -0800 (PST) Received: (from stox@localhost) by stox.sa.enteract.com (8.11.1/8.9.3) id f0IJeBV00960; Thu, 18 Jan 2001 13:40:11 -0600 (CST) (envelope-from stox) 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: <20010118072110.A431@puck.firepipe.net> Date: Thu, 18 Jan 2001 13:40:11 -0600 (CST) From: "Kenneth P. Stox" To: Will Andrews Subject: Re: HEADS UP: I386_CPU Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jan-01 Will Andrews wrote: > Well, Warner, I've never done embedded systems. So, tell me, do they > actually use any C++ code in embedded systems? C++ has a rather high > overhead as far as disk space & memory goes. I would imagine that 99%+ > of embedded systems do not use C++ code except perhaps for a very small > amount of the code. FYI, one of the first C++ applications to see the light of day outside of Bell Labs was DMDPI, a debugger for an intelligent graphic terminal ( DMD5620 ). I think that comes close to qualifying as an embedded application. When it is the right tool for the right job, C++ can be the most efficient tool around. When used incorrectly, it can be a nightmare, but then again, so can any language. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 11:49: 3 2001 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 1D95737B400; Thu, 18 Jan 2001 11:48:45 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id UAA49300; Thu, 18 Jan 2001 20:48:42 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Rogier Mulhuijzen Cc: John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: Panic w/crash dump (looks like atomic.h problem) References: <5.0.2.1.0.20010118152851.00a52ec0@tfrsolcom> <5.0.2.1.0.20010118201134.00a542c0@tfrsolcom> From: Dag-Erling Smorgrav Date: 18 Jan 2001 20:48:41 +0100 In-Reply-To: Rogier Mulhuijzen's message of "Thu, 18 Jan 2001 20:14:54 +0100" Message-ID: Lines: 14 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 Rogier Mulhuijzen writes: > My next question is, where are those ??'s from in #12 - #15? Could they be > addresses in kernel modules? Quite possibly. > If so, how do I readable output from that, save compiling everything into > the kernel statically? Read the handbook section on debugging kernel modules. DES -- Dag-Erling Smorgrav - des@ofug.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 18 12: 7:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 147FB37B698; Thu, 18 Jan 2001 12:06:43 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id D976819C7; Thu, 18 Jan 2001 15:06:37 -0500 (EST) Date: Thu, 18 Jan 2001 15:06:37 -0500 From: Will Andrews To: Mike Smith Cc: Will Andrews , FreeBSD Current Subject: Re: HEADS UP: I386_CPU Message-ID: <20010118150637.H1475@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Mike Smith , FreeBSD Current References: <20010118072110.A431@puck.firepipe.net> <200101181944.f0IJiIQ00677@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="PNpeiK4tTqhYOExY" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101181944.f0IJiIQ00677@mass.osd.bsdi.com>; from msmith@FreeBSD.org on Thu, Jan 18, 2001 at 11:44:18AM -0800 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --PNpeiK4tTqhYOExY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 18, 2001 at 11:44:18AM -0800, Mike Smith wrote: > You have a very vivid imagination. It's not easy to replace imagination with experience. This takes years, which I have yet to come upon. :-) > Unfortunately, imagination isn't very helpful here; the whole idea is to= =20 > do stuff that's actually useful, not just what we'd imagine might be=20 > useful. And in that regard, a *lot* of application programming (which= =20 > includes programming for embedded systems) is done using c++ compilers. As Warner and Wes pointed out, this is certainly true. I guess I need a reality check on this. ;> --=20 wca --PNpeiK4tTqhYOExY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6Z0zNF47idPgWcsURAisdAJ4uZkjUMXmkQ+lyF9DlpZdDFzt2TgCeJ0Zs HixfxqSIcFrQ4EWS0sQofvI= =QbxR -----END PGP SIGNATURE----- --PNpeiK4tTqhYOExY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 13: 7:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns1.virtuale.ws (ns1.virtuale.ws [210.155.63.114]) by hub.freebsd.org (Postfix) with ESMTP id AADA637B698 for ; Thu, 18 Jan 2001 13:07:01 -0800 (PST) Received: (from nobody@localhost) by ns1.virtuale.ws (8.9.3/8.9.3) id GAA14365; Fri, 19 Jan 2001 06:09:12 +0900 Date: Fri, 19 Jan 2001 06:09:12 +0900 Message-Id: <200101182109.GAA14365@ns1.virtuale.ws> To: freebsd-current@freebsd.org Subject: Internet Entertainment Solution From: swesu@hotmail.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ccccccccccccccccccccccccc @@@ƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€”Ì”„‚Ì‚¨’m‚点 ccccccccccccccccccccccccc ‚Šz‚Ì”ï—p‚ª‚©‚©‚Á‚Ä‚¢‚½“®‰æ‚̃VƒXƒeƒ€‚ðA‚±‚Ì“x ’ቿŠi‚Ŕ̔„‚·‚鎖‚É‚È‚è‚Ü‚µ‚½B ƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€‚Æ‚ÍEEE „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‚PDƒXƒ^ƒWƒI‚ð—pˆÓ‚µA‚»‚±‚ɃrƒfƒIƒJƒƒ‰‚ðÝ’uB @@—«‚ªƒXƒ^ƒ“ƒoƒC‚µ‚Ü‚·B ‚QD‰ïˆõ‚Ì’j«‚ÍAƒƒ“ƒo[“o˜^‚ð‚·‚Ü‚¹AID‚ÆPW‚ð @@“ü—Í‚µA‚»‚Ì“®‰æ‚ð‰{——‚µ‚Ü‚·B ‚RD’j«‚ÍAuƒ`ƒƒƒbƒgv‚Æ‚¢‚¤ƒVƒXƒeƒ€‚ðŽg‚¢A @@•¶Žš‚¾‚¯‚Å—«‚ƃRƒ~ƒ…ƒjƒP[ƒVƒ‡ƒ“‚ð‚Æ‚è‚Ü‚·B ‚SD‚»‚Ì•¶Žš‚ðƒXƒ^ƒWƒI‚Ì—‚ÌŽq‚̓fƒBƒXƒvƒŒ[‚Å @@Œ©‚È‚ª‚ç‰ï˜b‚µ‚Ü‚·B—‚ÌŽq‚̓rƒfƒIƒJƒƒ‰‚É @@Œü‚©‚Á‚Ęb‚ð‚µ‚½‚èA—lX‚È“®ì‚ð‚µ‚½‚è‚·‚ê‚Î @@‚¢‚¢‚¾‚¯‚Å‚·B‚»‚ꂪ‰ïˆõ’j«‚ɃCƒ“ƒ^[ƒlƒbƒg @@‚ð—˜—p‚µ‚Ä”zM‚³‚ê‚Ü‚·B ‚TD—˜—p‚µ‚½ŽžŠÔ•ª‚Ì‰Û‹à‚ª‹L˜^‚³‚êAˆê’è‚ÌŽžŠÔ‚Å @@¿‹ƒ[ƒ‹‚ð‘—M‚µ‚Ü‚·B „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‚±‚Ì‘S‚ẴVƒXƒeƒ€‚ð—pˆÓ‚·‚é‚Ì‚É—lX‚ȃ‰ƒCƒZƒ“ƒX ‚â‹@Þ‚È‚Çž‚Ý‚ÅA1ç–œŽã‚Ì”ï—p‚ª‚©‚©‚è‚Ü‚·B ¡‰ñ‚ÍA‚±‚̈ê˜A‚̃VƒXƒeƒ€Eƒ‰ƒCƒZƒ“ƒXE‹@Þ‚ðA ‚܂Ƃ߂ĒቿŠi‚Ŕ̔„’v‚µ‚Ü‚·BŒã‚ÍAADSL‚È‚Ç‚Ì o—ˆ‚邾‚¯‘¬‚¢‰ñü‚Æ­X‚Ì‹@Þ‚ð—pˆÓ‚·‚邾‚¯‚ÅA ‚·‚®‚É‚±‚Ìuƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€v‚ð—˜—p‚·‚鎖 ‚ªo—ˆ‚Ü‚·Bo‰ï‚¢ƒTƒCƒg‚Ŗڋʂ̃Rƒ~ƒ…ƒjƒP[ƒVƒ‡ƒ“ ‚É—˜—p‚·‚é‚Ì‚à‚悵AƒAƒ_ƒ‹ƒgŠÖ˜A‚Å—˜—p‚·‚é‚à‚悵A ‚±‚̒ቿŠi‚Å—pˆÓ‚Å‚«‚é—l‚ȃVƒXƒeƒ€‚Å‚Í‚ ‚è‚Ü‚¹‚ñB ¥”ñ‚±‚Ì‹@‰ï‚ðŒ©“¦‚³‚¸AVƒrƒWƒlƒX‚Ŗׂ¯‚ĉº‚³‚¢B “Á‚É‚Ç‚ñ‚ȃWƒƒƒ“ƒ‹‚Å‚àu—«‚Ì’²’B‚É¢‚ç‚È‚¢v—l ‚ÈŽ–‹Æ‚ÉÅ‚àƒ}ƒbƒ`‚µ‚Ä‚¢‚Ü‚·B ƒVƒXƒeƒ€‡@ Windows NT „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ EReal Server EDataBase(MSSQL) EŒŸjƒvƒƒOƒ‰ƒ€•¿‹ƒvƒƒOƒ‰ƒ€iŽè“®j Eƒƒ“ƒo[“o˜^ƒvƒƒOƒ‰ƒ€ Eƒ`ƒƒƒbƒgƒvƒƒOƒ‰ƒ€ EDual CPU(P‡U400x2jNTƒT[ƒo[ EƒrƒfƒIƒJƒƒ‰ EPCiNECj „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‘Šz1ç–œŽã‚Å\\’z‚µ‚½ƒVƒXƒeƒ€‡@‚ð300–œ‰~‚Å ”Ì”„‚µ‚Ü‚·B ƒVƒXƒeƒ€‡A Redhat Linux 6.2 „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ EReal Server EDataBase(MYSQLAMSQL) EŒŸjƒvƒƒOƒ‰ƒ€•¿‹ƒvƒƒOƒ‰ƒ€iŽ©“®j Eƒƒ“ƒo[“o˜^ƒvƒƒOƒ‰ƒ€ Eƒ`ƒƒƒbƒgƒvƒƒOƒ‰ƒ€ „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ŠJ”­”ï—p500–œŽã‚Å\\’zo—ˆ‚éƒVƒXƒeƒ€‡A‚ð300–œ‰~‚Å ”Ì”„‚µ‚Ü‚·B ƒAƒ_ƒ‹ƒgƒTƒCƒg‚Åuƒ‰ƒCƒuƒ`ƒƒƒbƒgv‚ðs‚¤ê‡A Šù‚ÉŽÀÑ‚Ì‚ ‚éƒRƒ“ƒeƒ“ƒc–ˆ‚¨÷‚è‚·‚鎖‚ào—ˆ‚Ü‚·B ‚±‚Ìê‡AŠù‚É1–œl’ö“x‚̌ڋqƒf[ƒ^‚à‚¨÷‚è‚·‚é Ž–‚ªo—ˆ‚Ü‚·Bwebƒy[ƒW‚àŠù‚É’m–¼“x‚Ì‚à‚Ì‚ð‚»‚Ì‚Ü ‚ÜA—˜—p‚Å‚«‚Ü‚·‚µAŠeŽíƒT[ƒ`ƒGƒ“ƒWƒ“‚È‚Ç‚É‚à “o˜^ς݂̃hƒƒCƒ“‚ª‚»‚Ì‚Ü‚Ü—˜—p‚Å‚«‚Ü‚·B—v‚·‚é‚É ŽÀÑ‚Ì‚ ‚éƒTƒCƒg‚ð‚»‚Ì‚Ü‚ÜƒVƒXƒeƒ€E‹@Þ–ˆA‚¨÷‚è o—ˆ‚é‚ÆŒ¾‚¤‚±‚Æ‚Å‚·BV‹K‚̃vƒƒ‚[ƒVƒ‡ƒ“‚È‚Ç‚Ì •K—v‚à‚È‚­A‚ ‚é’ö“x‚ׂ̖¯‚à–ñ‘©‚³‚ê‚Ä‚¢‚é‚킯‚Å‚·B ‚±‚¿‚ç‚ð‚²Šó–]‚ÌꇂÍA‚²‘Š’k‰º‚³‚¢B ‚Ü‚½AƒvƒƒOƒ‰ƒ€‚âƒT[ƒo[‚È‚ÇA’P‘̂ł̔̔„‚à l‚¦‚Ä‚¨‚è‚Ü‚·BReal Server‚Ȃǂ̃‰ƒCƒZƒ“ƒX‚ÍA 300–œ’ö‚µ‚Ü‚·‚ªA“–ŽÐ‚Å‚ÍAƒ‰ƒCƒZƒ“ƒX–ˆA’ቿŠi‚Å ‚¨÷‚è‚·‚邱‚Æ‚ªo—ˆ‚Ü‚·‚Ì‚ÅA‚²‘Š’k‰º‚³‚¢B ‹ï‘Ì“I‚É‚Ç‚¤‚¢‚Á‚½ƒVƒXƒeƒ€‚È‚Ì‚©‘ÌŒ±‚µ‚½‚¢•û‚ÍA ƒAƒ_ƒ‹ƒgƒTƒCƒg‚Å‚·‚ªAŽÀÛ‚É‚²——‚É‚È‚ê‚Ü‚·‚Ì‚ÅA ‰º‹LURL‚ð–K–₵‚Ä‚Ý‚Ä‚­‚¾‚³‚¢B http://www.dreamroom.ws/ ‚±‚Ì‹@‰ï‚𓦂·Žè‚Í‚ ‚è‚Ü‚¹‚ñBV‹KŽ–‹Æ‚ðŒŸ“¢‚Ì•ûA ¡‚·‚®A‚²˜A—‰º‚³‚¢B‚ ‚ç‚ä‚錂ÅA‘Š’k‚³‚¹‚Ä ’¸‚«‚Ü‚·B ccccccccccccccccccccccccc <‚¨–â‚¢‡‚¹‚Í‚±‚¿‚ç‚Ü‚Å>@¨@info@dreamroom.ws ccccccccccccccccccccccccc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 13: 7:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns1.virtuale.ws (ns1.virtuale.ws [210.155.63.114]) by hub.freebsd.org (Postfix) with ESMTP id 3715537B400 for ; Thu, 18 Jan 2001 13:07:03 -0800 (PST) Received: (from nobody@localhost) by ns1.virtuale.ws (8.9.3/8.9.3) id GAA14408; Fri, 19 Jan 2001 06:09:15 +0900 Date: Fri, 19 Jan 2001 06:09:15 +0900 Message-Id: <200101182109.GAA14408@ns1.virtuale.ws> To: freebsd-current@freebsd.org Subject: Internet Entertainment Solution From: swesu@hotmail.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ccccccccccccccccccccccccc @@@ƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€”Ì”„‚Ì‚¨’m‚点 ccccccccccccccccccccccccc ‚Šz‚Ì”ï—p‚ª‚©‚©‚Á‚Ä‚¢‚½“®‰æ‚̃VƒXƒeƒ€‚ðA‚±‚Ì“x ’ቿŠi‚Ŕ̔„‚·‚鎖‚É‚È‚è‚Ü‚µ‚½B ƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€‚Æ‚ÍEEE „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‚PDƒXƒ^ƒWƒI‚ð—pˆÓ‚µA‚»‚±‚ɃrƒfƒIƒJƒƒ‰‚ðÝ’uB @@—«‚ªƒXƒ^ƒ“ƒoƒC‚µ‚Ü‚·B ‚QD‰ïˆõ‚Ì’j«‚ÍAƒƒ“ƒo[“o˜^‚ð‚·‚Ü‚¹AID‚ÆPW‚ð @@“ü—Í‚µA‚»‚Ì“®‰æ‚ð‰{——‚µ‚Ü‚·B ‚RD’j«‚ÍAuƒ`ƒƒƒbƒgv‚Æ‚¢‚¤ƒVƒXƒeƒ€‚ðŽg‚¢A @@•¶Žš‚¾‚¯‚Å—«‚ƃRƒ~ƒ…ƒjƒP[ƒVƒ‡ƒ“‚ð‚Æ‚è‚Ü‚·B ‚SD‚»‚Ì•¶Žš‚ðƒXƒ^ƒWƒI‚Ì—‚ÌŽq‚̓fƒBƒXƒvƒŒ[‚Å @@Œ©‚È‚ª‚ç‰ï˜b‚µ‚Ü‚·B—‚ÌŽq‚̓rƒfƒIƒJƒƒ‰‚É @@Œü‚©‚Á‚Ęb‚ð‚µ‚½‚èA—lX‚È“®ì‚ð‚µ‚½‚è‚·‚ê‚Î @@‚¢‚¢‚¾‚¯‚Å‚·B‚»‚ꂪ‰ïˆõ’j«‚ɃCƒ“ƒ^[ƒlƒbƒg @@‚ð—˜—p‚µ‚Ä”zM‚³‚ê‚Ü‚·B ‚TD—˜—p‚µ‚½ŽžŠÔ•ª‚Ì‰Û‹à‚ª‹L˜^‚³‚êAˆê’è‚ÌŽžŠÔ‚Å @@¿‹ƒ[ƒ‹‚ð‘—M‚µ‚Ü‚·B „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‚±‚Ì‘S‚ẴVƒXƒeƒ€‚ð—pˆÓ‚·‚é‚Ì‚É—lX‚ȃ‰ƒCƒZƒ“ƒX ‚â‹@Þ‚È‚Çž‚Ý‚ÅA1ç–œŽã‚Ì”ï—p‚ª‚©‚©‚è‚Ü‚·B ¡‰ñ‚ÍA‚±‚̈ê˜A‚̃VƒXƒeƒ€Eƒ‰ƒCƒZƒ“ƒXE‹@Þ‚ðA ‚܂Ƃ߂ĒቿŠi‚Ŕ̔„’v‚µ‚Ü‚·BŒã‚ÍAADSL‚È‚Ç‚Ì o—ˆ‚邾‚¯‘¬‚¢‰ñü‚Æ­X‚Ì‹@Þ‚ð—pˆÓ‚·‚邾‚¯‚ÅA ‚·‚®‚É‚±‚Ìuƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€v‚ð—˜—p‚·‚鎖 ‚ªo—ˆ‚Ü‚·Bo‰ï‚¢ƒTƒCƒg‚Ŗڋʂ̃Rƒ~ƒ…ƒjƒP[ƒVƒ‡ƒ“ ‚É—˜—p‚·‚é‚Ì‚à‚悵AƒAƒ_ƒ‹ƒgŠÖ˜A‚Å—˜—p‚·‚é‚à‚悵A ‚±‚̒ቿŠi‚Å—pˆÓ‚Å‚«‚é—l‚ȃVƒXƒeƒ€‚Å‚Í‚ ‚è‚Ü‚¹‚ñB ¥”ñ‚±‚Ì‹@‰ï‚ðŒ©“¦‚³‚¸AVƒrƒWƒlƒX‚Ŗׂ¯‚ĉº‚³‚¢B “Á‚É‚Ç‚ñ‚ȃWƒƒƒ“ƒ‹‚Å‚àu—«‚Ì’²’B‚É¢‚ç‚È‚¢v—l ‚ÈŽ–‹Æ‚ÉÅ‚àƒ}ƒbƒ`‚µ‚Ä‚¢‚Ü‚·B ƒVƒXƒeƒ€‡@ Windows NT „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ EReal Server EDataBase(MSSQL) EŒŸjƒvƒƒOƒ‰ƒ€•¿‹ƒvƒƒOƒ‰ƒ€iŽè“®j Eƒƒ“ƒo[“o˜^ƒvƒƒOƒ‰ƒ€ Eƒ`ƒƒƒbƒgƒvƒƒOƒ‰ƒ€ EDual CPU(P‡U400x2jNTƒT[ƒo[ EƒrƒfƒIƒJƒƒ‰ EPCiNECj „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‘Šz1ç–œŽã‚Å\\’z‚µ‚½ƒVƒXƒeƒ€‡@‚ð300–œ‰~‚Å ”Ì”„‚µ‚Ü‚·B ƒVƒXƒeƒ€‡A Redhat Linux 6.2 „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ EReal Server EDataBase(MYSQLAMSQL) EŒŸjƒvƒƒOƒ‰ƒ€•¿‹ƒvƒƒOƒ‰ƒ€iŽ©“®j Eƒƒ“ƒo[“o˜^ƒvƒƒOƒ‰ƒ€ ? ƒ`ƒƒƒbƒgƒvƒƒOƒ‰ƒ€ „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ŠJ”­”ï—p500–œŽã‚Å\\’zo—ˆ‚éƒVƒXƒeƒ€‡A‚ð300–œ‰~‚Å ”Ì”„‚µ‚Ü‚·B ƒAƒ_ƒ‹ƒgƒTƒCƒg‚Åuƒ‰ƒCƒuƒ`ƒƒƒbƒgv‚ðs‚¤ê‡A Šù‚ÉŽÀÑ‚Ì‚ ‚éƒRƒ“ƒeƒ“ƒc–ˆ‚¨÷‚è‚·‚鎖‚ào—ˆ‚Ü‚·B ‚±‚Ìê‡AŠù‚É1–œl’ö“x‚̌ڋqƒf[ƒ^‚à‚¨÷‚è‚·‚é Ž–‚ªo—ˆ‚Ü‚·Bwebƒy[ƒW‚àŠù‚É’m–¼“x‚Ì‚à‚Ì‚ð‚»‚Ì‚Ü ‚ÜA—˜—p‚Å‚«‚Ü‚·‚µAŠeŽíƒT[ƒ`ƒGƒ“ƒWƒ“‚È‚Ç‚É‚à “o˜^ς݂̃hƒƒCƒ“‚ª‚»‚Ì‚Ü‚Ü—˜—p‚Å‚«‚Ü‚·B—v‚·‚é‚É ŽÀÑ‚Ì‚ ‚éƒTƒCƒg‚ð‚»‚Ì‚Ü‚ÜƒVƒXƒeƒ€E‹@Þ–ˆA‚¨÷‚è o—ˆ‚é‚ÆŒ¾‚¤‚±‚Æ‚Å‚·BV‹K‚̃vƒƒ‚[ƒVƒ‡ƒ“‚È‚Ç‚Ì •K—v‚à‚È‚­A‚ ‚é’ö“x‚ׂ̖¯‚à–ñ‘©‚³‚ê‚Ä‚¢‚é‚킯‚Å‚·B ‚±‚¿‚ç‚ð‚²Šó–]‚ÌꇂÍA‚²‘Š’k‰º‚³‚¢B ‚Ü‚½AƒvƒƒOƒ‰ƒ€‚âƒT[ƒo[‚È‚ÇA’P‘̂ł̔̔„‚à l‚¦‚Ä‚¨‚è‚Ü‚·BReal Server‚Ȃǂ̃‰ƒCƒZƒ“ƒX‚ÍA 300–œ’ö‚µ‚Ü‚·‚ªA“–ŽÐ‚Å‚ÍAƒ‰ƒCƒZƒ“ƒX–ˆA’ቿŠi‚Å ‚¨÷‚è‚·‚邱‚Æ‚ªo—ˆ‚Ü‚·‚Ì‚ÅA‚²‘Š’k‰º‚³‚¢B ‹ï‘Ì“I‚É‚Ç‚¤‚¢‚Á‚½ƒVƒXƒeƒ€‚È‚Ì‚©‘ÌŒ±‚µ‚½‚¢•û‚ÍA ƒAƒ_ƒ‹ƒgƒTƒCƒg‚Å‚·‚ªAŽÀÛ‚É‚²——‚É‚È‚ê‚Ü‚·‚Ì‚ÅA ‰º‹LURL‚ð–K–₵‚Ä‚Ý‚Ä‚­‚¾‚³‚¢B http://www.dreamroom.ws/ ‚±‚Ì‹@‰ï‚𓦂·Žè‚Í‚ ‚è‚Ü‚¹‚ñBV‹KŽ–‹Æ‚ðŒŸ“¢‚Ì•ûA ¡‚·‚®A‚²˜A—‰º‚³‚¢B‚ ‚ç‚ä‚錂ÅA‘Š’k‚³‚¹‚Ä ’¸‚«‚Ü‚·B ccccccccccccccccccccccccc <‚¨–â‚¢‡‚¹‚Í‚±‚¿‚ç‚Ü‚Å>@¨@info@dreamroom.ws ccccccccccccccccccccccccc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 13: 9:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id EE55C37B400 for ; Thu, 18 Jan 2001 13:09:13 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0IL6xL65432; Thu, 18 Jan 2001 13:06:59 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <5.0.2.1.0.20010118201134.00a542c0@tfrsolcom> Date: Thu, 18 Jan 2001 13:09:07 -0800 (PST) From: John Baldwin To: Rogier Mulhuijzen Subject: RE: Panic w/crash dump (looks like atomic.h problem) Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jan-01 Rogier Mulhuijzen wrote: > >>If you look at the traceback, vref() was called with a NULL vnode as its >>parameter, so the panic is due to dereferencing a NULL pointer, not a bug in >>the atomic ops. :) As to why the kernel was vref()'ing a NULL pointer, I >>have >>no idea. > >#11 0xc01c057f in vref (vp=0x0) at machine/atomic.h:332 >#12 0xc0f7aa82 in ?? () >#13 0xc0f7b933 in ?? () >#14 0xc0f7de1c in ?? () >#15 0xc0f7abb5 in ?? () >#16 0xc01c8acc in vn_read (fp=0xc105e9c0, uio=0xc7ff1ee4, cred=0xc1047600, > flags=0, p=0xc7f61540) at vnode_if.h:279 >#17 0xc019b9ba in dofileread (p=0xc7f61540, fp=0xc105e9c0, fd=9, > buf=0x8223c00, nbyte=512, offset=-1, flags=0) at ../../sys/file.h:141 > > Yup, looks like you're right. Totally overlooked that. (Can you tell > reading this is new to me? =) ) > > My next question is, where are those ??'s from in #12 - #15? Could they be > addresses in kernel modules? Yes. > If so, how do I readable output from that, save compiling everything into > the kernel statically? Static kernel is easiest, esp. if you can reproduce this. Otherwise you have to do other fun stuff to read in the symbols from the module. FWIW, if you are doing development or running -current, use a static kernel. If you are writing a specific device driver, then use a module for that, but make the rest of your kernel static. It's just easier that way. Also, for reading module symbols in, I think there is a relatiely easy way to do this now in gdb, but I don't know what it is. Of course, gdb -k is kind of broken right now because it hasn't caught up to the latest round of per-cpu changes.. > DocWilco -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 19:31: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 827F037B69B; Thu, 18 Jan 2001 19:30:41 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 18 Jan 2001 19:28:39 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0J3UPa75677; Thu, 18 Jan 2001 19:30:25 -0800 (PST) (envelope-from cjc) Date: Thu, 18 Jan 2001 19:30:25 -0800 (PST) Message-Id: <200101190330.f0J3UPa75677@rfx-216-196-73-168.users.reflexcom.com> To: FreeBSD-gnats-submit@freebsd.org Subject: syslogd(8) does not update hostname From: cjclark@reflexcom.com Reply-To: cjclark@alum.mit.edu Cc: current@freebsd.org X-send-pr-version: 3.113 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Submitter-Id: current-users >Originator: Crist J. Clark >Organization: >Confidential: no >Synopsis: syslogd(8) does not update hostname >Severity: non-critical >Priority: medium >Category: bin >Release: FreeBSD 5.0-CURRENT i386 >Class: sw-bug >Environment: All standard FreeBSD distributions. The code discussed is from 5.0-CURRENT, but should trivially merge back to -STABLE. >Description: Many tools and progams within FreeBSD date back to a time when it was expected that a machines IP and hostname seldom, if ever, changed. Even when a IP and hostname were received at boot, it rarely changed until shutdown. With many users using protocols like DHCP where IP and hostname change with time, many tools do not deal well with this behavior. One of these tools is syslogd(8). syslogd(8) is typically started at boot time and runs until shutdown. However, syslogd(8) loads the hostname at startup and syslogd(8)'s idea of the hostname can never change while it is running. One might expect that a SIGHUP would cause syslogd(8) to load the new hostname since a SIGHUP can cause syslogd(8) to re-read its configuration file and re-open the log files, but it does not. The fact that the hostname does not change can cause confusion in the log files. It could be especially troublesome when a machine is logging to a central loghost. At any given time, the names in the log files may not have any correspondence to the names the hosts currently have. There are even issues on a host that gets its IP and hostname via DHCP at boot and the name never changes. syslogd(8) is started before any network services are initialized in /etc/rc. I propose that syslogd(8) should reload the hostname with a SIGHUP. I cannot think of any reason that one should not update the hostname, but as I pointed out, there are reasons why one would want that behavior. >How-To-Repeat: # hostname -s bubbles # hostname bubbles-test.domain.org # kill -HUP `cat /var/run/syslog.pid` # logger -p user.notice "hostname test" # tail -4 /var/log/messages Jan 17 21:45:00 bubbles /boot/kernel/kernel: acd0: CDROM at ata0-slave using BIOSPIO Jan 17 21:45:00 bubbles /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s1a Jan 18 00:41:14 bubbles su: cjc to root on /dev/ttyp0 Jan 18 00:58:34 bubbles cjc: hostname test >Fix: I do not see any reason we cannot move the code that gets the hostname from the main() function into init(). init() is called when to "reload" settings. The hostname is never used in main() before init() is called. The patch is against -CURRENT and my box has not exploded yet. Here is what the above test looks like with the change in place. # hostname -s bubbles # hostname bubbles-test.cjclark.org # kill -HUP `cat /var/run/syslog.pid ` # logger -p user.notice "syslogd hostname test" # hostname bubbles.cjclark.org # kill -HUP `cat /var/run/syslog.pid ` # logger -p user.notice "syslogd hostname test" # tail -4 /var/log/messages Jan 18 13:36:58 bubbles su: BAD SU cjc to root on /dev/ttyp0 Jan 18 13:37:03 bubbles su: cjc to root on /dev/ttyp0 Jan 18 13:38:40 bubbles-test cjc: syslogd hostname test Jan 18 13:39:11 bubbles cjc: syslogd hostname test --- syslogd.c 2001/01/18 08:06:34 +++ syslogd.c 2001/01/18 08:09:23 @@ -395,12 +395,6 @@ consfile.f_type = F_CONSOLE; (void)strcpy(consfile.f_un.f_fname, ctty + sizeof _PATH_DEV - 1); - (void)gethostname(LocalHostName, sizeof(LocalHostName)); - if ((p = strchr(LocalHostName, '.')) != NULL) { - *p++ = '\0'; - LocalDomain = p; - } else - LocalDomain = ""; (void)strcpy(bootfile, getbootfile()); (void)signal(SIGTERM, die); (void)signal(SIGINT, Debug ? die : SIG_IGN); @@ -1342,6 +1336,16 @@ char host[MAXHOSTNAMELEN+1]; dprintf("init\n"); + + /* + * Load hostname (may have changed) + */ + (void)gethostname(LocalHostName, sizeof(LocalHostName)); + if ((p = strchr(LocalHostName, '.')) != NULL) { + *p++ = '\0'; + LocalDomain = p; + } else + LocalDomain = ""; /* * Close all open log files. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 20:26: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from VL-MS-MR002.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id D79BA37B400 for ; Thu, 18 Jan 2001 20:25:43 -0800 (PST) Received: from jehovah ([24.201.144.31]) by VL-MS-MR002.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G7E6YQ04.YWQ for ; Thu, 18 Jan 2001 23:25:38 -0500 Message-ID: <010401c081d0$183b8b30$1f90c918@jehovah> From: "Bosko Milekic" To: Subject: Small HEADS-UP Date: Thu, 18 Jan 2001 23:27:12 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, A few hours ago, this has been committed to -CURRENT: Commit log: [...] > Log: > Implement MTX_RECURSE flag for mtx_init(). > All calls to mtx_init() for mutexes that recurse must now include > the MTX_RECURSE bit in the flag argument variable. This change is in > preparation for an upcoming (further) mutex API cleanup. > The witness code will call panic() if a lock is found to recurse but > the MTX_RECURSE bit was not set during the lock's initialization. > > The old MTX_RECURSE "state" bit (in mtx_lock) has been renamed to > MTX_RECURSED, which is more appropriate given its meaning. > > The following locks have been made "recursive," thus far: > eventhandler, Giant, callout, sched_lock, possibly some others declared > in the architecture-specific code, all of the network card driver locks > in pci/, as well as some other locks in dev/ stuff that I've found to > be recursive. [...] This is a small HEADS-UP to let people who have WITNESS turned on that if they stumble into a panic() with a message such as: "[...] recursed on non-recursive mutex foo [...]" to take note of it and report it as soon as possible to the lists (feel free to CC me). I believe that I have covered the large majority of recursive mutexes in the patch, but it's difficult to go through all the surrounding code. So, if I happened to have missed some, it would be good to modify the required mtx_init()s immediately, before further cleanups are done. Thanks, Bosko. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 22:28:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id A155337B698 for ; Thu, 18 Jan 2001 22:28:00 -0800 (PST) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au with ESMTP id RAA08935 for ; Fri, 19 Jan 2001 17:27:53 +1100 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.5.1.R) for ; Fri, 19 Jan 2001 17:27:38 +1100 Reply-To: From: "Chris Knight" To: Subject: sysinstall move and make release on FreeBSD-stable Date: Fri, 19 Jan 2001 17:27:36 +1100 Message-ID: <004301c081e0$eafc3af0$020aa8c0@aims.private> 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 CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Return-Path: chris@aims.com.au X-MDaemon-Deliver-To: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, Since the sysinstall move, make release on FreeBSD-stable (as of 3 hrs ago) breaks when building sysinstall. The output is: ===> usr.sbin/sysinstall cc -o rtermcap /usr/src/usr.sbin/sysinstall/rtermcap.c -ltermcap rm -f makedevs.tmp echo '#include ' > makedevs.tmp ./rtermcap ansi | file2c 'const char termcap_ansi[] = {' ',0};' >> makedevs.tmp /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found ./rtermcap cons25w | file2c 'const char termcap_cons25w[] = {' ',0};' >> makedevs.tmp /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found ./rtermcap cons25 | file2c 'const char termcap_cons25[] = {' ',0};' >> makedevs.tmp /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found ./rtermcap cons25-m | file2c 'const char termcap_cons25_m[] = {' ',0};' >> makedevs.tmp /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found ./rtermcap cons25r | file2c 'const char termcap_cons25r[] = {' ',0};' >> makedevs.tmp /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found ./rtermcap cons25r-m | file2c 'const char termcap_cons25r_m[] = {' ',0};' >> makedevs.tmp /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found ./rtermcap cons25l1 | file2c 'const char termcap_cons25l1[] = {' ',0};' >> makedevs.tmp /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found ./rtermcap cons25l1-m | file2c 'const char termcap_cons25l1_m[] = {' ',0};' >> makedevs.tmp /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found ./rtermcap vt100 | file2c 'const char termcap_vt100[] = {' ',0};' >> makedevs.tmp /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found ./rtermcap xterm | file2c 'const char termcap_xterm[] = {' ',0};' >> makedevs.tmp /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found then: cc -O -pipe -Wall -I/usr/src/usr.sbin/sysinstall/../../gnu/lib/libdialog -I. -I/usr/obj/usr/src/i386/usr/include -c makedevs.c makedevs.c:4: syntax error before `,' makedevs.c:7: syntax error before `,' makedevs.c:10: syntax error before `,' makedevs.c:13: syntax error before `,' makedevs.c:16: syntax error before `,' makedevs.c:19: syntax error before `,' makedevs.c:22: syntax error before `,' makedevs.c:25: syntax error before `,' makedevs.c:28: syntax error before `,' makedevs.c:31: syntax error before `,' I did a local hack to copy libc.so.5 into ${CHROOTDIR}/usr/lib before the chroot command, but this doesn't solve the problem properly. At the moment, it seems that current snapshots can only be built with current, and I'm not sure of the correct way to fix this for stable. I'm thinking the best way is to change the linking command for rtermcap in /usr/src/usr.sbin/sysinstall/Makefile relative to one of the environment variables set for the make release process. Not foolproof, but better than my hack :-) Also, the following commands added to ${CHROOTDIR}/mk are now dependent on where sysinstall in the release you're trying to build lives. cd /usr/src/release/sysinstall make obj They've been removed from /usr/src/release/Makefile v1.589, but aren't they still required if you're trying to build a 4.x release? Or am I missing the point? Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 23: 1:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id D0CA237B401; Thu, 18 Jan 2001 23:01:24 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0J71Bk09591; Thu, 18 Jan 2001 23:01:11 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101190701.f0J71Bk09591@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Soren Schmidt Cc: jhb@FreeBSD.ORG (John Baldwin), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <200101181525.QAA21260@freebsd.dk> Content-Transfer-Encoding: 8bit Date: Thu, 18 Jan 2001 23:01:11 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Peter Wemm wrote: > > > > Soren, can you retest a buildworld with the currently committed kernel > > with no other changes? Let us see if the forward_signal() stuff is the > > culprit, and if not, try adding just the i386/i386/machdep.c patch to HLT > > the idle CPU. (if *that* makes a difference then we have got trouble!) > > It seems that the HLT thing is exactly the patch that makes it work! > > So we have trouble, I said that all along .5 :) So, the difference between -current working for you or not is this: +++ machdep.c 2001/01/18 13:44:48 @@ -1005,6 +1005,10 @@ void cpu_idle(void) { +#ifdef SMP + /* first candidate for an interrupt */ + lapic.tpr = 0; +#endif #ifndef SMP if (cpu_idle_hlt) { disable_intr(); ?? No other changes? This is bad news.. This means we have races somewhere, or some other badness. 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 18 23:24:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from kumi.webnewslink.com (unknown [64.132.3.187]) by hub.freebsd.org (Postfix) with ESMTP id 4336D37B401; Thu, 18 Jan 2001 23:24:16 -0800 (PST) Received: from pc ([64.132.3.188]) by kumi.webnewslink.com (8.9.3/8.9.3) with SMTP id VAA18949; Thu, 18 Jan 2001 21:10:02 -1000 Date: Thu, 18 Jan 2001 21:10:02 -1000 From: ami@e-hiddencam.com Message-Id: <200101190710.VAA18949@kumi.webnewslink.com> To: ami@e-hiddencam.com Subject: NEWS MIME-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ‰Ä”ü‚Å‚·B —F’B‚ƈê‚ɃAƒ_ƒ‹ƒgƒTƒCƒg‚ðì‚è‚Ü‚µ‚½B Ž„‚ào‰‰‚µ‚Ä‚¢‚Ü‚·B ‚³‚­‚ç‚ÆŒ¾‚¤–¼‘O‚Åo‚Ä‚¢‚Ü‚·B ’T‚µ‚Ä‚Ý‚ÄAŠ´‘z‚Å‚à•·‚©‚¹‚ĉº‚³‚¢B ‰Ä”ü http://63.100.42.104/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ If you are under 18 years of age or if it is illegal to view adult material in your community, please erase this message. _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ ********************************************************** ‚±‚̃[ƒŠƒ“ƒOƒŠƒXƒg‚©‚çA‚ ‚È‚½‚Ì‚¨–¼‘O‚ð휂µ‚½‚¢ê‡‚ÍA Œ–¼‚ð"remove" ‚Æ‚µA‚±‚̃[ƒ‹‚É‚»‚Ì‚Ü‚Ü•ÔM‚µ‚Ä‚­‚¾‚³ ‚¢B‚æ‚낵‚­‚¨Šè‚¢‚µ‚Ü‚·B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 18 23:35:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B555937B401; Thu, 18 Jan 2001 23:35:32 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA60706; Fri, 19 Jan 2001 08:35:15 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101190735.IAA60706@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <200101190701.f0J71Bk09591@mobile.wemm.org> from Peter Wemm at "Jan 18, 2001 11:01:11 pm" To: peter@netplex.com.au (Peter Wemm) Date: Fri, 19 Jan 2001 08:35:14 +0100 (CET) Cc: jhb@FreeBSD.ORG (John Baldwin), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com 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 Peter Wemm wrote: > Soren Schmidt wrote: > > It seems Peter Wemm wrote: > > > > > > Soren, can you retest a buildworld with the currently committed kernel > > > with no other changes? Let us see if the forward_signal() stuff is the > > > culprit, and if not, try adding just the i386/i386/machdep.c patch to HLT > > > the idle CPU. (if *that* makes a difference then we have got trouble!) > > > > It seems that the HLT thing is exactly the patch that makes it work! > > > > So we have trouble, I said that all along .5 :) > > So, the difference between -current working for you or not is this: [diff snipped] > ?? No other changes? I need the FULL change to machdep.c and apparently the chagne to subr_prf.c is needed too, at least it hasnt broke yet with that in place too, not that I can see why it matters though. The new diff to machdep.c that jhb made yesterday also causes trouble. > This is bad news.. This means we have races somewhere, or some other badness. That is what I've been harping about for months... What strikes me here as a very serious problem is that the SMPng developers has told me over and over that it works fine for them on -current, but when we get to the matter after months of frustration, it suddenly appears that they are not running the same -current as the rest of us. Now guys, excuse my language, but that *sucks* bigtime. However I'm still running tests here, and I'm offering to test every patch you can come up with to help locate the problem, just as always... -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 19 0:23:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 3AC7937B402; Fri, 19 Jan 2001 00:23:30 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0J8N6k10282; Fri, 19 Jan 2001 00:23:06 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101190823.f0J8N6k10282@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Soren Schmidt Cc: jhb@FreeBSD.ORG (John Baldwin), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <200101190735.IAA60706@freebsd.dk> Content-Transfer-Encoding: 8bit Date: Fri, 19 Jan 2001 00:23:05 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Peter Wemm wrote: > > This is bad news.. This means we have races somewhere, or some other badne ss. > > That is what I've been harping about for months... > > What strikes me here as a very serious problem is that the SMPng developers > has told me over and over that it works fine for them on -current, but > when we get to the matter after months of frustration, it suddenly appears > that they are not running the same -current as the rest of us. > > Now guys, excuse my language, but that *sucks* bigtime. I *am* runnning unmodified SMPng kernels and dont see this problem. And those that have changes certainly dont have John's patches in them. > -Søren 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 Fri Jan 19 0:30: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id CBBBC37B401 for ; Fri, 19 Jan 2001 00:29:52 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0J8RCL75582; Fri, 19 Jan 2001 00:27:15 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <004301c081e0$eafc3af0$020aa8c0@aims.private> Date: Fri, 19 Jan 2001 00:29:28 -0800 (PST) From: John Baldwin To: Chris Knight Subject: RE: sysinstall move and make release on FreeBSD-stable Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jan-01 Chris Knight wrote: > Howdy, > > Since the sysinstall move, make release on FreeBSD-stable (as of 3 hrs ago) > breaks when building sysinstall. The output is: rtermcap needs to be a build-tool in world. The 4.x upgrade path is b0rked too. I think that file2c also needs to become a build-tool, I just haven't had time yet to sit down and test this on a 4.x box. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 0:31:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id B324137B698; Fri, 19 Jan 2001 00:31:27 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0J8RHL75590; Fri, 19 Jan 2001 00:27:17 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101190735.IAA60706@freebsd.dk> Date: Fri, 19 Jan 2001 00:29:34 -0800 (PST) From: John Baldwin To: Soren Schmidt Subject: Re: HEADS-UP: await/asleep removal imminent Cc: rjesup@wgate.com, arch@FreeBSD.org, current@FreeBSD.org, (Alfred Perlstein) , (Peter Wemm) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jan-01 Soren Schmidt wrote: > It seems Peter Wemm wrote: >> Soren Schmidt wrote: >> > It seems Peter Wemm wrote: >> > > >> > > Soren, can you retest a buildworld with the currently committed kernel >> > > with no other changes? Let us see if the forward_signal() stuff is the >> > > culprit, and if not, try adding just the i386/i386/machdep.c patch to >> > > HLT >> > > the idle CPU. (if *that* makes a difference then we have got trouble!) >> > >> > It seems that the HLT thing is exactly the patch that makes it work! >> > >> > So we have trouble, I said that all along .5 :) >> >> So, the difference between -current working for you or not is this: > > [diff snipped] > >> ?? No other changes? > > I need the FULL change to machdep.c and apparently the chagne to subr_prf.c > is needed too, at least it hasnt broke yet with that in place too, not > that I can see why it matters though. > > The new diff to machdep.c that jhb made yesterday also causes trouble. > >> This is bad news.. This means we have races somewhere, or some other >> badness. That my other diff didn't work is more bad news. > That is what I've been harping about for months... > > What strikes me here as a very serious problem is that the SMPng developers > has told me over and over that it works fine for them on -current, but > when we get to the matter after months of frustration, it suddenly appears > that they are not running the same -current as the rest of us. This is _not_ true. My quad xeon test box runs a pure source tree, and has not had a single problem building many worlds and releases since the fix to atomic_store_rel_ptr(). Also, I rebuilt a fresh kernel from a freshly checked out tree without any patches today on mutex (the machine I built kernel.sos on) and that kernel has built worlds today without _any_ lockups. In fact, smp_hlt.patch is only something I've played with a bit for the last few weeks, and it doesn't really work anyways, as you can end up with CPU's staying in the HLT state for long periods of time even though there are runnable jobs, which is why I haven't bothered committing this. Can you post a dmesg of your box? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 0:34:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 99B8937B404; Fri, 19 Jan 2001 00:34:12 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0J8YCl81453; Fri, 19 Jan 2001 09:34:12 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: Soren Schmidt , rjesup@wgate.com, arch@FreeBSD.ORG, current@FreeBSD.ORG, bright@wintelcom.net (Alfred Perlstein), peter@netplex.com.au (Peter Wemm) Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: Your message of "Fri, 19 Jan 2001 00:29:34 PST." Date: Fri, 19 Jan 2001 09:34:12 +0100 Message-ID: <81448.979893252@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Baldwin writes: > >This is _not_ true. My quad xeon test box runs a pure source tree, and has not >had a single problem building many worlds and releases since the fix to >atomic_store_rel_ptr(). How many disks are active when you build world on that box ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 0:43:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 4104537B402; Fri, 19 Jan 2001 00:43:30 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0J8ctL75908; Fri, 19 Jan 2001 00:38:55 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <81448.979893252@critter> Date: Fri, 19 Jan 2001 00:41:12 -0800 (PST) From: John Baldwin To: Poul-Henning Kamp Subject: Re: HEADS-UP: await/asleep removal imminent Cc: (Peter Wemm) , (Alfred Perlstein) , current@FreeBSD.org, arch@FreeBSD.org, rjesup@wgate.com, Soren Schmidt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jan-01 Poul-Henning Kamp wrote: > In message , John Baldwin writes: >> >>This is _not_ true. My quad xeon test box runs a pure source tree, and has >>not >>had a single problem building many worlds and releases since the fix to >>atomic_store_rel_ptr(). > > How many disks are active when you build world on that box ? Just one. I don't have any boxes actually with lots of disks in them. Details like this would be helpful though. I'll see if I can't find someone to rummage together a vinum stripe to build on or some such. However, after thinking some more, even in a preemptive kernel, Giant will protect against the *strategy() race you brought up, because we won't get a context switch in kernel mode that releases Giant until either we exit the kernel or we call tsleep(). The interrupt handler will block on Giant when its thread runs, so it won't run until the top half finishes and returns. Does that make sense? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 0:46: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id AA72137B698; Fri, 19 Jan 2001 00:45:41 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0J8jfl82883; Fri, 19 Jan 2001 09:45:42 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: peter@netplex.com.au (Peter Wemm), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.org, arch@FreeBSD.org, rjesup@wgate.com, Soren Schmidt Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: Your message of "Fri, 19 Jan 2001 00:41:12 PST." Date: Fri, 19 Jan 2001 09:45:41 +0100 Message-ID: <82881.979893941@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Baldwin writes: >> >> How many disks are active when you build world on that box ? > >Just one. [...] >Details like this would be helpful though. They have never been secret, and I voiced this issue early on. > However, after >thinking some more, even in a preemptive kernel, Giant will protect against the >*strategy() race you brought up, [...] Could be. Many disks are still a defining difference on sos's machine and practically everybody any other machine. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 0:53:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id C8A9737B69B; Fri, 19 Jan 2001 00:52:59 -0800 (PST) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f0J8qXa03100; Fri, 19 Jan 2001 10:52:38 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.1/8.9.3) with ESMTP id f0J8qWr09817; Fri, 19 Jan 2001 10:52:32 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A68004F.D490D0D2@FreeBSD.org> Date: Fri, 19 Jan 2001 10:52:31 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John Baldwin Cc: Chris Knight , current@FreeBSD.org Subject: Re: sysinstall move and make release on FreeBSD-stable References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > On 19-Jan-01 Chris Knight wrote: > > Howdy, > > > > Since the sysinstall move, make release on FreeBSD-stable (as of 3 hrs ago) > > breaks when building sysinstall. The output is: > > rtermcap needs to be a build-tool in world. The 4.x upgrade path is b0rked > too. I think that file2c also needs to become a build-tool, I just haven't had > time yet to sit down and test this on a 4.x box. Slightly OT, but could we have a flag to disable building sysinstall during make world? It's hardly a tool that is required for day-to-day operation, so in most cases it will only waste considerable amount of root partitition. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 1: 4:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 83AF137B699; Fri, 19 Jan 2001 01:03:49 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA81774; Fri, 19 Jan 2001 10:03:47 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101190903.KAA81774@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <81448.979893252@critter> from Poul-Henning Kamp at "Jan 19, 2001 09:34:12 am" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Fri, 19 Jan 2001 10:03:47 +0100 (CET) Cc: jhb@FreeBSD.ORG (John Baldwin), rjesup@wgate.com, arch@FreeBSD.ORG, current@FreeBSD.ORG, bright@wintelcom.net (Alfred Perlstein), peter@netplex.com.au (Peter Wemm) 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 Poul-Henning Kamp wrote: > In message , John Baldwin writes: > > > >This is _not_ true. My quad xeon test box runs a pure source tree, and has not > >had a single problem building many worlds and releases since the fix to > >atomic_store_rel_ptr(). > > How many disks are active when you build world on that box ? And on how many controllers/interrupts ? -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 19 2:50:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 4FFF537B69D; Fri, 19 Jan 2001 02:50:22 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0JAm0L77613; Fri, 19 Jan 2001 02:48:00 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A68004F.D490D0D2@FreeBSD.org> Date: Fri, 19 Jan 2001 02:50:18 -0800 (PST) From: John Baldwin To: Maxim Sobolev Subject: Re: sysinstall move and make release on FreeBSD-stable Cc: current@FreeBSD.org, Chris Knight Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jan-01 Maxim Sobolev wrote: > John Baldwin wrote: > >> On 19-Jan-01 Chris Knight wrote: >> > Howdy, >> > >> > Since the sysinstall move, make release on FreeBSD-stable (as of 3 hrs >> > ago) >> > breaks when building sysinstall. The output is: >> >> rtermcap needs to be a build-tool in world. The 4.x upgrade path is b0rked >> too. I think that file2c also needs to become a build-tool, I just haven't >> had >> time yet to sit down and test this on a 4.x box. > > Slightly OT, but could we have a flag to disable building sysinstall during > make > world? It's hardly a tool that is required for day-to-day operation, so in > most > cases it will only waste considerable amount of root partitition. Umm, it's installed in /usr/sbin: -r-xr-xr-x 1 root wheel 369592 Jan 17 11:49 /usr/sbin/sysinstall -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 3:33:15 2001 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 2A1E737B400; Fri, 19 Jan 2001 03:32:58 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA52701; Fri, 19 Jan 2001 12:32:54 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: cjclark@alum.mit.edu Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname References: <200101190330.f0J3UPa75677@rfx-216-196-73-168.users.reflexcom.com> From: Dag-Erling Smorgrav Date: 19 Jan 2001 12:32:53 +0100 In-Reply-To: cjclark@reflexcom.com's message of "Thu, 18 Jan 2001 19:30:25 -0800 (PST)" Message-ID: Lines: 11 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 cjclark@reflexcom.com writes: > I propose that syslogd(8) should reload the hostname with a > SIGHUP. I cannot think of any reason that one should not update the > hostname, but as I pointed out, there are reasons why one would want > that behavior. It should also log a message if the hostname changes. DES -- Dag-Erling Smorgrav - des@ofug.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 19 3:48: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1F02E37B400; Fri, 19 Jan 2001 03:47:35 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA20267; Fri, 19 Jan 2001 12:47:32 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101191147.MAA20267@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: from John Baldwin at "Jan 19, 2001 00:29:34 am" To: jhb@FreeBSD.org (John Baldwin) Date: Fri, 19 Jan 2001 12:47:32 +0100 (CET) Cc: rjesup@wgate.com, arch@FreeBSD.org, current@FreeBSD.org, bright@wintelcom.net, peter@netplex.com.au 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 John Baldwin wrote: > > Can you post a dmesg of your box? Sure, attached the dmesg from the system that is worst affected: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #6: Thu Jan 18 21:39:51 CET 2001 sos@test.freebsd.dk:/u1/src/sys/compile/TEST Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (910.36-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 536850432 (524268K bytes) avail memory = 518602752 (506448K bytes) Changing APIC ID for IO APIC #1 from 3 to 1 in MP table Changing APIC ID for IO APIC #1 from 3 to 1 on chip Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 16 pins in IOAPIC #1 IOAPIC #1 intpin 0 -> irq 5 IOAPIC #1 intpin 1 -> irq 6 IOAPIC #1 intpin 4 -> irq 2 IOAPIC #1 intpin 8 -> irq 11 IOAPIC #1 intpin 9 -> irq 12 IOAPIC #1 intpin 14 -> irq 10 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 3, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 1, version: 0x000f0011, at 0xfec01000 Preloaded elf kernel "kernel" at 0xc03f3000. Preloaded elf module "random.ko" at 0xc03f309c. Pentium Pro MTRR support enabled Using $PIR table, 11 entries at 0xc00f0cb0 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 fxp0: port 0xd800-0xd83f mem 0xfd800000-0xfd8fffff,0xfe000000-0xfe000fff irq 2 at device 2.0 on pci0 fxp0: Ethernet address 00:e0:18:00:c8:15 atapci0: port 0xb000-0xb0ff,0xb400-0xb403,0xb800-0xb807,0xd000-0xd003,0xd400-0xd407 irq 5 at device 3.0 on pci0 ata2: at 0xd400 on atapci0 ata3: at 0xb800 on atapci0 atapci1: port 0x9400-0x94ff,0x9800-0x9803,0xa000-0xa007,0xa400-0xa403,0xa800-0xa807 irq 6 at device 4.0 on pci0 ata4: at 0xa800 on atapci1 ata5: at 0xa000 on atapci1 pci0: at 7.0 (no driver attached) isab0: at device 15.0 on pci0 isa0: on isab0 atapci2: port 0x8800-0x880f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci2 ata1: at 0x170 irq 15 on atapci2 ohci0: mem 0xfb000000-0xfb000fff irq 10 at device 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (unknown) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib1: at pcibus 1 on motherboard pci1: on pcib1 pci1: at 5.0 (no driver attached) pci1: at 5.1 (no driver attached) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff 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: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 ad0: 8063MB [16383/16/63] at ata0-master UDMA33 ar0: 146617MB [18691/255/63] subdisks: ad4: 73308MB [148945/16/63] at ata2-master UDMA100 ad6: 73308MB [148945/16/63] at ata3-master UDMA100 ar1: 146617MB [18691/255/63] subdisks: ad10: 73308MB [148945/16/63] at ata5-master UDMA100 ad8: 73308MB [148945/16/63] at ata4-master UDMA100 acd0: DVD-RAM at ata0-slave using PIO4 acd1: CD-RW at ata1-slave using PIO4 Mounting root from ufs:/dev/ad0a SMP: AP CPU #1 Launched! -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 19 4:16:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mgate05.so-net.ne.jp (mgate05.so-net.ne.jp [210.139.254.152]) by hub.freebsd.org (Postfix) with ESMTP id 48C9237B400 for ; Fri, 19 Jan 2001 04:16:37 -0800 (PST) Received: from mail.ya3.so-net.ne.jp (mspool11.so-net.ne.jp [210.139.248.11]) by mgate05.so-net.ne.jp (8.8.8+3.0Wbeta9/3.6W00122022) with ESMTP id VAA02655 for ; Fri, 19 Jan 2001 21:16:35 +0900 (JST) Received: from localhost (p84ea60.ykh2.ap.so-net.ne.jp [210.132.234.96]) by mail.ya3.so-net.ne.jp (8.9.3/3.7W99092111) with ESMTP id VAA10168 for ; Fri, 19 Jan 2001 21:16:34 +0900 (JST) To: current@FreeBSD.org Subject: adduser and /etc/auth.conf From: Yoshihiro Koya X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010119211923R.ipfw@ya3.so-net.ne.jp> Date: Fri, 19 Jan 2001 21:19:23 +0900 X-Dispatcher: imput version 990905(IM130) Lines: 43 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, The current default /etc/auth.conf is as follows: ---------- # # $FreeBSD: src/etc/auth.conf,v 1.5 2000/12/28 10:32:00 peter Exp $ # # This file contains information on what types of authentication to use. # It is just the beginnings of a greater scheme. # crypt_default = md5 des # auth_list = passwd kerberos auth_list = passwd ---------- On the other hand, the current default /etc/login.conf looks like: ---------- # login.conf - login class capabilities database. # (snip) default:\ :passwd_format=md5:\ :copyright=/etc/COPYRIGHT:\ :welcome=/etc/motd:\ (snip) ---------- This will cause a problem. A new user registered by adduser(1) will be able to loggin the system. Because the adduser script uses des as the default according to the setting in /etc/auth.conf and crypt_set_format(3) in passwd(1) sets md5 as the default hash function, the authentication will fail always. Of course, it is easy to change one of the above files. It might be, however, quite difficult to guess the reason of the login failure caused by this. I think that it might be convenient to describe this in some documents like UPDATING or a manpage of adduser(1) of -current. koya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 5:35:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from tfrsolcom.transfer-solutions.com (mail.transfer-solutions.com [195.109.218.250]) by hub.freebsd.org (Postfix) with ESMTP id E817337B400; Fri, 19 Jan 2001 05:35:08 -0800 (PST) Received: by mail.transfer-solutions.com with Internet Mail Service (5.5.2650.21) id ; Fri, 19 Jan 2001 14:29:12 +0100 Received: from tfrsolcom.transfer-solutions.com (localhost [127.0.0.1]) by tfrsolcom.transfer-solutions.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id DAATSSWL; Fri, 19 Jan 2001 14:26:03 +0100 Received: from 193.100.100.198 by tfrsolcom.transfer-solutions.com (InterScan E-Mail VirusWall NT); Fri, 19 Jan 2001 14:25:58 +0100 (Romance Standard Time) From: Rogier Mulhuijzen To: freebsd-current@freebsd.org Cc: John Baldwin Message-Id: <5.0.2.1.0.20010119135940.00a565d0@tfrsolcom> X-Sender: rmulhuij@tfrsolcom X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Fri, 19 Jan 2001 14:37:20 +0100 Subject: NTFS issue (was: Panic w/crash dump (looks like atomic.h problem)) In-Reply-To: References: <5.0.2.1.0.20010118201134.00a542c0@tfrsolcom> 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 a quick look at kldstat output pinpointed the ??'s in my stacktrace(see previous posts) to ntfs.ko. Compiled NTFS into my kernel and reproduced the crash. Taking a look at the trace now: #11 0xc01c0c97 in vref (vp=0x0) at machine/atomic.h:332 #12 0xc0239592 in ntfs_vgetex (mp=0xc0f7dc00, ino=4458, attrtype=128, attrname=0x0, lkflags=2, flags=4, p=0xc8d82640, vpp=0xc7f85db8) at ../../ntfs/ntfs_vfsops.c:987 #13 0xc0235a0b in ntfs_ntvattrget (ntmp=0xc0f7da00, ip=0xc1043000, type=128, name=0xc02c3fe8 "", vcn=0, vapp=0xc7f85e3c) at ../../ntfs/ntfs_subr.c:231 #14 0xc0238134 in ntfs_readattr (ntmp=0xc0f7da00, ip=0xc1043000, attrnum=128, attrname=0x0, roff=1644032, rsize=512, rdata=0x0, uio=0xc7f85ee4) at ../../ntfs/ntfs_subr.c:1699 #15 0xc02396c5 in ntfs_read (ap=0xc7f85e9c) at ../../ntfs/ntfs_vnops.c:184 #16 0xc01c91e4 in vn_read (fp=0xc103e540, uio=0xc7f85ee4, cred=0xc1024600, flags=0, p=0xc8d82640) at vnode_if.h:279 I took a look at the code in src/sys/ntfs/ntfs_vfsops.c I compared the code surrounding VREF there with code in other FS drivers. in ntfs/ntfs_vfsops.c if (lkflags & LK_TYPE_MASK) { error = VN_LOCK(vp, lkflags, p); if (error) { vput(vp); return (error); } } VREF(ip->i_devvp); in isofs/cd9660/cd9660_vfsops.c } else bp = 0; ip->i_mnt = imp; ip->i_devvp = imp->im_devvp; VREF(ip->i_devvp); in ufs/ffs/ffs_vfsops.c /* * Finish inode initialization now that aliasing has been resolved. */ ip->i_devvp = ump->um_devvp; VREF(ip->i_devvp); in ufs/ifs/ifs_vfsops.c /* * Finish inode initialization now that aliasing has been resolved. */ ip->i_devvp = ump->um_devvp; VREF(ip->i_devvp); Seeing this I added a check to see if ip->i_devvp was equal to ntmp->ntm_devvp. And a check to see if it was 0. During normal operation on my NTFS partition I got no messages, so I took a bold step and added 'ip->i_devvp = ntmp->ntm_devvp;' just before the VREF call. After installing new kernel and reboot I once again started playback of an mp3 on my NTFS partition and started make -j 128 world on my UFS partition. And 'lo behold, every time I got a message that ip->i_devvp was equal not to ntmp->ntm_devvp, ip->i_devvp was equal to 0. I can now stress the hell out of my box and the NTFS filesystem, and it keeps running. Why exactly ip->i_devvp is 0 I don't know, I have to dig into the code some deeper, but every other FS that uses VREF copies it from their mountpoint structure before calling vref(). Am I on the right track here? DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 5:39:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.clones.com (unknown [216.70.178.182]) by hub.freebsd.org (Postfix) with ESMTP id AD9A537B400; Fri, 19 Jan 2001 05:39:35 -0800 (PST) Received: from localhost (gross@localhost) by mail.clones.com (8.9.3/8.9.3) with ESMTP id FAA07315; Fri, 19 Jan 2001 05:40:16 -0800 Date: Fri, 19 Jan 2001 05:40:15 -0800 (PST) From: Glendon Gross To: Mike Smith Cc: Will Andrews , FreeBSD Current Subject: Re: HEADS UP: I386_CPU In-Reply-To: <200101181944.f0IJiIQ00677@mass.osd.bsdi.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 Just out of curiousity, has anyone documented how much of a performance hit there is with the i386 code enabled in the kernel? Regards, Glen Gross On Thu, 18 Jan 2001, Mike Smith wrote: > > > That's one of the big reasons that we're 4.x based right now rather > > > than 3.x based, despite 4.x's slightly larger memory footprint. That > > > and 4.x's much better c++ compiler. > > > > Well, Warner, I've never done embedded systems. So, tell me, do they > > actually use any C++ code in embedded systems? C++ has a rather high > > overhead as far as disk space & memory goes. I would imagine that 99%+ > > of embedded systems do not use C++ code except perhaps for a very small > > amount of the code. > > You have a very vivid imagination. > > Unfortunately, imagination isn't very helpful here; the whole idea is to > do stuff that's actually useful, not just what we'd imagine might be > useful. And in that regard, a *lot* of application programming (which > includes programming for embedded systems) is done using c++ compilers. > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 19 9:48: 3 2001 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 39B8637B402; Fri, 19 Jan 2001 09:47:42 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id EAA32665; Sat, 20 Jan 2001 04:47:35 +1100 Date: Sat, 20 Jan 2001 04:48:03 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: Poul-Henning Kamp , peter@netplex.com.au, bright@wintelcom.net, current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com, Soren Schmidt Subject: Re: HEADS-UP: await/asleep removal imminent 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, 19 Jan 2001, John Baldwin wrote: > rummage together a vinum stripe to build on or some such. However, after > thinking some more, even in a preemptive kernel, Giant will protect against the > *strategy() race you brought up, because we won't get a context switch in > kernel mode that releases Giant until either we exit the kernel or we call > tsleep(). The interrupt handler will block on Giant when its thread runs, so > it won't run until the top half finishes and returns. Does that make sense? This would be a bug in the preemptive kernel. To work as well as old kernels, everything that was not run because of a lock must be run when the lock is released. This corresponds to splx() running all software interrupt handlers that became runnable. 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 19 10:53:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 92B1F37B402; Fri, 19 Jan 2001 10:52:56 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0JIn4L85589; Fri, 19 Jan 2001 10:49:05 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 19 Jan 2001 10:51:27 -0800 (PST) From: John Baldwin To: Bruce Evans Subject: Re: HEADS-UP: await/asleep removal imminent Cc: Soren Schmidt , rjesup@wgate.com, arch@FreeBSD.org, current@FreeBSD.org, bright@wintelcom.net, peter@netplex.com.au, Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jan-01 Bruce Evans wrote: > On Fri, 19 Jan 2001, John Baldwin wrote: > >> rummage together a vinum stripe to build on or some such. However, after >> thinking some more, even in a preemptive kernel, Giant will protect against >> the >> *strategy() race you brought up, because we won't get a context switch in >> kernel mode that releases Giant until either we exit the kernel or we call >> tsleep(). The interrupt handler will block on Giant when its thread runs, >> so >> it won't run until the top half finishes and returns. Does that make sense? > > This would be a bug in the preemptive kernel. To work as well as old > kernels, everything that was not run because of a lock must be run when > the lock is released. This corresponds to splx() running all software > interrupt handlers that became runnable. I don't think we need to emulate every possible race condition of the old kernel. :) Eventually, what you ask _will_ be done because when we release a mutex, we make a process blocked on it runnable again, and if the new process has higher prioriry than the currnet priority. When you combine this with priority propagation, it will actually all work the way you want. It is just a more generic way of doing it since now any mtx_exit() of a sleep lock can effect this change, whereas before only splx() could effect this change. > Bruce -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 11: 4: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 6268937B400; Fri, 19 Jan 2001 11:03:50 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Fri, 19 Jan 2001 11:02:00 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0JJ3k708040; Fri, 19 Jan 2001 11:03:46 -0800 (PST) (envelope-from cjc) Date: Fri, 19 Jan 2001 11:03:41 -0800 From: "Crist J. Clark" To: Dag-Erling Smorgrav Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname Message-ID: <20010119110341.A7958@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <200101190330.f0J3UPa75677@rfx-216-196-73-168.users.reflexcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from des@ofug.org on Fri, Jan 19, 2001 at 12:32:53PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: > cjclark@reflexcom.com writes: > > I propose that syslogd(8) should reload the hostname with a > > SIGHUP. I cannot think of any reason that one should not update the > > hostname, but as I pointed out, there are reasons why one would want > > that behavior. > > It should also log a message if the hostname changes. Should that be a responsibility of syslogd(8) or hostname(1)? Personally, it might be a slippery slope to start adding things that syslogd(8) should maintain state on, but since syslogd(8) actually uses the hostname... One also could start arguing that syslogd(8) should check the hostname everytime it logs something despite the performance hit. As for what syslogd(8) does now, if you look at the example output in the PR, notice syslogd(8) didn't even log when it was HUP'ed. IMHO, I think it is beyond the scope of syslogd(8) to actually track changes in the hostname in real-time. Noticing a change when given a HUP signal, would seem reasonable, but if hostname(1) were to log changes, that would also be fairly redundant. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 12:50:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from gypsy.vrac.iastate.edu (gypsy.vrac.iastate.edu [129.186.232.122]) by hub.freebsd.org (Postfix) with ESMTP id 0C28F37B404 for ; Fri, 19 Jan 2001 12:50:11 -0800 (PST) Received: from tomservo.vrac.iastate.edu (tomservo.vrac.iastate.edu [129.186.232.121]) by gypsy.vrac.iastate.edu (Postfix) with ESMTP id E3982FD for ; Fri, 19 Jan 2001 14:50:10 -0600 (CST) Received: from tomservo.vrac.iastate.edu (localhost [127.0.0.1]) by tomservo.vrac.iastate.edu (Postfix) with ESMTP id 3125C5E16 for ; Fri, 19 Jan 2001 14:50:10 -0600 (CST) To: freebsd-current@freebsd.org Subject: Re: cvs commit: src/gnu/usr.bin/cc/cccp Makefile In-reply-to: "Wed, 03 Jan 2001 18:16:24 PST." <200101040216.f042GO305899@freefall.freebsd.org> Date: Fri, 19 Jan 2001 14:50:10 -0600 From: Patrick Hartling Message-Id: <20010119205010.3125C5E16@tomservo.vrac.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I remove the old /usr/libexec/cpp with a newer cpp0 installed, 'make world' fails with the following: -------------------------------------------------------------- >>> stage 4: populating /usr/obj/usr/src/i386/usr/include -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 SHARED=symlinks includes cd /usr/src/include; make -B all install creating osreldate.h from newvers.sh setvar PARAMFILE /usr/src/include/../sys/sys/param.h; . /usr/src/include/../sys/conf/newvers.sh; echo "$COPYRIGHT" > osreldate.h; echo \#'undef __FreeBSD_version' >> osreldate.h; echo \#'define __FreeBSD_version' $RELDATE >> osreldate.h ===> rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h rpcgen: cannot find any C preprocessor (cpp) *** Error code 1 Stop in /usr/src/include/rpcsvc. *** Error code 1 Stop in /usr/src/include. *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error Should other tools be updated to use cpp0 as a result of the change below? -Patrick "David E. O'Brien" wrote: } obrien 2001/01/03 18:16:24 PST } } Modified files: } gnu/usr.bin/cc/cccp Makefile } Log: } The preprocessor used by the `cc' driver is now named `ccp0' to make it } clear this is the 1st pass of compilation and to make clear this particular } cpp is for `cc's use only. } } Revision Changes Path } 1.17 +2 -2 src/gnu/usr.bin/cc/cccp/Makefile } } } } To Unsubscribe: send mail to majordomo@FreeBSD.org } with "unsubscribe cvs-all" in the body of the message Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 14:40:23 2001 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 E7B4237B400; Fri, 19 Jan 2001 14:40:04 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id XAA55181; Fri, 19 Jan 2001 23:09:25 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: cjclark@alum.mit.edu Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname References: <200101190330.f0J3UPa75677@rfx-216-196-73-168.users.reflexcom.com> <20010119110341.A7958@rfx-216-196-73-168.users.reflex> From: Dag-Erling Smorgrav Date: 19 Jan 2001 23:09:24 +0100 In-Reply-To: "Crist J. Clark"'s message of "Fri, 19 Jan 2001 11:03:41 -0800" Message-ID: Lines: 12 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 "Crist J. Clark" writes: > On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: > > It should also log a message if the hostname changes. > Should that be a responsibility of syslogd(8) or hostname(1)? I meant syslogd(8), but putting it in hostname(1) might makes sense, except that hostname(1) is not the only way to set the hostname ('sysctl -w kern.hostname=foo' is another) DES -- Dag-Erling Smorgrav - des@ofug.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 19 16:33:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from net2.gendyn.com (nat2.gendyn.com [204.60.171.12]) by hub.freebsd.org (Postfix) with ESMTP id 2C85C37B401; Fri, 19 Jan 2001 16:33:34 -0800 (PST) Received: from [153.11.109.12] (helo=fatboy.clc.gdeb.com) by net2.gendyn.com with esmtp (Exim 2.12 #1) id 14Jly3-000Fqc-00; Fri, 19 Jan 2001 19:33:19 -0500 Received: from vigrid.com (localhost [127.0.0.1]) by fatboy.clc.gdeb.com (8.11.0/8.9.3) with ESMTP id f0K0c0O92335; Fri, 19 Jan 2001 19:38:01 -0500 (EST) (envelope-from eischen@vigrid.com) Message-ID: <3A68DDE8.7F8D3C51@vigrid.com> Date: Fri, 19 Jan 2001 19:38:00 -0500 From: Daniel Eischen X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: arch@freebsd.org Cc: current@freebsd.org Subject: Request For Review: libc/libc_r changes to allow -lc_r Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Followups to -arch only please ] I've got some changes to libc and libc_r that I'd like reviewed. These changes eliminate the _THREAD_SAFE macro and allow a libc and libc_r that can be linked together via -lc_r. This also means that -pthread and -D_THREAD_SAFE can be deprecated. Note that libc_r could be now be renamed libpthread, but I would like to reserve that for KSE Project development where we might want to have both libraries around while libpthread (using KSEs) is being developed. The diffs are posted at: http://people.freebsd.org/~deischen/libc.diffs http://people.freebsd.org/~deischen/libc_r.diffs The libc diffs include src/include, src/lib/libc, as well as src/usr.sbin/pppctl (our only threaded app) changes, whereas the libc_r diffs are just those changes to src/lib/libc_r. I've tested these changes with ACE, but still have other testing that I'll be doing over the weekend. The patches have also survived a buildworld, but the installworld will have to wait for this weekend. If you try these patches make sure you save a copy of libc.so.5 just in case... And BTW, many thanks to John Polstra for explaining some of the issues involved with linking :-) Overview of the changes ----------------------- For those not familiar with our current libc_r, it is currently built to include a thread-safe libc as well as the POSIX threads routines. On the other hand, libc is built to be non-thread safe. This differs from other OSs and from what POSIX mandates and means that we require non-standard hacks like the linker option -pthread (which links to libc_r and prevents linking to libc). System calls that need to be wrapped (HIDDEN_SYSCALLS) are now defined in libc/Makefile instead of libc_r/Makefile. This means that libc now contains: _thread_sys_foo - actual syscall _foo - weak definition to _thread_sys_foo foo - weak definition to _thread_sys_foo I've changed all the instances of foo() to _foo() in libc for those hidden system calls. Anyone modifying or adding to libc will have to be careful to use the same conventions. In order to define the prototypes for _foo(), we introduce namespace.h and un-namespace.h. BDE suggested this as a way to define the prototypes for the hidden system calls. Use them as follows: #include "namespace.h" #include /* Other standard includes... */ #include "un-namespace.h" /* * DB contains the member 'close' which is defined to * _close if included before un-namespace.h */ #include /* Other local includes... */ int somelibcfunc(int fd, void *buf, size_t len) { ... ret = (int)_read(fd, buf, len); ... return (ret); } Including namespace.h will define those hidden system calls used within libc from foo to _foo; un-namespace.h will undefine them. A few others are defined as well, such as _pthread_mutex_lock and friends. This allows libc_r to provide replacement functions for them if it is also linked in. One note about lib/libc/stdio/mktemp.c. This file really wants to use namespace.h but can't because it is used in building part of the C compiler (or something like that; the error has long since scrolled off my window). There are basically only two changes to libc_r. One is to implement the pthread_foo() functions as _pthread_foo() and make pthread_foo a weak definition to _pthread_foo. This allows an application to have it's own pthread_foo(). I noticed Solaris does this to libpthread as well as to libc. The other change to libc_r is to eliminate references to the global _thread_run and replace them with a function call to get the currently running thread (which will be needed for the KSE project). Yes, I could do something like errno, but that wouldn't encourage getting the running thread once and caching it. Comments welcome, -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 17:20:21 2001 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 6F09E37B400 for ; Fri, 19 Jan 2001 17:20:03 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id CAA56201; Sat, 20 Jan 2001 02:20:02 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: current@freebsd.org Subject: ^T at the serial console causes a panic From: Dag-Erling Smorgrav Date: 20 Jan 2001 02:20:01 +0100 Message-ID: Lines: 29 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 lopanic: mutex_enter(sio:1, MTX_SPIN) out of order @ ../../isa/sio.c:2585 already holding sched lock:2 cpuid = 0; lapic.id = 00000000 Debugger("panic") d CPU0 stopping CPUs: 0x00000002... stopped. Stopped at Debugger+0x45: pushl %ebx db> trace Debugger(c0231e61) at Debugger+0x45 panic(c0230d20,c0252ed3,1,c0252fa3,a19) at panic+0xa5 witness_enter(c029ad60,1,c0252fa3,a19) at witness_enter+0xe5 comstart(c2924300,d4359df8,c0178f7d,c2924300,20) at comstart+0x86 ttstart(c2924300,20,c2924300,2,c2924300) at ttstart+0x18 tputchar(20,c2924300) at tputchar+0x45 putchar(20,d4359ec8) at putchar+0x4f kvprintf(c0235e81,c016f5c0,d4359ec8,a,d4359ee4) at kvprintf+0x8e ttyprintf(c2924300,c0235e80,d3f47b38,515,c0235e71) at ttyprintf+0x2b ttyinfo(c2924300) at ttyinfo+0x157 ttyinput(14,c2924300) at ttyinput+0x591 sioinput(c108a000) at sioinput+0x2a4 siopoll(0) at siopoll+0x19b sithd_loop(0) at sithd_loop+0xa0 fork_trampoline() at fork_trampoline+0x61 I can't get a dump on this box (it double-faults every time I try), but if anyone needs more info I can probably easily reproduce it. DES -- Dag-Erling Smorgrav - des@ofug.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 19 18:50:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 4E77137B401; Fri, 19 Jan 2001 18:50:14 -0800 (PST) Received: by relay.butya.kz (Postfix, from userid 1000) id D3F2528D9F; Sat, 20 Jan 2001 08:50:09 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id C34A028CD6; Sat, 20 Jan 2001 08:50:09 +0600 (ALMT) Date: Sat, 20 Jan 2001 08:50:09 +0600 (ALMT) From: Boris Popov To: Rogier Mulhuijzen Cc: freebsd-current@freebsd.org, John Baldwin Subject: Re: NTFS issue (was: Panic w/crash dump (looks like atomic.h problem)) In-Reply-To: <5.0.2.1.0.20010119135940.00a565d0@tfrsolcom> 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, 19 Jan 2001, Rogier Mulhuijzen wrote: > During normal operation on my NTFS partition I got no messages, so I took a > bold step and added 'ip->i_devvp = ntmp->ntm_devvp;' just before the VREF call. You're absolutely right here. This line definitely should be presented in the code. > Am I on the right track here? Yes, thanks :) -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 19:24:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id E686037B401; Fri, 19 Jan 2001 19:24:15 -0800 (PST) Received: by relay.butya.kz (Postfix, from userid 1000) id 1012628D9F; Sat, 20 Jan 2001 09:24:14 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 013C728CD6; Sat, 20 Jan 2001 09:24:13 +0600 (ALMT) Date: Sat, 20 Jan 2001 09:24:13 +0600 (ALMT) From: Boris Popov To: Rogier Mulhuijzen Cc: freebsd-current@freebsd.org, John Baldwin Subject: Re: NTFS issue (was: Panic w/crash dump (looks like atomic.h problem)) 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, 20 Jan 2001, Boris Popov wrote: > On Fri, 19 Jan 2001, Rogier Mulhuijzen wrote: > > > During normal operation on my NTFS partition I got no messages, so I took a > > bold step and added 'ip->i_devvp = ntmp->ntm_devvp;' just before the VREF call. > > You're absolutely right here. This line definitely should be > presented in the code. Hmm, scratch this. This field initialized when ntnode is born and it should be valid while ntnode is alive (I've looked at the wrong place first time). This probably caused by vnode or ntnode being recycled due to a locking problem or missing reference. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 22:24:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from edgemaster.zombie.org (edgemaster.creighton.edu [147.134.107.69]) by hub.freebsd.org (Postfix) with ESMTP id 3C76F37B401 for ; Fri, 19 Jan 2001 22:24:19 -0800 (PST) Received: by edgemaster.zombie.org (Postfix, from userid 1001) id 871D698F8; Sat, 20 Jan 2001 00:24:18 -0600 (CST) Date: Sat, 20 Jan 2001 00:24:18 -0600 From: Sean Kelly To: current@freebsd.org Subject: pcm status Message-ID: <20010120002418.A4673@edgemaster.zombie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the current status of the pcm driver? I ask this because I am able to hear sticking and slowdowns in sound when I move my PS/2 mouse. pcm0: at io 0xe800 irq 11 (4p/3r channels duplex) I did not have this behavior in -STABLE, but now I do since I upgraded to -CURRENT. FreeBSD edgemaster 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Jan 15 02:38:13 CST 2001 root@edgemaster:/usr/obj/usr/src/sys/EDGEMASTER i386 I also get many of these: pcm0: hwptr went backwards 2816 -> 2720 pcm0: hwptr went backwards 1760 -> 1568 pcm0: hwptr went backwards 1952 -> 1728 pcm0: hwptr went backwards 0 -> 3872 Other than that, -CURRENT has been very stable (except the time Ioaded vn.ko and the unloaded it and the kernel exploded, leaving me no useful crashdumps no less). -- Sean Kelly | PGP KeyID: 77042C7B smkelly@zombie.org | http://www.zombie.org For PGP key, send e-mail with subject "send pgp key" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 22:43:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5F0F437B400 for ; Fri, 19 Jan 2001 22:43:38 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.1/8.11.0) with ESMTP id f0K6haY00891; Fri, 19 Jan 2001 23:43:37 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id f0K6gXs19678; Fri, 19 Jan 2001 23:42:33 -0700 (MST) Message-Id: <200101200642.f0K6gXs19678@billy-club.village.org> To: Sean Kelly Subject: Re: pcm status Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sat, 20 Jan 2001 00:24:18 CST." <20010120002418.A4673@edgemaster.zombie.org> References: <20010120002418.A4673@edgemaster.zombie.org> Date: Fri, 19 Jan 2001 23:42:32 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010120002418.A4673@edgemaster.zombie.org> Sean Kelly writes: : I did not have this behavior in -STABLE, but now I do since I upgraded : to -CURRENT. -current's interrupt latency is horrible these days, which seems to manifest itself in problem with the sound driver. I have a -current laptop and get all kinds of artifacts on it. I have a laptop that is running -stable and has 1/3 the power of the -current laptop and plays w/o a hitch. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 19 23:39:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from server.bitmcnit.bryansk.su (bitmcnit.bryansk.ru [195.239.213.9]) by hub.freebsd.org (Postfix) with ESMTP id D849E37B400; Fri, 19 Jan 2001 23:39:10 -0800 (PST) Received: (from uucp@localhost) by server.bitmcnit.bryansk.su (8.9.3/8.9.3) with UUCP id KAA00563; Sat, 20 Jan 2001 10:29:16 +0300 Received: (from alex@localhost) by kapran.bitmcnit.bryansk.su (8.11.1/8.11.1) id f0K7Vek17184; Sat, 20 Jan 2001 10:31:40 +0300 (MSK) (envelope-from alex@kapran.bitmcnit.bryansk.su) Date: Sat, 20 Jan 2001 10:31:37 +0300 From: Alex Kapranoff To: current@freebsd.org Cc: questions@freebsd.org Subject: Lots of page faults Message-ID: <20010120103135.A10608@kapran.bitmcnit.bryansk.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a fairly recent CURRENT: FreeBSD kapran.bitmcnit.bryansk.su 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Dec 30 12:41:53 MSK 2000 root@kapran.bitmcnit.bryansk.su:/usr/src/sys/compile/KAPRAN i386 And what I noticed is a massive slowdown when running make(1). It seems that I am going to finish a new `buildkernel' in a millennium or two. Additional symptoms include very high system CPU state percentage and a lot of page faults. vmstat(8) shows something like (while building world): procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ac0 in sy cs us sy id 2 0 0 24216 8444 235 1 1 0 215 23 0 0 810 805 213 15 43 42 2 0 0 23776 8508 356 0 0 0 356 0 16 0 296 879 216 18 82 1 2 0 0 24252 8232 382 0 0 0 313 0 12 0 299 987 240 21 79 0 2 0 0 23664 8528 328 0 0 0 407 0 11 0 289 711 216 9 91 0 2 0 0 23816 8424 314 0 0 0 304 0 7 0 285 890 209 21 75 5 2 0 0 23792 8440 362 0 0 0 338 0 12 0 292 979 222 24 76 0 2 0 0 24284 8144 372 0 0 0 285 0 12 0 291 981 227 24 74 2 4 0 0 22724 8964 140 0 0 0 401 0 71 0 363 463 340 2 62 36 2 1 0 22392 8472 429 0 0 0 279 0 11 0 297 834 215 17 82 2 4 0 0 22628 8312 334 0 0 0 297 0 2 0 286 869 213 15 85 0 From time to time I get a core dump from `cc1' or `cpp' or even `as' too. Is my RAM rotting or what? -- Alex Kapranoff, Voice: +7(0832)791845 We've lived 2 weeks in the brand new millenium... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 1:26:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 477F337B400; Sat, 20 Jan 2001 01:25:57 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0K9O8I52405; Sat, 20 Jan 2001 11:24:27 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101200924.f0K9O8I52405@gratis.grondar.za> To: cjclark@alum.mit.edu Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: syslogd(8) does not update hostname References: <200101190330.f0J3UPa75677@rfx-216-196-73-168.users.reflexcom.com> In-Reply-To: <200101190330.f0J3UPa75677@rfx-216-196-73-168.users.reflexcom.com> ; from cjclark@reflexcom.com "Thu, 18 Jan 2001 19:30:25 PST." Date: Sat, 20 Jan 2001 11:24:16 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't agree with this change. hostname != name-that-IP-address-resolves-to. I can see how loggin the IP address (or some manifestation thereof) to a central logger, but this is too strong. Example: My laptop has a hostname set for my home network, and I connect it to my work network and DHCP an IP address there. I would be HOPPING mad if that caused my hostname and VPN to break. M > >Submitter-Id: current-users > >Originator: Crist J. Clark > >Organization: > >Confidential: no > >Synopsis: syslogd(8) does not update hostname > >Severity: non-critical > >Priority: medium > >Category: bin > >Release: FreeBSD 5.0-CURRENT i386 > >Class: sw-bug > >Environment: > > All standard FreeBSD distributions. The code discussed is from > 5.0-CURRENT, but should trivially merge back to -STABLE. > > >Description: > > Many tools and progams within FreeBSD date back to a time when > it was expected that a machines IP and hostname seldom, if ever, > changed. Even when a IP and hostname were received at boot, it rarely > changed until shutdown. With many users using protocols like DHCP > where IP and hostname change with time, many tools do not deal well > with this behavior. > > One of these tools is syslogd(8). syslogd(8) is typically > started at boot time and runs until shutdown. However, syslogd(8) > loads the hostname at startup and syslogd(8)'s idea of the hostname > can never change while it is running. > > One might expect that a SIGHUP would cause syslogd(8) to load > the new hostname since a SIGHUP can cause syslogd(8) to re-read its > configuration file and re-open the log files, but it does not. > > The fact that the hostname does not change can cause confusion > in the log files. It could be especially troublesome when a machine is > logging to a central loghost. At any given time, the names in the log > files may not have any correspondence to the names the hosts currently > have. There are even issues on a host that gets its IP and hostname > via DHCP at boot and the name never changes. syslogd(8) is started > before any network services are initialized in /etc/rc. > > I propose that syslogd(8) should reload the hostname with a > SIGHUP. I cannot think of any reason that one should not update the > hostname, but as I pointed out, there are reasons why one would want > that behavior. > > >How-To-Repeat: > > # hostname -s > bubbles > # hostname bubbles-test.domain.org > # kill -HUP `cat /var/run/syslog.pid` > # logger -p user.notice "hostname test" > # tail -4 /var/log/messages > Jan 17 21:45:00 bubbles /boot/kernel/kernel: acd0: CDROM at ata0-slave using BIOSPIO > Jan 17 21:45:00 bubbles /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s1a > Jan 18 00:41:14 bubbles su: cjc to root on /dev/ttyp0 > Jan 18 00:58:34 bubbles cjc: hostname test > > >Fix: > > I do not see any reason we cannot move the code that gets the > hostname from the main() function into init(). init() is called when > to "reload" settings. The hostname is never used in main() before > init() is called. The patch is against -CURRENT and my box has not > exploded yet. > > Here is what the above test looks like with the change in > place. > > # hostname -s > bubbles > # hostname bubbles-test.cjclark.org > # kill -HUP `cat /var/run/syslog.pid ` > # logger -p user.notice "syslogd hostname test" > # hostname bubbles.cjclark.org > # kill -HUP `cat /var/run/syslog.pid ` > # logger -p user.notice "syslogd hostname test" > # tail -4 /var/log/messages > Jan 18 13:36:58 bubbles su: BAD SU cjc to root on /dev/ttyp0 > Jan 18 13:37:03 bubbles su: cjc to root on /dev/ttyp0 > Jan 18 13:38:40 bubbles-test cjc: syslogd hostname test > Jan 18 13:39:11 bubbles cjc: syslogd hostname test > > > --- syslogd.c 2001/01/18 08:06:34 > +++ syslogd.c 2001/01/18 08:09:23 > @@ -395,12 +395,6 @@ > > consfile.f_type = F_CONSOLE; > (void)strcpy(consfile.f_un.f_fname, ctty + sizeof _PATH_DEV - 1); > - (void)gethostname(LocalHostName, sizeof(LocalHostName)); > - if ((p = strchr(LocalHostName, '.')) != NULL) { > - *p++ = '\0'; > - LocalDomain = p; > - } else > - LocalDomain = ""; > (void)strcpy(bootfile, getbootfile()); > (void)signal(SIGTERM, die); > (void)signal(SIGINT, Debug ? die : SIG_IGN); > @@ -1342,6 +1336,16 @@ > char host[MAXHOSTNAMELEN+1]; > > dprintf("init\n"); > + > + /* > + * Load hostname (may have changed) > + */ > + (void)gethostname(LocalHostName, sizeof(LocalHostName)); > + if ((p = strchr(LocalHostName, '.')) != NULL) { > + *p++ = '\0'; > + LocalDomain = p; > + } else > + LocalDomain = ""; > > /* > * Close all open log files. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 1:53:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id AC52637B401 for ; Sat, 20 Jan 2001 01:53:22 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0K9rMl04249 for ; Sat, 20 Jan 2001 10:53:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: current hangs... From: Poul-Henning Kamp Date: Sat, 20 Jan 2001 10:53:22 +0100 Message-ID: <4247.979984402@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 1:59:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 8EB7C37B400; Sat, 20 Jan 2001 01:59:34 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Sat, 20 Jan 2001 01:57:47 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0K9xY712913; Sat, 20 Jan 2001 01:59:34 -0800 (PST) (envelope-from cjc) Date: Sat, 20 Jan 2001 01:59:34 -0800 From: "Crist J. Clark" To: Mark Murray Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: syslogd(8) does not update hostname Message-ID: <20010120015934.F10761@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <200101190330.f0J3UPa75677@rfx-216-196-73-168.users.reflexcom.com> <200101200924.f0K9O8I52405@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200101200924.f0K9O8I52405@gratis.grondar.za>; from mark@grondar.za on Sat, Jan 20, 2001 at 11:24:16AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 20, 2001 at 11:24:16AM +0200, Mark Murray wrote: > I don't agree with this change. > > hostname != name-that-IP-address-resolves-to. Dunno what you are talking about. That has nothing directly to do with this. No one is talking about forcing you to change your hostname. The patch just allows syslogd(8) to take note if the hostname were to change. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 3: 2: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 8A67637B401; Sat, 20 Jan 2001 03:01:40 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0KB1SI52583; Sat, 20 Jan 2001 13:01:28 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101201101.f0KB1SI52583@gratis.grondar.za> To: cjclark@alum.mit.edu Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: syslogd(8) does not update hostname References: <20010120015934.F10761@rfx-216-196-73-168.users.reflex> In-Reply-To: <20010120015934.F10761@rfx-216-196-73-168.users.reflex> ; from "Crist J. Clark" "Sat, 20 Jan 2001 01:59:34 PST." Date: Sat, 20 Jan 2001 13:01:36 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Jan 20, 2001 at 11:24:16AM +0200, Mark Murray wrote: > > I don't agree with this change. > > > > hostname != name-that-IP-address-resolves-to. > > Dunno what you are talking about. That has nothing directly to do with > this. No one is talking about forcing you to change your hostname. The > patch just allows syslogd(8) to take note if the hostname were to > change. D'uh. Bad crack I'm on. :-) M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 4:15:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B8CF637B400; Sat, 20 Jan 2001 04:15:15 -0800 (PST) Received: from newsguy.com (p59-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.124]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id VAA13970; Sat, 20 Jan 2001 21:15:13 +0900 (JST) Message-ID: <3A6980BF.91F98797@newsguy.com> Date: Sat, 20 Jan 2001 21:12:47 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Maxim Sobolev Cc: John Baldwin , Chris Knight , current@FreeBSD.ORG Subject: Re: sysinstall move and make release on FreeBSD-stable References: <3A68004F.D490D0D2@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > > Slightly OT, but could we have a flag to disable building sysinstall during make > world? It's hardly a tool that is required for day-to-day operation, so in most > cases it will only waste considerable amount of root partitition. 1) Now sysinstall is /usr/sbin, and it is hardly all that big anyway. 2) It wouldn't waste any more space anyway, since it would be *replacing* what is already installed. 3) Most of what FreeBSD installs is not required for day-to-day for most users. Since many users use sysinstall to some extent as a system managing tool, sysinstall is actually quite more oftenly used than many. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@a.crazy.bsdconspiracy.net "There is no spoon." -- Kiki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 5:20:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 06BF237B400; Sat, 20 Jan 2001 05:20:27 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0KDKII52885; Sat, 20 Jan 2001 15:20:20 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101201320.f0KDKII52885@gratis.grondar.za> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: current hangs... References: <4247.979984402@critter> In-Reply-To: <4247.979984402@critter> ; from Poul-Henning Kamp "Sat, 20 Jan 2001 10:53:22 +0100." Date: Sat, 20 Jan 2001 15:20:24 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times > now hung the machine so that only reset got any attention simply by > make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 6: 1: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn68.dh.casema.net [212.64.31.68]) by hub.freebsd.org (Postfix) with ESMTP id D1A8B37B400; Sat, 20 Jan 2001 06:00:46 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0KEJdl15104; Sat, 20 Jan 2001 15:19:44 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010120150126.00c5b220@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 20 Jan 2001 15:02:03 +0100 To: "Daniel C. Sobral" , Maxim Sobolev From: "Rogier R. Mulhuijzen" Subject: Re: sysinstall move and make release on FreeBSD-stable Cc: John Baldwin , Chris Knight , current@FreeBSD.ORG In-Reply-To: <3A6980BF.91F98797@newsguy.com> References: <3A68004F.D490D0D2@FreeBSD.org> 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 >3) Most of what FreeBSD installs is not required for day-to-day for most >users. Since many users use sysinstall to some extent as a system >managing tool, sysinstall is actually quite more oftenly used than many. It's currently the best way to install packages IMHO. With the automatic dependancy resolving and downloading from FTP. The latter pkg_add offers, but it's a bother having to find the URLs. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 6:15:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 0062A37B400; Sat, 20 Jan 2001 06:15:38 -0800 (PST) Received: from newsguy.com (p59-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.124]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id XAA17924; Sat, 20 Jan 2001 23:15:29 +0900 (JST) Message-ID: <3A699CEE.5B04769@newsguy.com> Date: Sat, 20 Jan 2001 23:13:02 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: "Rogier R. Mulhuijzen" Cc: Maxim Sobolev , John Baldwin , Chris Knight , current@FreeBSD.ORG Subject: Re: sysinstall move and make release on FreeBSD-stable References: <3A68004F.D490D0D2@FreeBSD.org> <4.3.2.7.0.20010120150126.00c5b220@mail.drwilco.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rogier R. Mulhuijzen" wrote: > > >3) Most of what FreeBSD installs is not required for day-to-day for most > >users. Since many users use sysinstall to some extent as a system > >managing tool, sysinstall is actually quite more oftenly used than many. > > It's currently the best way to install packages IMHO. With the automatic > dependancy resolving and downloading from FTP. The latter pkg_add offers, > but it's a bother having to find the URLs. What are you talking about? pkg_add -r pkgname, that's all it takes. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@a.crazy.bsdconspiracy.net "There is no spoon." -- Kiki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 6:28: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn68.dh.casema.net [212.64.31.68]) by hub.freebsd.org (Postfix) with ESMTP id 8CA9A37B401 for ; Sat, 20 Jan 2001 06:27:49 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0KElBl15158 for ; Sat, 20 Jan 2001 15:47:12 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010120152738.00c78df0@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 20 Jan 2001 15:29:35 +0100 To: freebsd-current@freebsd.org From: "Rogier R. Mulhuijzen" Subject: Re: sysinstall move and make release on FreeBSD-stable In-Reply-To: <3A699CEE.5B04769@newsguy.com> References: <3A68004F.D490D0D2@FreeBSD.org> <4.3.2.7.0.20010120150126.00c5b220@mail.drwilco.net> 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 >What are you talking about? pkg_add -r pkgname, that's all it takes. *hides head in shame* OK so I'm a sucker for the graphical interface =) DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 6:46:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from Mail6.sc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 5291B37B401 for ; Sat, 20 Jan 2001 06:46:09 -0800 (PST) Received: from sc.rr.com ([24.88.102.101]) by Mail6.sc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sat, 20 Jan 2001 09:46:08 -0500 Received: (from dmaddox@localhost) by sc.rr.com (8.11.1/8.11.1) id f0KEl5j12484; Sat, 20 Jan 2001 09:47:05 -0500 (EST) (envelope-from dmaddox) Date: Sat, 20 Jan 2001 09:47:05 -0500 From: "Donald J . Maddox" To: Warner Losh Cc: Sean Kelly , current@FreeBSD.ORG Subject: Re: pcm status Message-ID: <20010120094705.B12408@cae88-102-101.sc.rr.com> Reply-To: dmaddox@sc.rr.com Mail-Followup-To: Warner Losh , Sean Kelly , current@FreeBSD.ORG References: <20010120002418.A4673@edgemaster.zombie.org> <200101200642.f0K6gXs19678@billy-club.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101200642.f0K6gXs19678@billy-club.village.org>; from imp@village.org on Fri, Jan 19, 2001 at 11:42:32PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is directly traceable to entropy harvesting by /dev/*random. I know it's not an option if you need to use ssh, but not loading random.ko will fix the sound problems when moving the mouse or typing. It doesn't fix the 'hwptr went backwards' messages, though. On Fri, Jan 19, 2001 at 11:42:32PM -0700, Warner Losh wrote: > In message <20010120002418.A4673@edgemaster.zombie.org> Sean Kelly writes: > : I did not have this behavior in -STABLE, but now I do since I upgraded > : to -CURRENT. > > -current's interrupt latency is horrible these days, which seems to > manifest itself in problem with the sound driver. I have a -current > laptop and get all kinds of artifacts on it. I have a laptop that is > running -stable and has 1/3 the power of the -current laptop and plays > w/o a hitch. > > Warner > > > 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 20 7: 6:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id A446737B401 for ; Sat, 20 Jan 2001 07:06:28 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0KF60l04895; Sat, 20 Jan 2001 16:06:00 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: current hangs... In-Reply-To: Your message of "Sat, 20 Jan 2001 15:20:24 +0200." <200101201320.f0KDKII52885@gratis.grondar.za> Date: Sat, 20 Jan 2001 16:06:00 +0100 Message-ID: <4893.980003160@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101201320.f0KDKII52885@gratis.grondar.za>, Mark Murray writes: >> >> on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times >> now hung the machine so that only reset got any attention simply by >> make -j 128 world > >Do you have an easy way to narrow it down to CCD by doing the same >thing but without ccd involvement? No, /usr is on ccd on this one :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 7:23:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 676C937B401 for ; Sat, 20 Jan 2001 07:23:34 -0800 (PST) Received: (qmail 93784 invoked by uid 100); 20 Jan 2001 15:23:33 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14953.44405.812413.17781@guru.mired.org> Date: Sat, 20 Jan 2001 09:23:33 -0600 (CST) To: Mark Murray Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: current hangs... In-Reply-To: <200101201320.f0KDKII52885@gratis.grondar.za> References: <4247.979984402@critter> <200101201320.f0KDKII52885@gratis.grondar.za> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray types: > > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times > > now hung the machine so that only reset got any attention simply by > > make -j 128 world > > Do you have an easy way to narrow it down to CCD by doing the same > thing but without ccd involvement? I don't think it's ccd. I get similar hangs with "make -j 20 buildworld" on a 2xPII-Xeon/450, 256M, two scsi disks on ahc without ccd. I think more likely it's related to the problems that sos is currently having/investigating. ; Sat, 20 Jan 2001 07:36:22 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0KFa2I53132; Sat, 20 Jan 2001 17:36:05 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101201536.f0KFa2I53132@gratis.grondar.za> To: dmaddox@sc.rr.com Cc: current@FreeBSD.ORG Subject: Re: pcm status References: <20010120094705.B12408@cae88-102-101.sc.rr.com> In-Reply-To: <20010120094705.B12408@cae88-102-101.sc.rr.com> ; from "Donald J . Maddox" "Sat, 20 Jan 2001 09:47:05 EST." Date: Sat, 20 Jan 2001 17:36:08 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is directly traceable to entropy harvesting by /dev/*random. > I know it's not an option if you need to use ssh, but not loading > random.ko will fix the sound problems when moving the mouse or > typing. It doesn't fix the 'hwptr went backwards' messages, though. Please tell me if sysctl -w kern.random.yarrow.bins=2 makes a difference for you. Thanks! M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 7:47:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail5.sc.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id 6520137B402 for ; Sat, 20 Jan 2001 07:47:06 -0800 (PST) Received: from sc.rr.com ([24.88.102.101]) by mail5.sc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sat, 20 Jan 2001 10:47:05 -0500 Received: (from dmaddox@localhost) by sc.rr.com (8.11.1/8.11.1) id f0KFm3E00351; Sat, 20 Jan 2001 10:48:03 -0500 (EST) (envelope-from dmaddox) Date: Sat, 20 Jan 2001 10:48:03 -0500 From: "Donald J . Maddox" To: Mark Murray Cc: dmaddox@sc.rr.com, current@FreeBSD.ORG Subject: Re: pcm status Message-ID: <20010120104803.A327@cae88-102-101.sc.rr.com> Reply-To: dmaddox@sc.rr.com Mail-Followup-To: Mark Murray , dmaddox@sc.rr.com, current@FreeBSD.ORG References: <20010120094705.B12408@cae88-102-101.sc.rr.com> <200101201536.f0KFa2I53132@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101201536.f0KFa2I53132@gratis.grondar.za>; from mark@grondar.za on Sat, Jan 20, 2001 at 05:36:08PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If it helps at all, it's marginal. I still get skips. On Sat, Jan 20, 2001 at 05:36:08PM +0200, Mark Murray wrote: > > This is directly traceable to entropy harvesting by /dev/*random. > > I know it's not an option if you need to use ssh, but not loading > > random.ko will fix the sound problems when moving the mouse or > > typing. It doesn't fix the 'hwptr went backwards' messages, though. > > Please tell me if > > sysctl -w kern.random.yarrow.bins=2 > makes a difference for you. > > Thanks! > > M > -- > Mark Murray > Warning: this .sig is umop ap!sdn > > > 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 20 8:10: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 92CF637B401 for ; Sat, 20 Jan 2001 08:09:42 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0KG9PI53208; Sat, 20 Jan 2001 18:09:27 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101201609.f0KG9PI53208@gratis.grondar.za> To: dmaddox@sc.rr.com Cc: current@FreeBSD.ORG Subject: Re: pcm status References: <20010120104803.A327@cae88-102-101.sc.rr.com> In-Reply-To: <20010120104803.A327@cae88-102-101.sc.rr.com> ; from "Donald J . Maddox" "Sat, 20 Jan 2001 10:48:03 EST." Date: Sat, 20 Jan 2001 18:09:30 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, please try this, then; change the HARVEST_RING_SIZE in sys/dev/random/yarrow.h to a smaller power-of-2 (256 or 128 would be good), and let me know how that helps-or-not. Thanks! M > If it helps at all, it's marginal. I still get skips. > > On Sat, Jan 20, 2001 at 05:36:08PM +0200, Mark Murray wrote: > > > This is directly traceable to entropy harvesting by /dev/*random. > > > I know it's not an option if you need to use ssh, but not loading > > > random.ko will fix the sound problems when moving the mouse or > > > typing. It doesn't fix the 'hwptr went backwards' messages, though. > > > > Please tell me if > > > > sysctl -w kern.random.yarrow.bins=2 > > makes a difference for you. > > > > Thanks! > > > > M > > -- > > Mark Murray > > Warning: this .sig is umop ap!sdn > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 9:44:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from lolita.speakeasy.net (lolita.speakeasy.net [216.254.0.13]) by hub.freebsd.org (Postfix) with SMTP id 1C07C37B400 for ; Sat, 20 Jan 2001 09:44:31 -0800 (PST) Received: (qmail 4801 invoked from network); 20 Jan 2001 17:36:33 -0000 Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by 192.168.0.13 with SMTP; 20 Jan 2001 17:36:33 -0000 Received: (qmail 23169 invoked from network); 20 Jan 2001 17:44:29 -0000 Received: from unknown (HELO celebris.tddhome) (64.81.20.229) by gonzo.speakeasy.net with SMTP; 20 Jan 2001 17:44:29 -0000 Received: (from tomdean@localhost) by celebris.tddhome (8.11.1/8.11.1) id f0KHiQ562089; Sat, 20 Jan 2001 09:44:26 -0800 (PST) (envelope-from tomdean@speakeasy.org) Date: Sat, 20 Jan 2001 09:44:26 -0800 (PST) Message-Id: <200101201744.f0KHiQ562089@celebris.tddhome> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: mark@grondar.za Cc: phk@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <200101201320.f0KDKII52885@gratis.grondar.za> (message from Mark Murray on Sat, 20 Jan 2001 15:20:24 +0200) Subject: Re: current hangs... References: <4247.979984402@critter> <200101201320.f0KDKII52885@gratis.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a recent -current that hangs in 'make -j36 world'. I am now running a UP kernel of the same date: # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Mon Jan 15 18:42:30 PST 2001 \ root@celebris:/usr/src/sys/compile/CELEBRIS i386 dmesg attached. tomdean ==== dmesg from a UP kernel =============== 96 blocks, 0.3% fragmentation) IP Filter: already initialized de0: enabling BNC port Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Jan 15 18:42:30 PST 2001 root@celebris:/usr/src/sys/compile/CELEBRIS Timecounter "i8254" frequency 1193029 Hz Timecounter "TSC" frequency 131996485 Hz CPU: Pentium/P54C (132.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 94597120 (92380K bytes) Preloaded elf kernel "kernel" at 0xc0334000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc033409c. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 ncr0: port 0xec00-0xecff mem 0xfedfbf00-0xfedfbfff irq 11 at device 1.0 on pci0 isab0: at device 2.0 on pci0 isa0: on isab0 pci0: at 6.0 (no driver attached) sis0: port 0xe800-0xe8ff mem 0xfedfa000-0xfedfafff irq 10 at device 7.0 on pci0 sis0: Ethernet address: 00:a0:cc:74:63:b4 miibus0: on sis0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto de0: port 0xe480-0xe4ff mem 0xfedfbe80-0xfedfbeff irq 15 at device 8.0 on pci0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 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 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port 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 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: can't assign resources unknown: can't assign resources IP Filter: v3.4.13 initialized. Default = pass all, Logging = enabled Waiting 10 seconds for SCSI devices to settle Mounting root from ufs:/dev/da1s1a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: cd present [326227 x 2048 byte records] da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) IP Filter: already initialized de0: enabling BNC port stray irq 7 stray irq 7 stray irq 7 stray irq 7 got 5 stray irq 7's: not logging anymore pid 27080 (communicator-4.7), uid 1001: exited on signal 10 (core dumped) microuptime() went backwards (272675.344496 -> 272675.-694570216) microuptime() went backwards (287740.708251 -> 287740.-694206432) pid 61804 (m6811-elf-gdb), uid 1001: exited on signal 11 (core dumped) pid 61824 (m6811-elf-gdb), uid 1001: exited on signal 11 (core dumped) pid 61834 (m6811-elf-gdb), uid 1001: exited on signal 11 (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 9:47:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id B083937B400; Sat, 20 Jan 2001 09:47:25 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f0KHjC821309; Sat, 20 Jan 2001 13:45:12 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 20 Jan 2001 13:45:12 -0400 (AST) From: The Hermit Hacker To: Mark Murray Cc: Poul-Henning Kamp , Subject: Re: current hangs... In-Reply-To: <200101201320.f0KDKII52885@gratis.grondar.za> 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, 20 Jan 2001, Mark Murray wrote: > > > > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times > > now hung the machine so that only reset got any attention simply by > > make -j 128 world > > Do you have an easy way to narrow it down to CCD by doing the same > thing but without ccd involvement? I don't have CCD, and got home last night from the office and mine was hung also, on a kernel from the day before ... being in X, pretty much nothing I could do to try and debug it ... new laptop gets in this week, so will be setting up the whole serial console debugging env ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 14:56:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 750FA37B400; Sat, 20 Jan 2001 14:56:03 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0KN0Es76064; Sat, 20 Jan 2001 15:00:16 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 20 Jan 2001 14:55:54 -0800 (PST) From: John Baldwin To: The Hermit Hacker Subject: Re: current hangs... Cc: current@FreeBSD.org, Poul-Henning Kamp , Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Jan-01 The Hermit Hacker wrote: > On Sat, 20 Jan 2001, Mark Murray wrote: > >> > >> > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times >> > now hung the machine so that only reset got any attention simply by >> > make -j 128 world >> >> Do you have an easy way to narrow it down to CCD by doing the same >> thing but without ccd involvement? > > I don't have CCD, and got home last night from the office and mine was > hung also, on a kernel from the day before ... being in X, pretty much > nothing I could do to try and debug it ... new laptop gets in this week, > so will be setting up the whole serial console debugging env ... Is it SMP, and does it have multiple SCSI disks hanging off of the same device? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 14:56:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 5B55B37B404 for ; Sat, 20 Jan 2001 14:56:06 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0KN0Ks76068; Sat, 20 Jan 2001 15:00:20 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010120094705.B12408@cae88-102-101.sc.rr.com> Date: Sat, 20 Jan 2001 14:56:00 -0800 (PST) From: John Baldwin To: "Donald J . Maddox" Subject: Re: pcm status Cc: current@FreeBSD.org, Sean Kelly , Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Jan-01 Donald J . Maddox wrote: > This is directly traceable to entropy harvesting by /dev/*random. > I know it's not an option if you need to use ssh, but not loading > random.ko will fix the sound problems when moving the mouse or > typing. It doesn't fix the 'hwptr went backwards' messages, though. The entropy stuff only kicks in on the keyboard and mouse. It can't really help the hwptr backwards stuff, as that is due to the additional overhead in the current interrupt path as well as asynchronous handling of interrupts. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 15:38:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 656A337B400; Sat, 20 Jan 2001 15:38:13 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0KNcCl06180; Sun, 21 Jan 2001 00:38:12 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: The Hermit Hacker , current@FreeBSD.org, Mark Murray Subject: Re: current hangs... In-Reply-To: Your message of "Sat, 20 Jan 2001 14:55:54 PST." Date: Sun, 21 Jan 2001 00:38:12 +0100 Message-ID: <6178.980033892@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Baldwin writes: > >On 20-Jan-01 The Hermit Hacker wrote: >> On Sat, 20 Jan 2001, Mark Murray wrote: >> >>> > >>> > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times >>> > now hung the machine so that only reset got any attention simply by >>> > make -j 128 world >>> >>> Do you have an easy way to narrow it down to CCD by doing the same >>> thing but without ccd involvement? >> >> I don't have CCD, and got home last night from the office and mine was >> hung also, on a kernel from the day before ... being in X, pretty much >> nothing I could do to try and debug it ... new laptop gets in this week, >> so will be setting up the whole serial console debugging env ... > >Is it SMP, and does it have multiple SCSI disks hanging off of the same device? SMP, one scsi disk on each controller, /usr and /home ccd'ed. dmesg: Booting [/boot/kernel/kernel]... stray irq 7 Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri Jan 19 23:21:40 CET 2001 root@varmpost.freebsd.dk:/usr/src/sys/compile/SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (333.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 258048000 (252000K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 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 Preloaded elf kernel "kernel" at 0xc031b000. Pentium Pro MTRR support enabled Using $PIR table, 9 entries at 0xc00fdf20 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: at device 2.1 on pci0 atapci0: Busmastering DMA not supported pci0: at 2.2 (no driver attached) Timecounter "PIIX" frequency 3579545 Hz pci0: at 2.3 (no driver attached) fxp0: port 0xfcc0-0xfcdf mem 0xfed00000-0xfedfffff,0xfecdf000-0xfecdffff irq 19 at device 3.0 on pci0 fxp0: Ethernet address 00:a0:c9:82:bb:30 ahc0: port 0xf800-0xf8ff mem 0xfecff000-0xfecfffff irq 17 at device 9.0 on pci0 aic7895: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xf400-0xf4ff mem 0xfecfe000-0xfecfefff irq 17 at device 9.1 on pci0 aic7895: Wide Channel B, SCSI Id=7, 32/255 SCBs pci0: at 13.0 (no driver attached) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 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 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources 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 IOAPIC #0 intpin 2 Waiting 2 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) WARNING: / was not properly dismounted SMP: AP CPU #1 Launched! ccd0-3: Concatenated disk drivers swapon: adding /dev/da1s1b as swap device swapon: adding /dev/da0s1b as swap device Automatic boot in progress... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 16: 5:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 1538D37B400 for ; Sat, 20 Jan 2001 16:05:04 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0L07Us76176; Sat, 20 Jan 2001 16:07:30 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <6178.980033892@critter> Date: Sat, 20 Jan 2001 16:03:08 -0800 (PST) From: John Baldwin To: Poul-Henning Kamp Subject: Re: current hangs... Cc: Mark Murray , current@FreeBSD.org, The Hermit Hacker Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Jan-01 Poul-Henning Kamp wrote: > In message , John Baldwin writes: >> >>On 20-Jan-01 The Hermit Hacker wrote: >>> On Sat, 20 Jan 2001, Mark Murray wrote: >>> >>>> > >>>> > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times >>>> > now hung the machine so that only reset got any attention simply by >>>> > make -j 128 world >>>> >>>> Do you have an easy way to narrow it down to CCD by doing the same >>>> thing but without ccd involvement? >>> >>> I don't have CCD, and got home last night from the office and mine was >>> hung also, on a kernel from the day before ... being in X, pretty much >>> nothing I could do to try and debug it ... new laptop gets in this week, >>> so will be setting up the whole serial console debugging env ... >> >>Is it SMP, and does it have multiple SCSI disks hanging off of the same >>device? > > SMP, one scsi disk on each controller, /usr and /home ccd'ed. Is there any code dealing with disk I/O in the kernel that does the equivalent of this: while (!io_done) /* spin */ ; That assumes an interrupt will set io_done? Using DELAY() in places might explain this. If the kernel is spining, then it is probably holding Giant, which prevents Ctrl-Alt-Esc (keyboard ithread blocks on Giant) not to mention we aren't doing a task switch to it anyways. Also, NMI's would be blocked by trap() being broken. I have a patch for trap() btw that tells it to not bother with Giant for NMI's. I haven't tested it yet though. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 17: 2:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 8332A37B400; Sat, 20 Jan 2001 17:02:04 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Sat, 20 Jan 2001 17:00:17 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0L11u923321; Sat, 20 Jan 2001 17:01:56 -0800 (PST) (envelope-from cjc) Date: Sat, 20 Jan 2001 17:01:55 -0800 From: "Crist J. Clark" To: Dag-Erling Smorgrav Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname Message-ID: <20010120170155.K10761@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <200101190330.f0J3UPa75677@rfx-216-196-73-168.users.reflexcom.com> <20010119110341.A7958@rfx-216-196-73-168.users.reflex> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from des@ofug.org on Fri, Jan 19, 2001 at 11:09:24PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 19, 2001 at 11:09:24PM +0100, Dag-Erling Smorgrav wrote: > "Crist J. Clark" writes: > > On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: > > > It should also log a message if the hostname changes. > > Should that be a responsibility of syslogd(8) or hostname(1)? > > I meant syslogd(8), but putting it in hostname(1) might makes sense, > except that hostname(1) is not the only way to set the hostname > ('sysctl -w kern.hostname=foo' is another) How about just logging a sethostname(3) call? But anyway, syslogd(8) does not track the state of any other system parameters, I think asking syslogd(8) to notice a change in the hostname on its own in a real-time fashion is beyond its scope. That said, I agree that syslogd(8) making a note when its own idea of the hostname changes would be useful. If one is analyzing logs, an entry indicating that messages from a given machine no longer will be labeled as coming from 'foo' but 'foobar' would be very helpful. Patches, patches, patches: --- usr.sbin/syslogd/syslogd.c 2001/01/18 08:06:34 1.1 +++ usr.sbin/syslogd/syslogd.c 2001/01/21 00:55:53 1.3 @@ -318,7 +318,7 @@ struct sockaddr_un sunx, fromunix; struct sockaddr_storage frominet; FILE *fp; - char *p, *hname, line[MAXLINE + 1]; + char *hname, line[MAXLINE + 1]; struct timeval tv, *tvp; struct sigaction sact; sigset_t mask; @@ -395,12 +395,6 @@ consfile.f_type = F_CONSOLE; (void)strcpy(consfile.f_un.f_fname, ctty + sizeof _PATH_DEV - 1); - (void)gethostname(LocalHostName, sizeof(LocalHostName)); - if ((p = strchr(LocalHostName, '.')) != NULL) { - *p++ = '\0'; - LocalDomain = p; - } else - LocalDomain = ""; (void)strcpy(bootfile, getbootfile()); (void)signal(SIGTERM, die); (void)signal(SIGINT, Debug ? die : SIG_IGN); @@ -1340,10 +1334,23 @@ char cline[LINE_MAX]; char prog[NAME_MAX+1]; char host[MAXHOSTNAMELEN+1]; + char oldLocalHostName[MAXHOSTNAMELEN+1]; + char hostMsg[2*(MAXHOSTNAMELEN+1)+40]; dprintf("init\n"); /* + * Load hostname (may have changed) + */ + strncpy(oldLocalHostName, LocalHostName, sizeof(LocalHostName)); + (void)gethostname(LocalHostName, sizeof(LocalHostName)); + if ((p = strchr(LocalHostName, '.')) != NULL) { + *p++ = '\0'; + LocalDomain = p; + } else + LocalDomain = ""; + + /* * Close all open log files. */ Initialized = 0; @@ -1492,6 +1499,17 @@ logmsg(LOG_SYSLOG|LOG_INFO, "syslogd: restart", LocalHostName, ADDDATE); dprintf("syslogd: restarted\n"); + /* + * Log a change in hostname, but only on a restart + */ + if ((signo != 0) && + (strncmp(oldLocalHostName, LocalHostName, sizeof(LocalHostName)) != 0)) { + snprintf(hostMsg, sizeof(hostMsg), + "syslogd: hostname changed, \"%s\" to \"%s\"", + oldLocalHostName, LocalHostName); + logmsg(LOG_SYSLOG|LOG_INFO, hostMsg, LocalHostName, ADDDATE); + dprintf("%s\n", hostMsg); + } } /* -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 17: 2:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 680F637B404; Sat, 20 Jan 2001 17:02:21 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f0L10TW26337; Sat, 20 Jan 2001 21:00:29 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 20 Jan 2001 21:00:29 -0400 (AST) From: The Hermit Hacker To: John Baldwin Cc: , Poul-Henning Kamp , Mark Murray Subject: Re: current hangs... 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, 20 Jan 2001, John Baldwin wrote: > > On 20-Jan-01 The Hermit Hacker wrote: > > On Sat, 20 Jan 2001, Mark Murray wrote: > > > >> > > >> > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times > >> > now hung the machine so that only reset got any attention simply by > >> > make -j 128 world > >> > >> Do you have an easy way to narrow it down to CCD by doing the same > >> thing but without ccd involvement? > > > > I don't have CCD, and got home last night from the office and mine was > > hung also, on a kernel from the day before ... being in X, pretty much > > nothing I could do to try and debug it ... new laptop gets in this week, > > so will be setting up the whole serial console debugging env ... > > Is it SMP, and does it have multiple SCSI disks hanging off of the same device? yes and yes ... ahc1: port 0xcc00-0xccff mem 0xef100000-0xef100fff irq 17 at device 13.0 on pci0 da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 6208MB (12715920 512 byte sectors: 255H 63S/T 791C) da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 8727MB (17873040 512 byte sectors: 255H 63S/T 1112C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 17:17:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CA2BB37B400; Sat, 20 Jan 2001 17:17:15 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA00994; Sat, 20 Jan 2001 17:04:49 -0800 Date: Sat, 20 Jan 2001 17:17:15 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@FreeBSD.ORG Cc: John Baldwin Subject: Re: current hangs... 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'll confirm a hang on both alpha && i386 (both SCSI, qlogic && ahc resp). The i386 was SMP. The Qlogic wasn't. Both were hung with phk's make -j 256 foolery. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 19:32:56 2001 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 E395937B698; Sat, 20 Jan 2001 19:32:37 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id EAA63396; Sun, 21 Jan 2001 04:32:34 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: cjclark@alum.mit.edu Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname References: <200101190330.f0J3UPa75677@rfx-216-196-73-168.users.reflexcom.com> <20010119110341.A7958@rfx-216-196-73-168.users.reflex> <20010120170155.K10761@rfx-216-196-73-168.users.reflex> From: Dag-Erling Smorgrav Date: 21 Jan 2001 04:32:33 +0100 In-Reply-To: "Crist J. Clark"'s message of "Sat, 20 Jan 2001 17:01:55 -0800" Message-ID: Lines: 11 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 "Crist J. Clark" writes: > How about just logging a sethostname(3) call? Still doesn't help. There are (at least) two different ways of setting the hostname, one being a syscall and the other being a sysctl. One could of course have the kernel print a message to the console about it, syslogd(8) would pick that up. DES -- Dag-Erling Smorgrav - des@ofug.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 20 20:50: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id B825D37B401 for ; Sat, 20 Jan 2001 20:49:46 -0800 (PST) Received: from bonsai.knology.net (user-24-214-88-8.knology.net [24.214.88.8]) by mail.hiwaay.net (8.11.0/8.11.0) with ESMTP id f0L4njo18903 for ; Sat, 20 Jan 2001 22:49:45 -0600 (CST) Received: (from steve@localhost) by bonsai.knology.net (8.11.1/8.11.1) id f0L4nia04681 for current@freebsd.org; Sat, 20 Jan 2001 22:49:44 -0600 (CST) (envelope-from steve) Date: Sat, 20 Jan 2001 22:49:44 -0600 From: Steve Price To: current@freebsd.org Subject: excessive paranoia in syslogd(8)? Message-ID: <20010120224944.I387@bonsai.knology.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it just me or does 'syslogd -s' exhibit just a little bit too much paranoia about allowing socket connections? I was futzing with a Perl script that needed to syslog(3) some stuff and after much hair pulling I realized that 'syslogd -s' didn't even allow connections from localhost. Apparently Perl opens a socket connection to syslog and with the '-s' syslogd doesn't read from socket connections either from localhost or from hosts specified with -a. This is a bad thing IMHO. Either I open syslogd up to all socket connections (including from localhost) or I can't use syslog from Perl. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 21:20:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id F0FC237B400 for ; Sat, 20 Jan 2001 21:20:40 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Sat, 20 Jan 2001 21:18:51 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0L5KeZ25006; Sat, 20 Jan 2001 21:20:40 -0800 (PST) (envelope-from cjc) Date: Sat, 20 Jan 2001 21:20:39 -0800 From: "Crist J. Clark" To: Steve Price Cc: current@FreeBSD.ORG Subject: Re: excessive paranoia in syslogd(8)? Message-ID: <20010120212039.M10761@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <20010120224944.I387@bonsai.knology.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010120224944.I387@bonsai.knology.net>; from sprice@hiwaay.net on Sat, Jan 20, 2001 at 10:49:44PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 20, 2001 at 10:49:44PM -0600, Steve Price wrote: > Is it just me or does 'syslogd -s' exhibit just a little bit too > much paranoia about allowing socket connections? I was futzing > with a Perl script that needed to syslog(3) some stuff and after > much hair pulling I realized that 'syslogd -s' didn't even allow > connections from localhost. Apparently Perl opens a socket > connection to syslog and with the '-s' syslogd doesn't read from > socket connections either from localhost or from hosts specified > with -a. This is a bad thing IMHO. Either I open syslogd up to > all socket connections (including from localhost) or I can't use > syslog from Perl. You can write to the /dev/log (usually symlinked to /var/run/log) socket with '-s' set. If you want to or need to use network sockets, # syslogd -a localhost Should provide the behavior you want. As you noted this is not the same as '-s'. It is a feature and not a bug. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 21:29:25 2001 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 6FC5537B400 for ; Sat, 20 Jan 2001 21:29:07 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id GAA63804; Sun, 21 Jan 2001 06:29:02 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Steve Price Cc: current@FreeBSD.ORG Subject: Re: excessive paranoia in syslogd(8)? References: <20010120224944.I387@bonsai.knology.net> From: Dag-Erling Smorgrav Date: 21 Jan 2001 06:29:02 +0100 In-Reply-To: Steve Price's message of "Sat, 20 Jan 2001 22:49:44 -0600" Message-ID: Lines: 13 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Price writes: > Is it just me or does 'syslogd -s' exhibit just a little bit too > much paranoia about allowing socket connections? I was futzing > with a Perl script that needed to syslog(3) some stuff and after > much hair pulling I realized that 'syslogd -s' didn't even allow > connections from localhost. RTFM ('perldoc Sys::Syslog' in this case, pay special attention to setlogsock()) DES -- Dag-Erling Smorgrav - des@ofug.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 20 21:39:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 2FEFA37B402 for ; Sat, 20 Jan 2001 21:39:40 -0800 (PST) Received: from bonsai.knology.net (user-24-214-88-8.knology.net [24.214.88.8]) by mail.hiwaay.net (8.11.0/8.11.0) with ESMTP id f0L5dbo13319; Sat, 20 Jan 2001 23:39:37 -0600 (CST) Received: (from steve@localhost) by bonsai.knology.net (8.11.1/8.11.1) id f0L5dbb04989; Sat, 20 Jan 2001 23:39:37 -0600 (CST) (envelope-from steve) Date: Sat, 20 Jan 2001 23:39:37 -0600 From: Steve Price To: cjclark@alum.mit.edu Cc: current@FreeBSD.ORG Subject: Re: excessive paranoia in syslogd(8)? Message-ID: <20010120233937.J387@bonsai.knology.net> References: <20010120224944.I387@bonsai.knology.net> <20010120212039.M10761@rfx-216-196-73-168.users.reflex> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010120212039.M10761@rfx-216-196-73-168.users.reflex>; from cjclark@reflexnet.net on Sat, Jan 20, 2001 at 09:20:39PM -0800 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 20, 2001 at 09:20:39PM -0800, Crist J. Clark wrote: # # You can write to the /dev/log (usually symlinked to /var/run/log) # socket with '-s' set. # # If you want to or need to use network sockets, # # # syslogd -a localhost # # Should provide the behavior you want. As you noted this is not the # same as '-s'. It is a feature and not a bug. I'm still deciding on that... Here's what I see: steve@test1(~)$ telnet localhost 514 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host. steve@test1(/tmp/tard)$ steve@bonsai(~)$ telnet 192.168.21.28 514 Trying 192.168.21.28... Connected to 192.168.21.28. Escape character is '^]'. Connection closed by foreign host. And here is what I see in syslogd: test1# syslogd -d -a localhost ... logmsg: pri 45, flags 0, from test1, msg Jan 20 23:34:52 rshd[53675]: connection from 127.0.0.1 on illegal port 1186 Logging to CONSOLE /dev/console Logging to FILE /var/log/messages Logging to USERS logmsg: pri 45, flags 0, from test1, msg Jan 20 23:34:54 rshd[53676]: connection from 192.168.21.1 on illegal port 2855 Logging to CONSOLE /dev/console Logging to FILE /var/log/messages Logging to USERS ??? -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 21:46:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id AFFA437B402 for ; Sat, 20 Jan 2001 21:46:28 -0800 (PST) Received: from bonsai.knology.net (user-24-214-88-8.knology.net [24.214.88.8]) by mail.hiwaay.net (8.11.0/8.11.0) with ESMTP id f0L5kQo13782; Sat, 20 Jan 2001 23:46:27 -0600 (CST) Received: (from steve@localhost) by bonsai.knology.net (8.11.1/8.11.1) id f0L5kQV05048; Sat, 20 Jan 2001 23:46:26 -0600 (CST) (envelope-from steve) Date: Sat, 20 Jan 2001 23:46:26 -0600 From: Steve Price To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: excessive paranoia in syslogd(8)? Message-ID: <20010120234626.K387@bonsai.knology.net> References: <20010120224944.I387@bonsai.knology.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Sun, Jan 21, 2001 at 06:29:02AM +0100 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 06:29:02AM +0100, Dag-Erling Smorgrav wrote: # Steve Price writes: # > Is it just me or does 'syslogd -s' exhibit just a little bit too # > much paranoia about allowing socket connections? I was futzing # > with a Perl script that needed to syslog(3) some stuff and after # > much hair pulling I realized that 'syslogd -s' didn't even allow # > connections from localhost. # # RTFM ('perldoc Sys::Syslog' in this case, pay special attention to # setlogsock()) Aha! I must have read that manpage a dozen times and I didn't catch on, but if I do this it works like I would expect even with '-s'. #!/usr/bin/perl -w use Sys::Syslog qw(:DEFAULT setlogsock); setlogsock('unix'); openlog('foo', 'cons,ndelay,pid', 'local0'); syslog('emerg', 'emerg message'); closelog(); Thanks! :) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 22: 5:57 2001 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 45FB437B401 for ; Sat, 20 Jan 2001 22:05:37 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id HAA63956; Sun, 21 Jan 2001 07:05:33 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Steve Price Cc: current@FreeBSD.ORG Subject: Re: excessive paranoia in syslogd(8)? References: <20010120224944.I387@bonsai.knology.net> <20010120234626.K387@bonsai.knology.net> From: Dag-Erling Smorgrav Date: 21 Jan 2001 07:05:32 +0100 In-Reply-To: Steve Price's message of "Sat, 20 Jan 2001 23:46:26 -0600" Message-ID: Lines: 11 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 Steve Price writes: > Aha! I must have read that manpage a dozen times and I didn't catch > on, but if I do this it works like I would expect even with '-s'. ...and even with -ss, which you might as well use unless you intend to log *to* remote hosts, or are sufficiently paranoid to want to log attempts *from* remote hosts to log *to* your box. DES -- Dag-Erling Smorgrav - des@ofug.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 20 22:13:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 616DA37B400 for ; Sat, 20 Jan 2001 22:13:28 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id C16571A63; Sun, 21 Jan 2001 01:13:26 -0500 (EST) Date: Sun, 21 Jan 2001 01:13:26 -0500 From: Will Andrews To: current@FreeBSD.org Subject: sys/time.h w/ timespec stuff Message-ID: <20010121011326.D3002@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , current@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="/3yNEOqWowh/8j+e" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --/3yNEOqWowh/8j+e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey all, I've lately been trying to dig into why OpenPackages make(1) currently doesn't compile on FreeBSD but does on OpenBSD. There is a (very slight) difference between their sys/time.h headers. The timespec* stuff is hidden behind the _KERNEL aura on FreeBSD, but not on OpenBSD. This is manifested in OpenBSD's make source, which uses timespec for a few things. So now, maybe someone can answer my question: why is timespec _KERNEL? --=20 wca --/3yNEOqWowh/8j+e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6an4GF47idPgWcsURAk8oAJ47GYDyPpXqK1D+H8POA6J032SphQCfR2u1 QAnDbHLvW4IfWXPYuDZMZLY= =vsKI -----END PGP SIGNATURE----- --/3yNEOqWowh/8j+e-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 22:43:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from tomts8-srv.bellnexxia.net (tomts8.bellnexxia.net [209.226.175.52]) by hub.freebsd.org (Postfix) with ESMTP id 6D8F037B401 for ; Sat, 20 Jan 2001 22:43:10 -0800 (PST) Received: from sympatico.ca ([209.226.117.189]) by tomts8-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010121064309.DGMN10080.tomts8-srv.bellnexxia.net@sympatico.ca> for ; Sun, 21 Jan 2001 01:43:09 -0500 Message-ID: <3A6A86AA.8F29A04B@sympatico.ca> Date: Sun, 21 Jan 2001 01:50:18 -0500 From: Kelvin Farmer Reply-To: kfarmer@sympatico.ca X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: loader / loader.old install behaviour suggestion Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, After /boot/loader is moved to /boot/loader.old, the install of the new /boot/loader can fail for whatever reason, leaving a computer that cannot automatically bootup, since someone has to type in /boot/loader.old at the boot prompt. I suggest that if the boot process can't find /boot/loader it tries /boot/loader.old before failing, or if the install process fails to install the new /boot/loader that the move of /boot/loader to /boot/loader.old is undone. Just my 2 cents, since i was just hit by this problem. Thanks Kelvin Farmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 22:58:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id C8C1637B400 for ; Sat, 20 Jan 2001 22:58:25 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Sat, 20 Jan 2001 22:56:27 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0L6wG825571; Sat, 20 Jan 2001 22:58:16 -0800 (PST) (envelope-from cjc) Date: Sat, 20 Jan 2001 22:58:15 -0800 From: "Crist J. Clark" To: Steve Price Cc: cjclark@alum.mit.edu, current@FreeBSD.ORG Subject: Re: excessive paranoia in syslogd(8)? Message-ID: <20010120225815.N10761@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <20010120224944.I387@bonsai.knology.net> <20010120212039.M10761@rfx-216-196-73-168.users.reflex> <20010120233937.J387@bonsai.knology.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010120233937.J387@bonsai.knology.net>; from sprice@hiwaay.net on Sat, Jan 20, 2001 at 11:39:37PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 20, 2001 at 11:39:37PM -0600, Steve Price wrote: > On Sat, Jan 20, 2001 at 09:20:39PM -0800, Crist J. Clark wrote: > # > # You can write to the /dev/log (usually symlinked to /var/run/log) > # socket with '-s' set. > # > # If you want to or need to use network sockets, > # > # # syslogd -a localhost > # > # Should provide the behavior you want. As you noted this is not the > # same as '-s'. It is a feature and not a bug. > > I'm still deciding on that... Here's what I see: > > steve@test1(~)$ telnet localhost 514 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > Connection closed by foreign host. > steve@test1(/tmp/tard)$ > > steve@bonsai(~)$ telnet 192.168.21.28 514 > Trying 192.168.21.28... > Connected to 192.168.21.28. > Escape character is '^]'. > Connection closed by foreign host. > > And here is what I see in syslogd: > > test1# syslogd -d -a localhost > ... > logmsg: pri 45, flags 0, from test1, msg Jan 20 23:34:52 rshd[53675]: > connection from 127.0.0.1 on illegal port 1186 > Logging to CONSOLE /dev/console > Logging to FILE /var/log/messages > Logging to USERS > logmsg: pri 45, flags 0, from test1, msg Jan 20 23:34:54 rshd[53676]: > connection from 192.168.21.1 on illegal port 2855 > Logging to CONSOLE /dev/console > Logging to FILE /var/log/messages > Logging to USERS It looks like syslogd(8) is working fine from this. Is something with syslogd(8) not working? 'tail /var/log/messages' aren't those messages there? -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 20 23:51:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from midway.uchicago.edu (midway.uchicago.edu [128.135.12.12]) by hub.freebsd.org (Postfix) with ESMTP id 9E1E037B401 for ; Sat, 20 Jan 2001 23:51:17 -0800 (PST) Received: from C40948-B.uchicago.edu (broad-173-147.rh.uchicago.edu [128.135.173.147]) by midway.uchicago.edu (8.10.1/8.10.1) with ESMTP id f0L7pGf09482 for ; Sun, 21 Jan 2001 01:51:16 -0600 (CST) Message-Id: <4.3.2.7.2.20010121013438.00ba9100@nsit-popmail.uchicago.edu> X-Sender: dbsypher@nsit-popmail.uchicago.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 21 Jan 2001 01:51:05 -0600 To: current@freebsd.org From: David Syphers Subject: XFree86 4.0.2 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 How should I install XFree86 4.0.2 on a system running a -current snapshot from January 20? I tried downloading the binaries from xfree86.org, but Xinstall.sh complained that my extract file was bad (it wasn't), and when I ran 'sh Xinstall.sh -check' it told me that "binaries are not available for this version" of FreeBSD, namely 5.x, despite the fact that I downloaded the binaries from a directory labeled "FreeBSD 5.x". So I tried the ports, and it built fine for a long time, and then after about 35300 lines of output to the screen, ran into make: don't know how to make ../../../fonts/encodings/encodings.dir. Stop *** Error code 2 Stop in /usr/ports/x11/XFree86-4/work/xc/fonts/bdf. This system is a fresh install, except for a custom kernel and some rc.conf changes. Any suggestions other than waiting until cardbus support _finally_ gets in to -stable so I can stop trying to run -current? Thanks, -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 21 0: 1:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunyip.flash.net (bunyip.flash.net [209.30.2.15]) by hub.freebsd.org (Postfix) with ESMTP id 9A69537B401 for ; Sun, 21 Jan 2001 00:01:23 -0800 (PST) Received: from bbnow.net (ip81.seattle34.wa.pub-ip.psi.net [38.28.178.81]) by bunyip.flash.net (8.9.3/Pro-8.9.3) with ESMTP id CAA03242 for ; Sun, 21 Jan 2001 02:01:16 -0600 (CST) Message-ID: <3A6A9729.D382506F@bbnow.net> Date: Sun, 21 Jan 2001 00:00:41 -0800 From: Nathan Zornes X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message