From owner-freebsd-stable@FreeBSD.ORG Sun Dec 11 10:20:57 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6999A16A41F for ; Sun, 11 Dec 2005 10:20:57 +0000 (GMT) (envelope-from dispatcher@ig.every1.net) Received: from aws70.neoplus.adsl.tpnet.pl (aws70.neoplus.adsl.tpnet.pl [83.27.78.70]) by mx1.FreeBSD.org (Postfix) with SMTP id 40B7643D58 for ; Sun, 11 Dec 2005 10:20:56 +0000 (GMT) (envelope-from dispatcher@ig.every1.net) Received: from unknown (HELO molasses) (192.168.65.165) by aws70.neoplus.adsl.tpnet.pl with SMTP; Sun, 11 Dec 2005 11:21:00 +0100 Content-Transfer-Encoding: 7bit Message-Id: <35437101200.124701127505@aws70.neoplus.adsl.tpnet.pl> Content-Type: text/plain; charset=us-ascii To: freebsd-stable@freebsd.org From: Bridget Lopez X-Antivirus: avast! (VPS 0550-0, 2005-12-10), Outbound message X-Antivirus-Status: Clean Date: Sun, 11 Dec 2005 10:20:56 +0000 (GMT) Subject: Bigger, harder, and longer - lasting results NOW with a discreet little patch. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 10:20:57 -0000 ADD 3+ inches today - don't get left behind http://www.kurevalw.net/pt/ Life is a zoo in a jungle. Fishing is a delusion entirely surrounded by liars in old clothes. If I've done anything I'm sorry for, I'm willing to be forgiven. Talk sense to a fool and he calls you foolish. Do not envy a sinner; you don't know what disaster awaits him. From owner-freebsd-stable@FreeBSD.ORG Sun Dec 11 18:22:56 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92ABC16A420 for ; Sun, 11 Dec 2005 18:22:56 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 764AB43D8B for ; Sun, 11 Dec 2005 18:22:47 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id jBBIMfNW013395 for ; Sun, 11 Dec 2005 18:22:41 GMT Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.13.4/8.13.4) with ESMTP id jBBIMf5p073335 for ; Sun, 11 Dec 2005 18:22:41 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from localhost (gavin@localhost) by ury.york.ac.uk (8.13.4/8.13.1/Submit) with ESMTP id jBBIMeB0073332 for ; Sun, 11 Dec 2005 18:22:40 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Sun, 11 Dec 2005 18:22:40 +0000 (GMT) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: freebsd-stable@freebsd.org Message-ID: <20051211181324.G71610@ury.york.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Subject: puc fails to attach serial ports X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 18:22:56 -0000 Hi, I'm trying to use puc(4) under RELENG_6 to attach the two serial ports on a PCI card I have, but it's not working. It also fails under 6.0-RELEASE, I don't have the ability to test earlier versions. The card is developed, but as far as I can see, no attempt is made to attach the sio(4) devices below it. puc0: port 0x18c0-0x18df irq 25 at device 9.0 on pci0 puc0: Reserved 0x20 bytes for rid 0x10 type 4 at 0x18c0 port rid 16 bst 0, start 18c0, end 18df puc0: i 0, type sio, ressz 8, type 1 puc: Using sio2 puc: type 1, bar 10, offset 0 puc0: i 1, type sio, ressz 8, type 1 puc: Using sio3 puc: type 1, bar 10, offset 8 Adding some printfs to the code, it turns out that device_probe_and_attach around line 375 of sys/dev/puc/puc.c is returning 6. I have also added printfs to the probe and attach code of both the pci and puc attachments of sio(4), and have determined that none of them get called. How can I further diagnose why this card is not getting recognised? Thanks, Gavin -- "Experience is directly proportional to the value of equipment destroyed." -- Carolyn Scheppner - Gavin Atkinson - General layabout - University Radio York - From owner-freebsd-stable@FreeBSD.ORG Sun Dec 11 20:14:06 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCDE816A41F for ; Sun, 11 Dec 2005 20:14:06 +0000 (GMT) (envelope-from mikes@siralan.org) Received: from rader.servnow.com (rader5.servnow.com [69.93.129.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4818043D60 for ; Sun, 11 Dec 2005 20:14:06 +0000 (GMT) (envelope-from mikes@siralan.org) Received: from 12-210-221-89.client.insightbb.com ([12.210.221.89] helo=familysquires.net) by rader.servnow.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.52) id 1ElXa3-0002CC-8d for freebsd-stable@freebsd.org; Sun, 11 Dec 2005 15:13:59 -0500 Date: Sun, 11 Dec 2005 15:14:02 -0500 (EST) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: freebsd-stable@freebsd.org In-Reply-To: <20050925142016.L7868@familysquires.net> Message-ID: <20051211145338.J56200@familysquires.net> References: <87y85nuqhy.fsf@beaker.data-secure.net> <4335D1D2.9060501@leadhill.net> <87r7bdt6o3.fsf@beaker.data-secure.net> <20050925142016.L7868@familysquires.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - rader.servnow.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - siralan.org X-Source: X-Source-Args: X-Source-Dir: Subject: Toshiba 8100 Fix (was Re: 5.4-STABLE changes breaks IDE boot (was Re: 5.3 -> 5.4 breaks ATA (Intel ICH2)) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 20:14:07 -0000 I have a Toshiba 8100 notebook which runs 5.4-STABLE. Kernels compiled after some time in September 2005 fail to boot; the machine locks up right after the ata controller is called in the boot messages. I have traced the problem to a change to /usr/src/sys/dev/pci.c, (see below from my cvsup log). I found the problem by cvsup'ing /usr/src for dates starting with my last working kernel and once I had the date of problem code tied down to a couple of days adding in each update to see if it caused the failure to boot. I then added the fix to the latest 5.4 sources to make sure that the fix still worked. The problem (really the Toshiba 8100 BIOS problem) was triggered by: Edit src/sys/dev/pci/pci.c Add delta 1.264.2.12 2005.09.05.18.09.20 imp which changes line 835 of pci.c from if (base == 0) to if (base == 0 || map == testval) The sysctl parameter "hw.pci.enable_io_modes" is supposed to allow PCs with "lazy" BIOSes to boot, but in the case of the 8100 setting hw.pci.enable_io_modes: 0 doesn't allow the system to boot. This is obviously a problem with the Toshiba BIOS, which I know from other times has other problems; I am putting this here in case someone else has the same problem and wants to boot FreeBSD 5.4-STABLE with a kernel revision after 9/5/2005. Mike Squires From owner-freebsd-stable@FreeBSD.ORG Sun Dec 11 22:58:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E356416A41F; Sun, 11 Dec 2005 22:58:32 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [203.96.152.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4B5143D45; Sun, 11 Dec 2005 22:58:31 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-3.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-1.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IRC00NCPVTH3B@linda-1.paradise.net.nz>; Mon, 12 Dec 2005 11:58:29 +1300 (NZDT) Received: from [192.168.1.11] (218-101-29-214.dsl.clear.net.nz [218.101.29.214]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id D6C8A280EDC; Mon, 12 Dec 2005 11:58:27 +1300 (NZDT) Date: Mon, 12 Dec 2005 11:58:26 +1300 From: Mark Kirkwood In-reply-to: <000101c5fcf8$05dbd870$59ab3a40@sleuth> To: vizion Message-id: <439CAF12.10107@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106) References: <000101c5fcf8$05dbd870$59ab3a40@sleuth> Cc: 'Peter Jeremy' , 'Doug Barton' , freebsd-stable@freebsd.org, "'Michael C. Shultz'" Subject: Re: Freebsd Stable documentation X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 22:58:33 -0000 vizion wrote: > Thiis was originally > Upgrading 5.3 > 6.0 buildworld failure now in libmagic > And on Mike Shultz recommendation I have relabeled the topic > > (mass snippage) > I have not tried to upgrade directly from 5.3 -> 6.0 (however, I did do 5.4 -> early 6-current a few months ago, so this is topic of interest for me). I guess I would recommend doing this: 1) Work out how to successfully perform the upgrade (using help from this list). 2) Note what changes are needed to the upgrading section of the Handbook, patch the src SGML, and submit said patch to freebsd-doc. I should add that I have not actually tried this plan myself - however I have been involved in a similar sort of thing with Postgresql - their docs list guys were very receptive to some patches I submitted. I suspect the Freebsd folks would be too. Cheers Mark From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 08:10:04 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6408316A41F for ; Mon, 12 Dec 2005 08:10:04 +0000 (GMT) (envelope-from gmenhennitt@optusnet.com.au) Received: from mail28.syd.optusnet.com.au (mail28.syd.optusnet.com.au [211.29.133.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id B754A43D64 for ; Mon, 12 Dec 2005 08:10:03 +0000 (GMT) (envelope-from gmenhennitt@optusnet.com.au) Received: from [203.2.73.8] (c220-237-136-178.mckinn1.vic.optusnet.com.au [220.237.136.178]) by mail28.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBC89vRF005844 for ; Mon, 12 Dec 2005 19:10:02 +1100 Message-ID: <439D3053.3020504@optusnet.com.au> Date: Mon, 12 Dec 2005 19:09:55 +1100 From: Graham Menhennitt User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: puzzling "ipfw show" output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 08:10:04 -0000 I got the following output from "ipfw show" in my daily security run output email. +++ /tmp/security.yri47lgA Mon Dec 12 03:01:45 2005 +00522 3530 1204158 deny ip from 10.0.0.0/8 to any via sis1 +02522 18 784 deny tcp from any to any in via sis1 setup +65530 0 0 deny ip from any to any +65535 2 688 deny ip from any to any Could somebody please explain to me how those packets got past rule 65530 to be stopped by (the identical) rule 65535? The ipfw rules have not changed since the machine rebooted. The only explanation I have is that the packets arrived between the time when the machine started accepting incoming packets and when the rules were loaded in /etc/rc.d/ipfw. If that's the case, it's a pretty good argument for defaulting to rejecting packets. Didn't somebody here suggest that this wasn't really necessary a few weeks ago (something to do with using pf)? Graham From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 08:39:48 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3314F16A420 for ; Mon, 12 Dec 2005 08:39:48 +0000 (GMT) (envelope-from trond@ramstind.gtf.ol.no) Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6006143D58 for ; Mon, 12 Dec 2005 08:39:47 +0000 (GMT) (envelope-from trond@ramstind.gtf.ol.no) Received: from ramstind.gtf.ol.no (Ximalas@localhost [127.0.0.1]) by ramstind.gtf.ol.no (8.12.9/8.12.9) with ESMTP id jBC8djjA053085 for ; Mon, 12 Dec 2005 09:39:45 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.12.9/8.12.3/Submit) with ESMTP id jBC8djIR053082 for ; Mon, 12 Dec 2005 09:39:45 +0100 (CET) Date: Mon, 12 Dec 2005 09:39:44 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= To: FreeBSD stable In-Reply-To: <439D3053.3020504@optusnet.com.au> Message-ID: <20051212092932.T40542@ramstind.gtf.ol.no> References: <439D3053.3020504@optusnet.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Subject: Re: puzzling "ipfw show" output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 08:39:48 -0000 On Mon, 12 Dec 2005 19:09+1100, Graham Menhennitt wrote: > The only explanation I have is that the packets arrived between the > time when the machine started accepting incoming packets and when > the rules were loaded in /etc/rc.d/ipfw. You just explained this yourself. One solution to this small problem could be to change part of the boot sequence into this: a. Create VLAN interfaces etc if configured, assign IP addresses to each configured interface, but do not UP them. b. Load the firewall rules, and optionally turn on forwarding. c. Set all configured interfaces to UP. One last question: Why do you need rule 65530 when the built-in rule 65535 does the same job? -- ---------------------------------------------------------------------- Trond Endrestřl | trond@fagskolen.gjovik.no Patron of The Art of Computer Programming| FreeBSD 4.8-S & Pine 4.55 From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 11:03:43 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3F6916A420 for ; Mon, 12 Dec 2005 11:03:43 +0000 (GMT) (envelope-from pherman@frenchfries.net) Received: from alcatraz.frenchfries.net (216-73-106-93.ocdc-01.net [216.73.106.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id E68D743D45 for ; Mon, 12 Dec 2005 11:03:21 +0000 (GMT) (envelope-from pherman@frenchfries.net) Received: from localhost (alcatraz [216.73.106.93]) by alcatraz.frenchfries.net (Postfix) with ESMTP id 6D0B3C6481 for ; Mon, 12 Dec 2005 03:02:59 -0800 (PST) Date: Mon, 12 Dec 2005 12:02:57 +0100 (CET) From: Paul Herman X-X-Sender: pherman@tahoe.cgn.cleverbridge.com To: FreeBSD Stable MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Message-Id: <20051212110259.6D0B3C6481@alcatraz.frenchfries.net> Subject: 6.0-STABLE setkey panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 11:03:43 -0000 Hi all, Just installed 6.0-STABLE/amd64 (cvsup from within the last day) onto a K8 Sempron with IPSEC compiled in and I get a kernel panic when I try to run racoon. Anyone else seen this? Unfortunately the usual ways I know how to debug don't work: * "kgdb /path/to/kernel.debug /var/crash/vmcore.0" hangs and takes 100% CPU (20% user, 80% system) * "kgdb /boot/kernel/kernel /var/crash/vmcore.0" gives me a backtrace, but no symbols and looks like the stack is mangled anyway. * Falling into DDB on the console after the panic refuses to provide any kind of backtrace, it complains that the stack is garbled. The good news: I can reproduce this at any time with just "setkey -D". No special kernel tweaks except for adding IPSEC into the config, so I'm hoping many of you can reproduce this, and hopefuly someone else with more debugging foo. Anyone? -Paul. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 14:01:24 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E96A216A424 for ; Mon, 12 Dec 2005 14:01:24 +0000 (GMT) (envelope-from content-filter@makana.gov.za) Received: from smtp2.imaginet.co.za (smtp2.imaginet.co.za [196.34.166.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C99143D76 for ; Mon, 12 Dec 2005 14:01:06 +0000 (GMT) (envelope-from content-filter@makana.gov.za) Received: from [196.211.28.150] (helo=makana.gov.za) by smtp2.imaginet.co.za with esmtpa (Exim 4.50 (FreeBSD)) id 1EloEZ-000OTF-K7 for freebsd-stable@freebsd.org; Mon, 12 Dec 2005 16:00:59 +0200 Received: from 192.168.13.10 for freebsd-stable@freebsd.org; Mon, 12 Dec 2005 16:00:28 +0200 From: "WorkgroupMail Content Filter" To: freebsd-stable@freebsd.org Sender: "WorkgroupMail Content Filter" Date: Mon, 12 Dec 2005 16:00:27 +0200 X-WM-Plugin-Generated: MailScan MIME-Version: 1.0 Content-type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Message-ID: X-Whitelisted: The user has authenticated (1). X-Whitelisted: The user has Authenticated (2). Subject: QUARANTINED: Mail System Error - Returned Mail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 14:01:25 -0000 The message "Mail System Error - Returned Mail" from MAILER-DAEMON, sent on 12/12/2005 15:55 was quarantined because it contained either an executable file, a batch file or a screen saver file. All of these types of attachments are considered security risks. Please consult your mail administrator who can release the message. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 14:04:51 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3484F16A41F for ; Mon, 12 Dec 2005 14:04:51 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 062A343D5C for ; Mon, 12 Dec 2005 14:04:48 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jBCE4l44030384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Dec 2005 17:04:47 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jBCE4kQa030383; Mon, 12 Dec 2005 17:04:46 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 12 Dec 2005 17:04:46 +0300 From: Gleb Smirnoff To: Gavin Atkinson Message-ID: <20051212140446.GQ37414@FreeBSD.org> References: <20051211181324.G71610@ury.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20051211181324.G71610@ury.york.ac.uk> User-Agent: Mutt/1.5.6i Cc: freebsd-stable@FreeBSD.org Subject: Re: puc fails to attach serial ports X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 14:04:51 -0000 On Sun, Dec 11, 2005 at 06:22:40PM +0000, Gavin Atkinson wrote: G> I'm trying to use puc(4) under RELENG_6 to attach the two serial ports on G> a PCI card I have, but it's not working. It also fails under 6.0-RELEASE, G> I don't have the ability to test earlier versions. G> G> The card is developed, but as far as I can see, no attempt is made to G> attach the sio(4) devices below it. G> G> puc0: port 0x18c0-0x18df irq 25 at device 9.0 on G> pci0 G> puc0: Reserved 0x20 bytes for rid 0x10 type 4 at 0x18c0 G> port rid 16 bst 0, start 18c0, end 18df G> puc0: i 0, type sio, ressz 8, type 1 G> puc: Using sio2 G> puc: type 1, bar 10, offset 0 G> puc0: i 1, type sio, ressz 8, type 1 G> puc: Using sio3 G> puc: type 1, bar 10, offset 8 G> G> Adding some printfs to the code, it turns out that device_probe_and_attach G> around line 375 of sys/dev/puc/puc.c is returning 6. G> G> I have also added printfs to the probe and attach code of both the pci and G> puc attachments of sio(4), and have determined that none of them get G> called. G> G> How can I further diagnose why this card is not getting recognised? Afaik, you need 'device uart', that will attach to your pucs. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 15:04:27 2005 Return-Path: X-Original-To: stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E67C616A41F for ; Mon, 12 Dec 2005 15:04:27 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30CCD43DB3 for ; Mon, 12 Dec 2005 15:04:07 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.52 (FreeBSD)) id 1ElpDb-000KqX-TX for stable@FreeBSD.ORG; Mon, 12 Dec 2005 15:03:59 +0000 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.52 (FreeBSD)) id 1ElpDb-000DnG-Mf for stable@FreeBSD.ORG; Mon, 12 Dec 2005 15:03:59 +0000 To: stable@FreeBSD.ORG Message-Id: From: Pete French Date: Mon, 12 Dec 2005 15:03:59 +0000 Cc: Subject: Any vital post 6.0 fixes gone into stable ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 15:04:28 -0000 I'm about to start installing a whole new set of machines for production use with 6.0 on them. Normally I would just use -RELEASE, but as this is a dot-nought release I was wondering if there is anything vital which has been commited to stable, and if I should therefore sun the machines under stable instead. I havent seen anything go past which I regard as critical, though somebody did make a mention of some arp problem being fixed, which I could find a reference to the original problem for. Anything I need to know ? Am running release on a couple of machines here and it works fine for me so far, but always good to get other opinions. -pcf. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 15:57:01 2005 Return-Path: X-Original-To: stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54FCC16A41F for ; Mon, 12 Dec 2005 15:57:01 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout1-sn1.fre.skanova.net (pne-smtpout1-sn1.fre.skanova.net [81.228.11.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 460EC43D55 for ; Mon, 12 Dec 2005 15:56:55 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from royal64.emp.zapto.org (195.198.193.104) by pne-smtpout1-sn1.fre.skanova.net (7.2.060.1) id 4396EEA40016F013; Mon, 12 Dec 2005 16:56:54 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Mon, 12 Dec 2005 16:56:53 +0100 Message-ID: <4F9C9299A10AE74E89EA580D14AA10A605F575@royal64.emp.zapto.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Any vital post 6.0 fixes gone into stable ? thread-index: AcX/LXfOBrqH1iNvR2CzEUT7dvxnrwABrzsg From: "Daniel Eriksson" To: Cc: Pete French Subject: RE: Any vital post 6.0 fixes gone into stable ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 15:57:01 -0000 Pete French wrote: > I havent seen anything go past which I regard as > critical, though somebody did make a mention of some arp problem > being fixed, which I could find a reference to the original=20 > problem for. The ARP problem is not in -RELEASE, it was introduced in -STABLE and fixed a day later. /Daniel Eriksson From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 16:16:49 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BF6816A41F for ; Mon, 12 Dec 2005 16:16:49 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 048DD43D5E for ; Mon, 12 Dec 2005 16:16:47 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by xproxy.gmail.com with SMTP id i31so1034352wxd for ; Mon, 12 Dec 2005 08:16:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ErinM3/OpVvbvxCLmbaL9Z4K75XHXCCDFZ+wS65ndbWRuVVpsjHYzWaz8476xYGbxYt3GRQXcApqLr6kP8DLhBpSU9sDZUue/SyoBMHAIzBuwVmI22kOc1VZKG5OasyZdNv7hN118+Hxqp11jDb7k7yXAMe9vPBtBIE/LxAWe6A= Received: by 10.70.96.9 with SMTP id t9mr9646498wxb; Mon, 12 Dec 2005 08:16:40 -0800 (PST) Received: by 10.70.31.5 with HTTP; Mon, 12 Dec 2005 08:16:40 -0800 (PST) Message-ID: <790a9fff0512120816v1f449490sd59a80a380870932@mail.gmail.com> Date: Mon, 12 Dec 2005 10:16:40 -0600 From: Scot Hetzel To: Graham Menhennitt In-Reply-To: <439D3053.3020504@optusnet.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <439D3053.3020504@optusnet.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: puzzling "ipfw show" output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 16:16:49 -0000 On 12/12/05, Graham Menhennitt wrote: > I got the following output from "ipfw show" in my daily security run outp= ut email. > > +++ /tmp/security.yri47lgA Mon Dec 12 03:01:45 2005 > +00522 3530 1204158 deny ip from 10.0.0.0/8 to any via sis1 > +02522 18 784 deny tcp from any to any in via sis1 setup > +65530 0 0 deny ip from any to any > +65535 2 688 deny ip from any to any > > Could somebody please explain to me how those packets got past rule 65530= to be stopped by (the identical) rule 65535? The ipfw rules have not chang= ed since the machine rebooted. The only explanation I have is that the pack= ets arrived between the time when the machine started accepting incoming pa= ckets and when the rules were loaded in /etc/rc.d/ipfw. > > If that's the case, it's a pretty good argument for defaulting to rejecti= ng packets. Didn't somebody here suggest that this wasn't really necessary = a few weeks ago (something to do with using pf)? > This is exactly what compiling your kernel with IPFIREWALL does, it defaults to denying packets by default. You can change this behavior by adding IPFIREWALL_DEFAULT_TO_ACCEPT but is strongly discouraged. See sys/conf/NOTES ( http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/conf/NOTES?rev=3D1.1337&conte= nt-type=3Dtext/x-cvsweb-markup ) for pf you need to add IPFILTER_DEFAULT_BLOCK to block packets by default. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 16:32:14 2005 Return-Path: X-Original-To: stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAB4416A420 for ; Mon, 12 Dec 2005 16:32:14 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C21643D5A for ; Mon, 12 Dec 2005 16:32:14 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.52 (FreeBSD)) id 1Elqay-000P1E-Uo; Mon, 12 Dec 2005 16:32:12 +0000 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.52 (FreeBSD)) id 1Elqay-000DyG-R5; Mon, 12 Dec 2005 16:32:12 +0000 To: daniel_k_eriksson@telia.com, stable@FreeBSD.ORG In-Reply-To: <4F9C9299A10AE74E89EA580D14AA10A605F575@royal64.emp.zapto.org> Message-Id: From: Pete French Date: Mon, 12 Dec 2005 16:32:12 +0000 Cc: Subject: RE: Any vital post 6.0 fixes gone into stable ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 16:32:15 -0000 > The ARP problem is not in -RELEASE, it was introduced in -STABLE and > fixed a day later. Ah, O.K. thanks -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 20:21:33 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B60816A41F for ; Mon, 12 Dec 2005 20:21:33 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out1.tiscali.nl (smtp-out1.tiscali.nl [195.241.79.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD35C43D62 for ; Mon, 12 Dec 2005 20:21:32 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out1.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1EluAt-0000hL-Ti for ; Mon, 12 Dec 2005 21:21:32 +0100 Received: (qmail 952 invoked from network); 12 Dec 2005 20:21:30 -0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 12 Dec 2005 20:21:30 -0000 To: stable@freebsd.org References: Message-ID: Date: Mon, 12 Dec 2005 21:21:29 +0100 From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Opera M2/8.51 (FreeBSD, build 1462) Cc: Subject: Re: Any vital post 6.0 fixes gone into stable ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 20:21:33 -0000 On Mon, 12 Dec 2005 16:03:59 +0100, Pete French wrote: > I'm about to start installing a whole new set of machines for production > use with 6.0 on them. Normally I would just use -RELEASE, but as this is > a dot-nought release I was wondering if there is anything vital which > has been commited to stable, and if I should therefore sun the machines > under stable instead. I havent seen anything go past which I regard as > critical, though somebody did make a mention of some arp problem > being fixed, which I could find a reference to the original problem for. > > Anything I need to know ? Am running release on a couple of machines here > and it works fine for me so far, but always good to get other opinions. Try downloading an iso and search for release notes in it (RELNOTES.txt or something like that.) ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/Dec_2005/ I don't know how often these are updated. Ronald. -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 21:08:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FB6216A420 for ; Mon, 12 Dec 2005 21:08:27 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35BCB43D6A for ; Mon, 12 Dec 2005 21:08:22 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.41] (asd0.aplus.net [216.55.129.41]) (authenticated bits=0) by pro20.abac.com (8.13.4/8.13.4) with ESMTP id jBCL8KQu069475 for ; Mon, 12 Dec 2005 13:08:20 -0800 (PST) (envelope-from atanas@asd.aplus.net) Message-ID: <439DE88B.1090407@asd.aplus.net> Date: Mon, 12 Dec 2005 13:15:55 -0800 From: Atanas User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: multipart/mixed; boundary="------------010501090004000608080205" X-Spam-Score: 1.47 (SPF_SOFTFAIL) Subject: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 21:08:27 -0000 This is a multi-part message in MIME format. --------------010501090004000608080205 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I have 3 machines running 6.0-RELEASE, and recently 2 of them started freezing once a day or so. There are no error messages on the console or in the system logs. The first one I put in production about a month ago and it was working flawlessly until it got some load and now it started freezing almost every day. The second one has exactly the same behavior - it was fine when doing nothing (a couple of weeks), and started freezing when loaded. The load I'm talking about is less than moderate (less that 2.0 with plenty of CPU idle time). The freezing thing also does not appear to happen at peak times (I have rrdtool based CPU load graphs). Both machines have (almost) identical motherboards: Intel SE7520JR2SCSID2 and SE7520JR2ATAD2 2 Intel XeonE 3.2GHz 800MHz CPUs 4GB DDRII400 RegECC RAM The first one has 8 72GB Ultra320 SCSI drives attached as plain drives (no raid) to the on-board . The second one has 8 500GB SATA2 drives attached to a <3ware Model 9550SX-8LP> controller and configured as a RAID5 array. The motherboards have 2 1000Mbps NICs on board, but due to some (em) driver problems, I usually disable these from BIOS and use a PCI Intel 100Mbps (fxp) instead. Both machines were running 6.0-RELEASE, i386. For the last one I had to updated the twa driver manually, as the one shipped with 6.0 didn't support 3ware 9550SX. I see that new version recently got committed into the -STABLE branches. Here are the diffs against the GENERIC kernel configuration: < cpu I486_CPU < cpu I586_CPU < makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols < options INET6 # IPv6 communications protocols 53d47 < options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI > options QUOTA > options SMP # Symmetric MultiProcessor Kernel /boot/loader.conf: kern.ipc.nmbclusters="65536" /etc/stysctl.conf: kern.ipc.somaxconn=1024 net.inet.tcp.recvspace=16384 net.inet.ip.fw.verbose=1 machdep.hyperthreading_allowed=1 Both machines boot with ACPI and hyperthreading enabled. First I suspected the hardware, so I replaced the entire box (keeping the same drives) - no changes - it got frozen again in less than 24 hours. Then I disabled ACPI (hint.acpi.0.disabled="1") and the hyperthreading - no change - the same thing. Then after reading all related (I believe) postings here and in freebsd-current, I decided to upgrade both boxes to 6.0-STABLE (I saw a lot of changes in the source tree), but the thing continued to happen. I have another machine with the same hardware components (the SCSI based one), but running 5.4-RELEASE. Unlike these two, it's really loaded (even got DDoS-ed a while ago) and I had zero problems with it for months. I remember having similar issues when performing 4GB RAM upgrades on a bunch of 4.x based boxes, when I had to set KVA_PAGES to something like 512. For 5.3+ however this is no longer seems to be an issue. I would provide more useful feedback if I had some real and relevant error messages. Actually I got some unusual errors on only one of the affected servers: Dec 11 02:48:36 xyz kernel: calcru: runtime went backwards from 28636364 usec to 28636021 usec for pid 28588 (httpd) But it does not seem to be much relevant to the problem as it did not happened to be any close to the freezes (i.e. it was 26 hours after the last crash and 19 hours before the next one). Now the only reasonable option for me (I mean for production and in relatively short term) seems going downward to 5.4 and wait until 6.x get more stable Two dmesg.boot files attached. Any comments, suggestions and questions are welcome. Regards, Atanas --------------010501090004000608080205 Content-Type: text/plain; name="dmesg.boot-sata" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.boot-sata" Copyright (c) 1992-2005 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 6.0-STABLE #0: Fri Dec 9 14:54:05 PST 2005 root@xyz:/var/obj/usr/src/sys/XYZ ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3192.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20100000 Hyperthreading: 2 logical CPUs real memory = 3757965312 (3583 MB) avail memory = 3678597120 (3508 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic2: Changing APIC ID to 10 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 cpu2: on acpi0 acpi_throttle2: on cpu2 acpi_throttle2: failed to attach P_CNT device_attach: acpi_throttle2 attach returned 6 cpu3: on acpi0 acpi_throttle3: on cpu3 acpi_throttle3: failed to attach P_CNT device_attach: acpi_throttle3 attach returned 6 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 1.0 (no driver attached) pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 fxp0: port 0xdc00-0xdc3f mem 0xfcffe000-0xfcffefff,0xfcfa0000-0xfcfbffff irq 28 at device 2.0 on pci2 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:0e:0c:9c:47:a8 3ware device driver for 9000 series storage controllers, version: 3.60.02.012 twa0: <3ware 9000 series Storage Controller> port 0xdc80-0xdcbf mem 0xfa000000-0xfbffffff,0xfcfff000-0xfcffffff irq 27 at device 3.0 on pci2 twa0: [FAST] twa0: WARNING: (0x04: 0x0008): Unclean shutdown detected: unit=0 twa0: INFO: (0x15: 0x1300): Controller details:: Model 9550SX-8LP, 8 ports, Firmware FE9X 3.02.00.004, BIOS BE9X 3.01.00.024 pcib3: at device 0.2 on pci1 pci3: on pcib3 pcib4: at device 30.0 on pci0 pci4: on pcib4 pci4: at device 12.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xca7ff,0xca800-0xcbfff,0xcc000-0xcd7ff,0xd5000-0xdb7ff on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 twa0: ERROR: (0x03: 0x01d0): Invalid field in parameter list: da0 at twa0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 100.000MB/s transfers da0: 2860962MB (5859250176 512 byte sectors: 255H 63S/T 364721C) SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Trying to mount root from ufs:/dev/da0s1a WARNING: / was not properly dismounted WARNING: /home/u1 was not properly dismounted /home/u1: mount pending error: blocks 888 files 2 WARNING: /home/u2 was not properly dismounted WARNING: /var was not properly dismounted /var: mount pending error: blocks 292 files 1 ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled Accounting enabled --------------010501090004000608080205 Content-Type: text/plain; name="dmesg.boot-scsi" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.boot-scsi" Copyright (c) 1992-2005 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 6.0-STABLE #0: Fri Dec 9 11:52:26 PST 2005 root@xyz:/var/obj/usr/src/sys/XYZ ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3192.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20100000 Hyperthreading: 2 logical CPUs real memory = 3757965312 (3583 MB) avail memory = 3678597120 (3508 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic2: Changing APIC ID to 10 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 cpu2: on acpi0 acpi_throttle2: on cpu2 acpi_throttle2: failed to attach P_CNT device_attach: acpi_throttle2 attach returned 6 cpu3: on acpi0 acpi_throttle3: on cpu3 acpi_throttle3: failed to attach P_CNT device_attach: acpi_throttle3 attach returned 6 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 1.0 (no driver attached) pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 fxp0: port 0xd480-0xd4bf mem 0xfcfd7000-0xfcfd7fff,0xfcf80000-0xfcf9ffff irq 27 at device 3.0 on pci2 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:0e:0c:9c:4c:87 mpt0: port 0xd800-0xd8ff mem 0xfcfc0000-0xfcfcffff,0xfcfb0000-0xfcfbffff irq 26 at device 5.0 on pci2 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.14.0 mpt0: Unhandled Event Notify Frame. Event 0xa. mpt0: Capabilities: ( RAID-1E RAID-1 SAFTE ) mpt0: 0 Active Volumes (1 Max) mpt0: 0 Hidden Drive Members (6 Max) mpt1: port 0xdc00-0xdcff mem 0xfcff0000-0xfcffffff,0xfcfe0000-0xfcfeffff irq 25 at device 5.1 on pci2 mpt1: [GIANT-LOCKED] mpt1: MPI Version=1.2.14.0 mpt1: Unhandled Event Notify Frame. Event 0xa. mpt1: Capabilities: ( RAID-1E RAID-1 SAFTE ) mpt1: 0 Active Volumes (1 Max) mpt1: 0 Hidden Drive Members (6 Max) pcib3: at device 0.2 on pci1 pci3: on pcib3 pcib4: at device 30.0 on pci0 pci4: on pcib4 pci4: at device 12.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xcc80-0xcc87,0xcc00-0xcc03,0xc880-0xc887,0xc800-0xc803,0xc480-0xc48f irq 18 at device 31.2 on pci0 atapci1: failed to enable memory mapping! ata2: on atapci1 ata3: on atapci1 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xca7ff,0xca800-0xce7ff on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 ad4: 476940MB at ata2-master SATA150 Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! da1 at mpt0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da3 at mpt0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da3: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da2 at mpt0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da5 at mpt0 bus 0 target 5 lun 0 da5: Fixed Direct Access SCSI-3 device da5: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da5: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da4 at mpt0 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI-3 device da4: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da4: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da6 at mpt0 bus 0 target 6 lun 0 da6: Fixed Direct Access SCSI-3 device da6: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da6: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da7 at mpt0 bus 0 target 8 lun 0 da7: Fixed Direct Access SCSI-3 device da7: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da7: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) Trying to mount root from ufs:/dev/da0s1a WARNING: / was not properly dismounted ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled Accounting enabled --------------010501090004000608080205-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 21:23:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15FDA16A41F for ; Mon, 12 Dec 2005 21:23:32 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE15A43D78 for ; Mon, 12 Dec 2005 21:23:25 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1482907nzo for ; Mon, 12 Dec 2005 13:23:21 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FIDCFocVOjbSuQggbR6N0QGu3owMcuPK6WU/9/lgTVBMCUJde8rDM/1ded9Y8yAKCnMGVl3hC2KOAZvdmbSahYFHdPRtDF1fZxO7mvsUa807vQCk1y5bp3za4f0MG6VlXyzQGIzeY/iaclpxr8XVh/JkFtYyaBb4awf9oz1nDTU= Received: by 10.64.253.16 with SMTP id a16mr97714qbi; Mon, 12 Dec 2005 13:23:20 -0800 (PST) Received: by 10.65.192.14 with HTTP; Mon, 12 Dec 2005 13:23:20 -0800 (PST) Message-ID: Date: Mon, 12 Dec 2005 22:23:20 +0100 From: Claus Guttesen To: Atanas In-Reply-To: <439DE88B.1090407@asd.aplus.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <439DE88B.1090407@asd.aplus.net> Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 21:23:32 -0000 > The load I'm talking about is less than moderate (less that 2.0 with > plenty of CPU idle time). The freezing thing also does not appear to > happen at peak times (I have rrdtool based CPU load graphs). > > Both machines have (almost) identical motherboards: > > Intel SE7520JR2SCSID2 and SE7520JR2ATAD2 > 2 Intel XeonE 3.2GHz 800MHz CPUs > 4GB DDRII400 RegECC RAM > Both machines boot with ACPI and hyperthreading enabled. Try to disable HTT in bios. It seldom gives you very much, and somtetimes degrades performance. Is it a webserver? If it generates alot of temporary files you can try adding/changing the following in /etc/sysctl.conf: kern.ipc.somaxconn=3D2048 kern.maxfiles=3D65536 vfs.ufs.dirhash_maxmem=3D8388608 regards Claus From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 21:27:28 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAACD16A41F for ; Mon, 12 Dec 2005 21:27:28 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out2.tiscali.nl (smtp-out2.tiscali.nl [195.241.79.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id C57F043D6D for ; Mon, 12 Dec 2005 21:27:25 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out2.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1ElvCd-0001V9-V2 for ; Mon, 12 Dec 2005 22:27:24 +0100 Received: (qmail 21577 invoked from network); 12 Dec 2005 21:27:23 -0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 12 Dec 2005 21:27:23 -0000 Date: Mon, 12 Dec 2005 22:27:22 +0100 To: Atanas , freebsd-stable@freebsd.org References: <439DE88B.1090407@asd.aplus.net> From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <439DE88B.1090407@asd.aplus.net> User-Agent: Opera M2/8.51 (FreeBSD, build 1462) Cc: Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 21:27:28 -0000 On Mon, 12 Dec 2005 22:15:55 +0100, Atanas wrote: > Hi, > > I have 3 machines running 6.0-RELEASE, and recently 2 of them started > freezing once a day or so. There are no error messages on the console or > in the system logs. What happens if you set one of these sysctl values to 0? (This disables SMP changes from 5.4 to 6.0.) debug.mpsafevfs: 1 debug.mpsafenet: 1 debug.mpsafevm: 1 And is there a possibility (performance-wise) to build a kernel with WITNESS and/or INVARIANTS options compiled in. This will give more info about possible locking problems. Your system will run slower. And because of this the problem may not occur anymore, but it is worth the try. Ronald. -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 21:40:20 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDA0716A41F for ; Mon, 12 Dec 2005 21:40:20 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2232D43D55 for ; Mon, 12 Dec 2005 21:40:18 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail09.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBCLe4L0026188 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Dec 2005 08:40:05 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBCLe4Hh077294; Tue, 13 Dec 2005 08:40:04 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBCLe4lo077293; Tue, 13 Dec 2005 08:40:04 +1100 (EST) (envelope-from pjeremy) Date: Tue, 13 Dec 2005 08:40:04 +1100 From: Peter Jeremy To: Atanas Message-ID: <20051212214003.GA77268@cirb503493.alcatel.com.au> References: <439DE88B.1090407@asd.aplus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <439DE88B.1090407@asd.aplus.net> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 21:40:20 -0000 On Mon, 2005-Dec-12 13:15:55 -0800, Atanas wrote: >I have 3 machines running 6.0-RELEASE, and recently 2 of them started >freezing once a day or so. There are no error messages on the console or >in the system logs. > >The first one I put in production about a month ago and it was working >flawlessly until it got some load and now it started freezing almost >every day. The second one has exactly the same behavior - it was fine >when doing nothing (a couple of weeks), and started freezing when loaded. Define "freezing": Does it respond to pings? Can you switch VTYs? Do the num-lock/caps-lock LEDs respond? Do some processes seem to freeze before others? I suggest you add the following to your kernel config: options KDB # Enable kernel debugger support. options DDB # Support DDB. When it hangs, break into DDB (Ctrl-Alt-Esc on the console or BREAK on a serial console). As a start, run 'show lockedvnods' and 'ps'. My guess is that you'll see a lock that has a number of waiters - which is probably the culprit. Use 'panic' or 'call doadump' to get a crashdump and then you can use kgdb to rummage around once you reboot - see http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebg-gdb.html >< makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols I suggest you add this back in. Without it, you can't debug any crash dumps that you manage to get (and add "dumpdev" to your rc.conf). >Now the only reasonable option for me (I mean for production and in >relatively short term) seems going downward to 5.4 and wait until 6.x >get more stable Whilst I realise that you can't have production machines freezing on schedule, your assistance in providing more information about your problem will help make 6.x more stable. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 23:33:55 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CCA316A41F for ; Mon, 12 Dec 2005 23:33:55 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15D4E43D4C for ; Mon, 12 Dec 2005 23:33:55 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.41] (asd0.aplus.net [216.55.129.41]) (authenticated bits=0) by pro20.abac.com (8.13.4/8.13.4) with ESMTP id jBCNXoa6099122 for ; Mon, 12 Dec 2005 15:33:51 -0800 (PST) (envelope-from atanas@asd.aplus.net) Message-ID: <439E0AA6.5070300@asd.aplus.net> Date: Mon, 12 Dec 2005 15:41:26 -0800 From: Atanas User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <439DE88B.1090407@asd.aplus.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 23:33:55 -0000 Claus Guttesen said the following on 12/12/05 13:23: >>Both machines boot with ACPI and hyperthreading enabled. > > Try to disable HTT in bios. > I think that I already achieved that by simply disabling the acpi module from device.hints, and it had no effect to the problem. > It seldom gives you very much, and > somtetimes degrades performance. Is it a webserver? > It is a web server, and as such it tends to generate a lot of processes, many of them independent of each other and trying to run simultaneously. Thus more work horses (even less powerful virtual CPUs) make the server to perform smoother. This is just a practical observation though, and I could be wrong. I would rather go with 2 dual core Opterons, but these are sort of expensive for now. > If it generates > alot of temporary files you can try adding/changing the following in > /etc/sysctl.conf: > > kern.ipc.somaxconn=2048 > kern.maxfiles=65536 > vfs.ufs.dirhash_maxmem=8388608 > Currently I have the following: kern.ipc.somaxconn: 1024 kern.maxfiles: 12328 vfs.ufs.dirhash_maxmem: 2097152 kern.openfiles: 1992 It's closest relative (running 5.4-RELEASE on the same hardware) handles about twice more requests, temporary files, and open files. kern.openfiles there is about 4000, and if something tries to go above the limits, the kernel usually reports that. I have plenty of other boxes serving at least twice more requests with less powerful (also hyperthreaded) CPUs running 4.x and 5.x and with no problems. The ones I have problems with are way less loaded, and are supposedly faster ones. Thanks for your suggestions! Regards, Atanas From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 23:36:06 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B05C16A420 for ; Mon, 12 Dec 2005 23:36:06 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9AE043D81 for ; Mon, 12 Dec 2005 23:35:58 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.41] (asd0.aplus.net [216.55.129.41]) (authenticated bits=0) by pro20.abac.com (8.13.4/8.13.4) with ESMTP id jBCNZt4S002174; Mon, 12 Dec 2005 15:35:56 -0800 (PST) (envelope-from atanas@asd.aplus.net) Message-ID: <439E0B23.3060304@asd.aplus.net> Date: Mon, 12 Dec 2005 15:43:31 -0800 From: Atanas User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ronald Klop , freebsd-stable@freebsd.org References: <439DE88B.1090407@asd.aplus.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 23:36:06 -0000 Ronald Klop said the following on 12/12/05 13:27: > > What happens if you set one of these sysctl values to 0? (This disables > SMP changes from 5.4 to 6.0.) > debug.mpsafevfs: 1 > debug.mpsafenet: 1 > debug.mpsafevm: 1 > Thanks for the suggestion! I just did so and rebooted both machines, so we'll see. I remember unseting debug.mpsafenet before 5.4 due to some ipfw limitations, but didn't know about the other two. > And is there a possibility (performance-wise) to build a kernel with > WITNESS and/or INVARIANTS options compiled in. This will give more info > about possible locking problems. Your system will run slower. And > because of this the problem may not occur anymore, but it is worth the > try. > Both machines are not much loaded, so I could afford slowing them down a bit for a while (I hope it won't be several times slower). I will do that at some point later if the problem still persists. I hope I won't be forced to downgrade to 5.4, though I'm already working on that (just in case). Regards, Atanas From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 02:21:54 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5ED416A41F for ; Tue, 13 Dec 2005 02:21:54 +0000 (GMT) (envelope-from fredthetree@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id D367643D58 for ; Tue, 13 Dec 2005 02:21:53 +0000 (GMT) (envelope-from fredthetree@gmail.com) Received: by wproxy.gmail.com with SMTP id i4so25440wra for ; Mon, 12 Dec 2005 18:21:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=U23QuWwx0/3XB3LsUkzjSlZSQVJmfqpNdiDiBDmqYDMknEZYsGhbBjJdyLKbp8xf7Pn89lacx/67E+3AtN5EdxZusoTCue183Fvu3GBtgqo36HDkEms23MedtfCaXAtMKKoKQyc13omZ/mMnblRZD+EKH5pew0WQ/BR01hlmvFQ= Received: by 10.54.159.5 with SMTP id h5mr204446wre; Mon, 12 Dec 2005 18:21:52 -0800 (PST) Received: by 10.54.146.19 with HTTP; Mon, 12 Dec 2005 18:21:52 -0800 (PST) Message-ID: Date: Mon, 12 Dec 2005 22:21:52 -0400 From: fredthetree To: freebsd-stable@freebsd.org In-Reply-To: <439E0B23.3060304@asd.aplus.net> MIME-Version: 1.0 References: <439DE88B.1090407@asd.aplus.net> <439E0B23.3060304@asd.aplus.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 02:21:54 -0000 I just wanted to chime in and say I've had my 6.0-RELEASE #0 freeze up twic= e in the past few days. never once had it happen with 5.x. everything locks= , no keyboard response, no mouse, and after several minutes it reboots itself= , and savecore starts up during boot.. and again, it's not during heavy load= , both times i was running X, just browsing ye olde internet with firefox, some other apps running as per usual.. FreeBSD atlan.ns.ca 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC i386 Copyright (c) 1992-2005 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 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (701.59-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x683 Stepping =3D 3 Features=3D0x387f9ff real memory =3D 536805376 (511 MB) avail memory =3D 515956736 (492 MB) ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 5 on acpi0 pci_link2: irq 9 on acpi0 pci_link3: irq 10 on acpi0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0 pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 7.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0x9000-0x901f irq 10 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) pcm0: port 0x9400-0x941f irq 9 at device 10.0 on pci0 pcm0: ath0: mem 0xe8000000-0xe800ffff irq 5 at device 11.0 on pci0 ath0: Ethernet address: 00:0f:3d:50:13:5c ath0: mac 5.9 phy 4.3 radio 4.6 fdc0: port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 umass0: Cowon Systems, Inc. iAUDIO M3 Digital Audio Player, rev 2.00/1.00, addr 2 ugen0: EPSON EPSON Scanner, rev 2.00/1.10, addr 3 Timecounter "TSC" frequency 701594095 Hz quality 800 Timecounters tick every 1.000 msec ad0: 8063MB at ata0-master UDMA33 ad1: 57241MB at ata0-slave UDMA33 acd0: CDRW at ata1-master UDMA33 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 19073MB (39063024 512 byte sectors: 255H 63S/T 2431C) Trying to mount root from ufs:/dev/ad0s1a On 12/12/05, Atanas wrote: > > Ronald Klop said the following on 12/12/05 13:27: > > > > What happens if you set one of these sysctl values to 0? (This disables > > SMP changes from 5.4 to 6.0.) > > debug.mpsafevfs: 1 > > debug.mpsafenet : 1 > > debug.mpsafevm: 1 > > > Thanks for the suggestion! > I just did so and rebooted both machines, so we'll see. > > I remember unseting debug.mpsafenet before 5.4 due to some ipfw > limitations, but didn't know about the other two. > > > And is there a possibility (performance-wise) to build a kernel with > > WITNESS and/or INVARIANTS options compiled in. This will give more info > > about possible locking problems. Your system will run slower. And > > because of this the problem may not occur anymore, but it is worth the > > try. > > > Both machines are not much loaded, so I could afford slowing them down a > bit for a while (I hope it won't be several times slower). I will do > that at some point later if the problem still persists. > > I hope I won't be forced to downgrade to 5.4, though I'm already working > on that (just in case). > > Regards, > Atanas > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 02:49:50 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D94D516A41F for ; Tue, 13 Dec 2005 02:49:49 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93EF643D5E for ; Tue, 13 Dec 2005 02:49:49 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.41] (asd0.aplus.net [216.55.129.41]) (authenticated bits=0) by pro20.abac.com (8.13.4/8.13.4) with ESMTP id jBD2nk9i092416; Mon, 12 Dec 2005 18:49:47 -0800 (PST) (envelope-from atanas@asd.aplus.net) Message-ID: <439E3894.6060901@asd.aplus.net> Date: Mon, 12 Dec 2005 18:57:24 -0800 From: Atanas User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Jeremy References: <439DE88B.1090407@asd.aplus.net> <20051212214003.GA77268@cirb503493.alcatel.com.au> In-Reply-To: <20051212214003.GA77268@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 02:49:50 -0000 Peter Jeremy said the following on 12/12/05 13:40: > > Define "freezing": Does it respond to pings? Can you switch VTYs? > Do the num-lock/caps-lock LEDs respond? Do some processes seem to > freeze before others? > I used the word "freeze" instead of "crash", because the latter often gets associated with some errors reported by the kernel in system logs or on the console. In this case there are absolutely no error messages. I have also remote logging enabled (on another machine over the network), but there's nothing either. When the thing happens, the server appears to respond to pings for the first few minutes, but everything goes down until I go to the data canter. When I plug a keyboard, there's no response at all - no LEDs, no VTYs, Ctrl-Alt-Esc, etc. You might think of "hint.atkbd.0.flags" not being set properly, but it's right (i.e. unchanged, it appears to default to that on i386 5.x+) and other machines with identical configuration do accept keyboard. I have no information about processes. Only the thing I have is a real time CPU load graph. I have a script tailing the output of a "vmstat cpu 15" and drawing a graph with user/system/idle times, so according to that graph there are no load spikes or unusual variations before the crashes. The usual user/system/idle percentages look like 10/7/83. > I suggest you add the following to your kernel config: > options KDB # Enable kernel debugger support. > options DDB # Support DDB. > I just set these along with the DEBUG option below, and got the new kernel (from 6.0-RELEASE sources dated Dec 9) running on both machines, so we'll see. > When it hangs, break into DDB (Ctrl-Alt-Esc on the console or BREAK on > a serial console). > > As a start, run 'show lockedvnods' and 'ps'. My guess is that you'll > see a lock that has a number of waiters - which is probably the > culprit. Use 'panic' or 'call doadump' to get a crashdump and then > you can use kgdb to rummage around once you reboot - see > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebg-gdb.html > I don't have any experience in chasing kernel bugs, so I'm not sure whether I would be able to get something useful, but I'll try that on the next crash. But if I have no keyboard response I won't be able to save it, right? I do not know what a serial console is and would need some time to get along with it. Would I get something in addition to what I can get from the standard console? >>< makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols > > I suggest you add this back in. Without it, you can't debug any crash > dumps that you manage to get (and add "dumpdev" to your rc.conf). > My bad, I realized that it's kind of harmless, but it was weeks later after I put the box in production. It's back there now. The "dumpdev" variable seems to default to AUTO, i.e. trying to use the first swap device if it's bigger than the RAM (in my case yes), so I guess I don't need to touch it. > Whilst I realise that you can't have production machines freezing on > schedule, your assistance in providing more information about your > problem will help make 6.x more stable. > Yes, I know and I will try. Today I already had a couple of crashes (got lucky, no nasty data corruptions this time), and I cannot afford this to continue. I'm already working on the downgrade, but most likely I will have at least one of these 2 machines still running 6.x during the next day or two. After the downgrade we could eventually set a test bed and start hammering it with requests. The problem would be how to trigger the crash and whether we would be able to reproduce it at all. Thanks for the prompt reply! Regards, Atanas From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 02:50:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3470116A420 for ; Tue, 13 Dec 2005 02:50:32 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 293EB43D69 for ; Tue, 13 Dec 2005 02:50:30 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail15.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBD2oS4f026908 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Dec 2005 13:50:29 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBD2oSHh077622; Tue, 13 Dec 2005 13:50:28 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBD2oSZI077621; Tue, 13 Dec 2005 13:50:28 +1100 (EST) (envelope-from pjeremy) Date: Tue, 13 Dec 2005 13:50:28 +1100 From: Peter Jeremy To: fredthetree Message-ID: <20051213025028.GC77268@cirb503493.alcatel.com.au> References: <439DE88B.1090407@asd.aplus.net> <439E0B23.3060304@asd.aplus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 02:50:32 -0000 On Mon, 2005-Dec-12 22:21:52 -0400, fredthetree wrote: >I just wanted to chime in and say I've had my 6.0-RELEASE #0 freeze up twice >in the past few days. never once had it happen with 5.x. everything locks, >no keyboard response, no mouse, and after several minutes it reboots itself, >and savecore starts up during boot.. This suggests you've had a panic (or something that develops into one). If you've got a crashdump, you can probably get enough information out of it for people to get an idea of what is wrong. Please have a look at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebg-gdb.html -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 03:05:31 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 264BC16A41F for ; Tue, 13 Dec 2005 03:05:31 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCAD343D53 for ; Tue, 13 Dec 2005 03:05:30 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.41] (asd0.aplus.net [216.55.129.41]) (authenticated bits=0) by pro20.abac.com (8.13.4/8.13.4) with ESMTP id jBD35RCu007490; Mon, 12 Dec 2005 19:05:28 -0800 (PST) (envelope-from atanas@asd.aplus.net) Message-ID: <439E3C40.10901@asd.aplus.net> Date: Mon, 12 Dec 2005 19:13:04 -0800 From: Atanas User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Atanas References: <439DE88B.1090407@asd.aplus.net> <439E0B23.3060304@asd.aplus.net> In-Reply-To: <439E0B23.3060304@asd.aplus.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: freebsd-stable@freebsd.org, Ronald Klop Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 03:05:31 -0000 Atanas said the following on 12/12/05 15:43: > Ronald Klop said the following on 12/12/05 13:27: >> >> What happens if you set one of these sysctl values to 0? (This >> disables SMP changes from 5.4 to 6.0.) >> debug.mpsafevfs: 1 >> debug.mpsafenet: 1 >> debug.mpsafevm: 1 >> > Thanks for the suggestion! > I just did so and rebooted both machines, so we'll see. > (replying to myself) ... and coincidentally or not, I got the next crash in less than 10 minutes :-( After the crash it ran for longer, until I rebooted it after rebuilding the kernel with debug hookups. Before the reboot I commented these out (i.e. set them back to "1"), and now I'm waiting for a crashdump. Regards, Atanas From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 06:03:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CCAE16A41F for ; Tue, 13 Dec 2005 06:03:32 +0000 (GMT) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (gw-ipinc.museum.rain.com [65.75.192.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4D8A43D5E for ; Tue, 13 Dec 2005 06:03:30 +0000 (GMT) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (localhost [127.0.0.1]) by ns.museum.rain.com (8.13.4/8.13.4) with ESMTP id jBD6365L019606 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Mon, 12 Dec 2005 22:03:06 -0800 (PST) (envelope-from james@umpquanet.com) Received: (from james@localhost) by ns.museum.rain.com (8.13.4/8.13.4/Submit) id jBD635c4019605; Mon, 12 Dec 2005 22:03:05 -0800 (PST) (envelope-from james) Date: Mon, 12 Dec 2005 22:03:04 -0800 From: James Long To: freebsd-stable@freebsd.org Message-ID: <20051213060304.GA19568@ns.museum.rain.com> References: <20051212120057.673BB16A427@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051212120057.673BB16A427@hub.freebsd.org> User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-100.8 required=5.0 tests=ALL_TRUSTED, J_CHICKENPOX_71,USER_IN_WHITELIST autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ns.museum.rain.com Cc: Subject: Re: puzzling "ipfw show" output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 06:03:32 -0000 > Date: Mon, 12 Dec 2005 09:39:44 +0100 (CET) > From: Trond Endrest?l > Subject: Re: puzzling "ipfw show" output > To: FreeBSD stable > Message-ID: <20051212092932.T40542@ramstind.gtf.ol.no> > Content-Type: TEXT/PLAIN; charset=ISO-8859-1 > > On Mon, 12 Dec 2005 19:09+1100, Graham Menhennitt wrote: > > One last question: > > Why do you need rule 65530 when the built-in rule 65535 does the same > job? Having rule 65530 there allows the ruleset to function consistently on systems configured to accept by default or deny by default. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 06:30:41 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C36C416A41F for ; Tue, 13 Dec 2005 06:30:41 +0000 (GMT) (envelope-from trond@ramstind.gtf.ol.no) Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0503643D64 for ; Tue, 13 Dec 2005 06:30:40 +0000 (GMT) (envelope-from trond@ramstind.gtf.ol.no) Received: from ramstind.gtf.ol.no (Ximalas@localhost [127.0.0.1]) by ramstind.gtf.ol.no (8.12.9/8.12.9) with ESMTP id jBD6UdjA076479 for ; Tue, 13 Dec 2005 07:30:39 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.12.9/8.12.3/Submit) with ESMTP id jBD6Uduq076476 for ; Tue, 13 Dec 2005 07:30:39 +0100 (CET) Date: Tue, 13 Dec 2005 07:30:38 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= To: FreeBSD stable In-Reply-To: <20051213060304.GA19568@ns.museum.rain.com> Message-ID: <20051213072929.A76032@ramstind.gtf.ol.no> References: <20051212120057.673BB16A427@hub.freebsd.org> <20051213060304.GA19568@ns.museum.rain.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Subject: Re: puzzling "ipfw show" output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 06:30:41 -0000 On Mon, 12 Dec 2005 22:03-0800, James Long wrote: > > Date: Mon, 12 Dec 2005 09:39:44 +0100 (CET) > > From: Trond Endrest?l > > Subject: Re: puzzling "ipfw show" output > > To: FreeBSD stable > > Message-ID: <20051212092932.T40542@ramstind.gtf.ol.no> > > Content-Type: TEXT/PLAIN; charset=ISO-8859-1 > > > > Why do you need rule 65530 when the built-in rule 65535 does the same > > job? > > Having rule 65530 there allows the ruleset to function consistently > on systems configured to accept by default or deny by default. Good point. -- ---------------------------------------------------------------------- Trond Endrestřl | trond@fagskolen.gjovik.no Patron of The Art of Computer Programming| FreeBSD 4.8-S & Pine 4.55 From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 06:43:53 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 821EB16A41F for ; Tue, 13 Dec 2005 06:43:53 +0000 (GMT) (envelope-from dikshie@ppk.itb.ac.id) Received: from mx-itb.geoph.ITB.ac.id (mx7.ITB.ac.id [167.205.30.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id BACAE43D8C for ; Tue, 13 Dec 2005 06:43:36 +0000 (GMT) (envelope-from dikshie@ppk.itb.ac.id) Received: from antivirus.itb.ac.id (antivirus.ITB.ac.id [167.205.108.137]) by mx-itb.geoph.ITB.ac.id (Postfix) with SMTP id 3AD0120B28 for ; Tue, 13 Dec 2005 13:44:56 +0700 (WIT) Received: from ipv6.ppk.itb.ac.id (ipv6.ppk.itb.ac.id [167.205.30.228]) by mx-itb.geoph.ITB.ac.id (Postfix) with ESMTP id ED39120AD3 for ; Tue, 13 Dec 2005 13:44:53 +0700 (WIT) Received: by ipv6.ppk.itb.ac.id (Postfix, from userid 1001) id 189821151A; Tue, 13 Dec 2005 13:43:17 +0700 (WIT) Date: Tue, 13 Dec 2005 13:43:17 +0700 From: Dikshie To: freebsd-stable@freebsd.org Message-ID: <20051213064316.GA3620@ppk.itb.ac.id> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: (FreeBSD 6.0-STABLE i386) X-Uptime: 1:41PM up 1:53, 3 users, load averages: 0.04, 0.01, 0.00 X-Organization: Pusat Penelitian Kelautan (PPK) X-Location: Labtek VI Building, Institute of Technology, Bandung, Indonesia X-Web-Site: http://ipv6.ppk.itb.ac.id/~dikshie X-Yahoo-ID: dikshie X-GnuPG-Key: http://ipv6.ppk.itb.ac.id/gpg/ X-FingerPrint: 19AC 2592 1394 6C96 BABB 9060 50B8 D244 88E3 B55D X-BitDefender-SpamStamp: 1.1.4 049000040111AAAAAE X-BitDefender-Scanner: Clean, Agent: BitDefender POSTFIX 1.6.2 on mx7.itb.ac.id X-BitDefender-Spam: No (15) Subject: 6.0-STABLE panic once a day X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 06:43:53 -0000 Dear All, one of my 6.0-STABLE box always panic once a day. here's the dump: lapi# kgdb kernel.debug vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: panic: trying to sleep while sleeping is prohibited KDB: stack backtrace: kdb_backtrace(100,c32f4480,c06f74e8,c32f4480,c06f2550) at 0xc0510601 = kdb_backtrace+0x29 panic(c06976a5,c32f4480,0,c06f2550,d5629a7c) at 0xc04f90e4 = panic+0xa8 sleepq_add(c06f2550,c06f3414,c06906e8,1,c06f3414,0,c0690a7a,7d) at 0xc0515b40 = sleepq_add+0x8c cv_wait(c06f2550,c06f3414,0,16,d5629cb4) at 0xc04d3aa6 = cv_wait+0x132 _sx_xlock(c06f2520,c06907df,180) at 0xc04fe100 = _sx_xlock+0x5c acctwatch(0) at 0xc04d1c40 = acctwatch+0x20 softclock(0) at 0xc05040b1 = softclock+0x211 ithread_loop(c32ab500,d5629d38,c32ab500,c04e5d20,0) at 0xc04e5e64 = ithread_loop+0x144 fork_exit(c04e5d20,c32ab500,d5629d38) at 0xc04e52d4 = fork_exit+0xa0 fork_trampoline() at 0xc0650aac = fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd5629d6c, ebp = 0 --- Uptime: 14h34m3s Dumping 510 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130608 pages) 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:165 #1 0xc04f8e9c in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc04f9147 in panic (fmt=0xc06976a5 "trying to sleep while sleeping is prohibited") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc0515b40 in sleepq_add (wchan=0xc06f2550, lock=0xc06f3414, wmesg=0x0, flags=1) at /usr/src/sys/kern/subr_sleepqueue.c:273 #4 0xc04d3aa6 in cv_wait (cvp=0xc06f2550, mp=0xc06f3414) at /usr/src/sys/kern/kern_condvar.c:127 #5 0xc04fe100 in _sx_xlock (sx=0xc06f2520, file=0xc06907df "/usr/src/sys/kern/kern_acct.c", line=384) at /usr/src/sys/kern/kern_sx.c:175 #6 0xc04d1c40 in acctwatch (a=0x0) at /usr/src/sys/kern/kern_acct.c:384 #7 0xc05040b1 in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:290 #8 0xc04e5e64 in ithread_loop (arg=0xc32ab500) at /usr/src/sys/kern/kern_intr.c:547 #9 0xc04e52d4 in fork_exit (callout=0xc04e5d20 , arg=0xc32ab500, frame=0xd5629d38) at /usr/src/sys/kern/kern_fork.c:789 #10 0xc0650aac in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208 (kgdb) best regards, -dikshie- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 07:19:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F49E16A41F for ; Tue, 13 Dec 2005 07:19:27 +0000 (GMT) (envelope-from gmenhennitt@optusnet.com.au) Received: from mail26.syd.optusnet.com.au (mail26.syd.optusnet.com.au [211.29.133.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1000043D45 for ; Tue, 13 Dec 2005 07:19:26 +0000 (GMT) (envelope-from gmenhennitt@optusnet.com.au) Received: from [203.2.73.8] (c220-237-136-178.mckinn1.vic.optusnet.com.au [220.237.136.178]) by mail26.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBD7JO7O002093 for ; Tue, 13 Dec 2005 18:19:25 +1100 Message-ID: <439E75FB.5030202@optusnet.com.au> Date: Tue, 13 Dec 2005 18:19:23 +1100 From: Graham Menhennitt User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: FreeBSD stable References: <439D3053.3020504@optusnet.com.au> <20051212092932.T40542@ramstind.gtf.ol.no> In-Reply-To: <20051212092932.T40542@ramstind.gtf.ol.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: puzzling "ipfw show" output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 07:19:27 -0000 Trond Endrestřl wrote: > On Mon, 12 Dec 2005 19:09+1100, Graham Menhennitt wrote: > > >> The only explanation I have is that the packets arrived between the >> time when the machine started accepting incoming packets and when >> the rules were loaded in /etc/rc.d/ipfw. >> > > You just explained this yourself. > > One solution to this small problem could be to change part of the boot > sequence into this: > > a. Create VLAN interfaces etc if configured, assign IP addresses to > each configured interface, but do not UP them. > > b. Load the firewall rules, and optionally turn on forwarding. > > c. Set all configured interfaces to UP. > > One last question: > > Why do you need rule 65530 when the built-in rule 65535 does the same > job? > > Thanks Trond. You've confirmed what I suspected. I just wanted to be sure that there wasn't something dodgy happening. As James has already said, the extra rule is so that it doesn't matter if the "default to accept" option is set or not. It would also handle the case where I made a mistake and accidentally turned that option on, or there was a bug in the kernel that made it the default. Just making sure. Thanks, Graham From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 08:06:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83FA616A41F for ; Tue, 13 Dec 2005 08:06:32 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0915443D5A for ; Tue, 13 Dec 2005 08:06:31 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [64.203.49.168] (user-10cmcd8.cable.mindspring.com [64.203.49.168]) (authenticated bits=0) by pro20.abac.com (8.13.4/8.13.4) with ESMTP id jBD86NbO053340; Tue, 13 Dec 2005 00:06:26 -0800 (PST) (envelope-from atanas@asd.aplus.net) Message-ID: <439E8103.7020106@asd.aplus.net> Date: Tue, 13 Dec 2005 00:06:27 -0800 From: Atanas User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: Atanas References: <439DE88B.1090407@asd.aplus.net> <20051212214003.GA77268@cirb503493.alcatel.com.au> <439E3894.6060901@asd.aplus.net> In-Reply-To: <439E3894.6060901@asd.aplus.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: Peter Jeremy , freebsd-stable@freebsd.org Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 08:06:32 -0000 Atanas said the following on 12/12/05 18:57: > Peter Jeremy said the following on 12/12/05 13:40: >> >> When it hangs, break into DDB (Ctrl-Alt-Esc on the console or BREAK on >> a serial console). >> > But if I have no keyboard response I won't be able to save it, right? > (replying to myself) This is exactly what I was afraid would happen. The SATA based box just hung up again, with all of the kernel debugging options in place: makeoptions DEBUG=-g options KDB options DDB But I wasn't able to do anything with the keyboard in order to save a crashdump, so I got no other choices than hitting the reset button. Regards, Atanas From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 10:00:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24AC416A41F for ; Tue, 13 Dec 2005 10:00:44 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail10.syd.optusnet.com.au (mail10.syd.optusnet.com.au [211.29.132.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3173B43D58 for ; Tue, 13 Dec 2005 10:00:42 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail10.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBDA0ZTH027607 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Dec 2005 21:00:36 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBDA0ZHh078037; Tue, 13 Dec 2005 21:00:35 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBDA0YcU078036; Tue, 13 Dec 2005 21:00:34 +1100 (EST) (envelope-from pjeremy) Date: Tue, 13 Dec 2005 21:00:34 +1100 From: Peter Jeremy To: Atanas Message-ID: <20051213100034.GE77268@cirb503493.alcatel.com.au> References: <439DE88B.1090407@asd.aplus.net> <20051212214003.GA77268@cirb503493.alcatel.com.au> <439E3894.6060901@asd.aplus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <439E3894.6060901@asd.aplus.net> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 10:00:44 -0000 On Mon, 2005-Dec-12 18:57:24 -0800, Atanas wrote: >When I plug a keyboard, there's no response at all - no LEDs, no VTYs, >Ctrl-Alt-Esc, etc. You might think of "hint.atkbd.0.flags" not being set >properly, but it's right (i.e. unchanged, it appears to default to that >on i386 5.x+) and other machines with identical configuration do accept >keyboard. Note that PS/2 keyboards aren't hot-pluggable and attempts to do so can have deleterious effects on your keyboard and/or motherboard. In any case, the probe/attach sequence relies on the kernel being in a reasonably sane state (and I'm not sure if it will detect the keyboard as a console device except at boot time). If the keyboard has been plugged in since the system booted, do you still get the same "no response"? If so, the kernel has wedged at a fairly low level and I'm not quite sure how to proceed other than by enabling the sanity checks that other people have mentioned (eg WITNESS, INVARIANTS) and hoping they catch something. >the next crash. But if I have no keyboard response I won't be able to >save it, right? True. But DDB has been designed to rely on a fairly minimal subset of kernel functionality and often works, even though the system appears frozen. >I do not know what a serial console is and would need some time to get >along with it. Would I get something in addition to what I can get from >the standard console? I only mentioned serial consoles on the off-chance that you had one. Whilst it may not help here, serial consoles have a number of advantages when managing remote equipment (ie equipment not sitting on your desk) - you can access the console remotely and log all console output on another computer (either cross-connect com1/com2 on pairs of hosts or get a multi-port serial card to manage a number of systems). If your BIOS can handle serial communications, you virtually never need to physically visit your servers. For details, check out: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html I personally use ports/comms/conserver-com to manage about 50 assorted Unix/FreeBSD servers and switches at work. >The "dumpdev" variable seems to default to AUTO, i.e. trying to use the >first swap device if it's bigger than the RAM (in my case yes), so I >guess I don't need to touch it. It seems that my suggestion has been obsoleted by changes to the startup scripts since I checked last. >After the downgrade we could eventually set a test bed and start >hammering it with requests. The problem would be how to trigger the >crash and whether we would be able to reproduce it at all. Depending on your application and the interfaces to it, it might be feasible to either tee live traffic into both systems and just junk the responses from your test bed, or "record" live traffic and replay it into your test bed. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 10:08:48 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8D3B16A41F for ; Tue, 13 Dec 2005 10:08:48 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: from mail.interbgc.com (mx03.interbgc.com [217.9.224.229]) by mx1.FreeBSD.org (Postfix) with SMTP id C99DC43D60 for ; Tue, 13 Dec 2005 10:08:47 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: (qmail 1300 invoked from network); 13 Dec 2005 10:06:37 -0000 Received: from nike_d@cytexbg.com by keeper.interbgc.com by uid 1002 with qmail-scanner-1.14 (uvscan: v4.2.40/v4374. spamassassin: 2.63. Clear:SA:0(-2.6/8.0):. Processed in 1.913493 secs); 13 Dec 2005 10:06:37 -0000 X-Spam-Status: No, hits=-2.6 required=8.0 Received: from 213-240-204-179.1697748.ddns.cablebg.net (HELO tormentor.totalterror.net) (213.240.204.179) by mx03.interbgc.com with SMTP; 13 Dec 2005 10:06:35 -0000 Received: (qmail 56140 invoked from network); 13 Dec 2005 10:06:34 -0000 Received: from qmail by qscan (mail filter); 13 Dec 2005 10:06:34 +0000 Received: from unknown (HELO ?10.0.0.3?) (10.0.0.3) by tormentor.totalterror.net with SMTP; 13 Dec 2005 10:06:34 -0000 Message-ID: <439E9FBD.8090406@cytexbg.com> Date: Tue, 13 Dec 2005 12:17:33 +0200 From: Niki Denev User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.93.0.0 OpenPGP: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: devfs.rules and serial devices question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 10:08:49 -0000 Hi all, I'm setting up a UPS on one machine, and the ups daemon (nut) works as user "upsd". To make it work properly i have added in devfs.rules the following : perm ttyd0 0660 own ttyd0 upsd:upsd But it still does not work because ttyd0.init and ttyd0.lock are still owned by root. I'll try adding them too to the devfs.rules file, but i'm wondering if this is the expected behaviour of devfs? I think that maybe it will be better if one specify ttyd0 in the file, that rule also to apply for ttyd0.init and ttyd0.lock files. What do you think? --niki From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 10:48:06 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CDD316A420 for ; Tue, 13 Dec 2005 10:48:06 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AAD943D68 for ; Tue, 13 Dec 2005 10:48:05 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp133-7.lns2.adl2.internode.on.net [59.167.133.7]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id jBDAlrEQ058219 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 13 Dec 2005 21:17:54 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Tue, 13 Dec 2005 21:17:41 +1030 User-Agent: KMail/1.8.3 References: <439E9FBD.8090406@cytexbg.com> In-Reply-To: <439E9FBD.8090406@cytexbg.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8661115.gi6kduSHta"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512132117.47915.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: Subject: Re: devfs.rules and serial devices question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 10:48:06 -0000 --nextPart8661115.gi6kduSHta Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 13 Dec 2005 20:47, Niki Denev wrote: > perm ttyd0 0660 > own ttyd0 upsd:upsd > > But it still does not work because ttyd0.init and ttyd0.lock > are still owned by root. So? > I'll try adding them too to the devfs.rules file, > but i'm wondering if this is the expected behaviour of devfs? Yes. > I think that maybe it will be better if one specify ttyd0 in the > file, that rule also to apply for ttyd0.init and ttyd0.lock files. > What do you think? I don't see why your program needs to open .init and .lock files. Both of=20 those are pretty much exclusively for administrator use. NUT should definitely work without being able to open them. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart8661115.gi6kduSHta Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDnqbT5ZPcIHs/zowRAvDOAJ9PPH5zLBnrXw2y93Y5HVIf1unaBgCfVPnJ XWCSLKukqcEA3q3y1fSa6hg= =OwiO -----END PGP SIGNATURE----- --nextPart8661115.gi6kduSHta-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 11:17:19 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5862616A41F; Tue, 13 Dec 2005 11:17:19 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from mailhost.u-strasbg.fr (mailhost.u-strasbg.fr [130.79.200.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id A337E43D55; Tue, 13 Dec 2005 11:17:18 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.13.4/jtpda-5.5pre1) with ESMTP id jBDBHHkO050443 ; Tue, 13 Dec 2005 12:17:17 +0100 (CET) Received: from [127.0.0.1] (crc.u-strasbg.fr [IPv6:2001:660:2402:1001::1]) by baal.u-strasbg.fr (8.13.4/jtpda-5.5pre1) with ESMTP id jBDBHGqT019601 ; Tue, 13 Dec 2005 12:17:17 +0100 Message-ID: <439EAD8A.4070105@crc.u-strasbg.fr> Date: Tue, 13 Dec 2005 12:16:26 +0100 From: Philippe Pegon User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051016) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-hubs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1209/Mon Dec 12 16:48:01 2005 on mr5.u-strasbg.fr X-Virus-Scanned: ClamAV 0.87.1/1209/Mon Dec 12 16:48:01 2005 on baal.u-strasbg.fr X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (mailhost.u-strasbg.fr [IPv6:2001:660:2402::155]); Tue, 13 Dec 2005 12:17:17 +0100 (CET) X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS autolearn=disabled version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mr5.u-strasbg.fr Cc: Subject: ftp8.fr.freebsd.org HP msa20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 11:17:19 -0000 Hi, we are hosting ftp8.fr.freebsd.org. The server is an HP DL360 G4 with an HP msa20 attached for mirrors with FreeBSD 6, the msa20 is connected to a smart array 642 card. Yesterday, due to bugs in the firmware of the msa20 (like false detection of disk failures), we upgraded it with version 2.4.56-6 and now FreeBSD cannot detect the msa20. Therefore ftp8.fr.freebsd.org is down. Somebody can help ? thanks in advance -- Philippe Pegon From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 14:40:21 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2594416A41F; Tue, 13 Dec 2005 14:40:21 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from mailhost.u-strasbg.fr (mailhost.u-strasbg.fr [130.79.200.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AE6143D49; Tue, 13 Dec 2005 14:40:20 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.13.4/jtpda-5.5pre1) with ESMTP id jBDEeIa6048236 ; Tue, 13 Dec 2005 15:40:18 +0100 (CET) Received: from [127.0.0.1] (crc.u-strasbg.fr [IPv6:2001:660:2402:1001::1]) by baal.u-strasbg.fr (8.13.4/jtpda-5.5pre1) with ESMTP id jBDEeHp1029828 ; Tue, 13 Dec 2005 15:40:17 +0100 Message-ID: <439EDD1F.2050802@crc.u-strasbg.fr> Date: Tue, 13 Dec 2005 15:39:27 +0100 From: Philippe Pegon User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051016) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Simon Barner References: <439EAD8A.4070105@crc.u-strasbg.fr> <20051213115503.GA9261@zi025.glh.mhn.de> In-Reply-To: <20051213115503.GA9261@zi025.glh.mhn.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1209/Mon Dec 12 16:48:01 2005 on mr7.u-strasbg.fr X-Virus-Scanned: ClamAV 0.87.1/1209/Mon Dec 12 16:48:01 2005 on baal.u-strasbg.fr X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (mailhost.u-strasbg.fr [IPv6:2001:660:2402::157]); Tue, 13 Dec 2005 15:40:18 +0100 (CET) X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS autolearn=disabled version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mr7.u-strasbg.fr Cc: freebsd-hubs@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: ftp8.fr.freebsd.org HP msa20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 14:40:21 -0000 Simon Barner wrote: > Philippe Pegon wrote: > >>Hi, >> >>we are hosting ftp8.fr.freebsd.org. The server is an HP DL360 G4 with an >>HP msa20 attached for mirrors with FreeBSD 6, the msa20 is connected to >>a smart array 642 card. Yesterday, due to bugs in the firmware of the >>msa20 (like false detection of disk failures), we upgraded it with >>version 2.4.56-6 and now FreeBSD cannot detect the msa20. Therefore >>ftp8.fr.freebsd.org is down. Somebody can help ? > > > You'll probably need to provide more information, e.g. > > - pciconf -l > - Expert from old dmesg where it was detected. > - Maybe the kernel config you are right anubis# pciconf -l hostb0@pci0:0:0: class=0x060000 card=0x32000e11 chip=0x35908086 rev=0x0a hdr=0x00 pcib1@pci0:2:0: class=0x060400 card=0x00000050 chip=0x35958086 rev=0x0a hdr=0x01 pcib2@pci0:4:0: class=0x060400 card=0x00000050 chip=0x35978086 rev=0x0a hdr=0x01 pcib5@pci0:6:0: class=0x060400 card=0x00000050 chip=0x35998086 rev=0x0a hdr=0x01 pcib6@pci0:28:0: class=0x060400 card=0x00000050 chip=0x25ae8086 rev=0x02 hdr=0x01 pcib7@pci0:30:0: class=0x060400 card=0x00000000 chip=0x244e8086 rev=0x0a hdr=0x01 isab0@pci0:31:0: class=0x060100 card=0x00000000 chip=0x25a18086 rev=0x02 hdr=0x00 atapci0@pci0:31:1: class=0x01018a card=0x32010e11 chip=0x25a28086 rev=0x02 hdr=0x00 pcib3@pci6:0:0: class=0x060400 card=0x00000044 chip=0x03298086 rev=0x09 hdr=0x01 pcib4@pci6:0:2: class=0x060400 card=0x00000044 chip=0x032a8086 rev=0x09 hdr=0x01 ciss0@pci10:1:0: class=0x010400 card=0x409b0e11 chip=0x00460e11 rev=0x01 hdr=0x00 ciss1@pci2:1:0: class=0x010400 card=0x40910e11 chip=0x00460e11 rev=0x01 hdr=0x00 bge0@pci2:2:0: class=0x020000 card=0x00d00e11 chip=0x164814e4 rev=0x10 hdr=0x00 bge1@pci2:2:1: class=0x020000 card=0x00d00e11 chip=0x164814e4 rev=0x10 hdr=0x00 none0@pci1:3:0: class=0x030000 card=0x001e0e11 chip=0x47521002 rev=0x27 hdr=0x00 none1@pci1:4:0: class=0x088000 card=0xb2060e11 chip=0xb2030e11 rev=0x01 hdr=0x00 none2@pci1:4:2: class=0x088000 card=0xb2060e11 chip=0xb2040e11 rev=0x01 hdr=0x00 I cannot find an old dmesg (too many error messages have filled /var/log/messages*). The current dmesg : Copyright (c) 1992-2005 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 6.0-RELEASE #0: Thu Nov 24 20:51:49 CET 2005 toor@maton.u-strasbg.fr:/usr/obj/usr/src/sys/ANUBIS Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3600.15-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x659d> AMD Features=0x20000000 Hyperthreading: 2 logical CPUs real memory = 3758043136 (3583 MB) avail memory = 3678756864 (3508 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic1: Changing APIC ID to 9 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard ioapic3 irqs 72-95 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 7 on acpi0 pci_link1: irq 0 on acpi0 pci_link2: irq 7 on acpi0 pci_link3: irq 3 on acpi0 pci_link4: irq 0 on acpi0 pci_link5: irq 5 on acpi0 pci_link6: irq 5 on acpi0 pci_link7: irq 3 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 cpu0: on acpi0 acpi_perf0: on cpu0 cpu1: on acpi0 pcib0: on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci13: on pcib1 pcib2: at device 4.0 on pci0 pci6: on pcib2 pcib3: at device 0.0 on pci6 pci7: on pcib3 pcib4: at device 0.2 on pci6 pci10: on pcib4 ciss0: port 0x5000-0x50ff mem 0xfdff0000-0xfdff1fff,0xfdf80000-0xfdfbffff irq 72 at device 1.0 on pci10 ciss0: [GIANT-LOCKED] pcib5: at device 6.0 on pci0 pci3: on pcib5 pcib6: at device 28.0 on pci0 pci2: on pcib6 ciss1: port 0x4000-0x40ff mem 0xfdef0000-0xfdef1fff,0xfde80000-0xfdebffff irq 24 at device 1.0 on pci2 ciss1: [GIANT-LOCKED] bge0: mem 0xfde70000-0xfde7ffff irq 25 at device 2.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:12:79:3d:13:27 bge1: mem 0xfde60000-0xfde6ffff irq 26 at device 2.1 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:12:79:3d:13:26 pcib7: at device 30.0 on pci0 pci1: on pcib7 pci1: at device 3.0 (no driver attached) pci1: at device 4.0 (no driver attached) pci1: at device 4.2 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x500-0x50f irq 18 at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff,0xee000-0xeffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master PIO4 SMP: AP CPU #1 Launched! da0 at ciss1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 135.168MB/s transfers da0: 34727MB (71122560 512 byte sectors: 255H 32S/T 8716C) Trying to mount root from ufs:/dev/da0s1a WARNING: /home was not properly dismounted WARNING: /local was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted WARNING: /home was not properly dismounted WARNING: /local was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted Kernel config (include a GENERIC without cpu I486_CPU and cpu I586_CPU) : # # ANUBIS # include GENERIC2 ident ANUBIS ################################################################################ # removed from GENERIC ################################################################################ #nocpu I486_CPU #nocpu I586_CPU # Bus support. nodevice eisa # SCSI Controllers nodevice amd # AMD 53C974 (Tekram DC-390(T)) nodevice isp # Qlogic family #device ispfw # Firmware for QLogic HBAs- normally a module nodevice mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic nodevice trm # Tekram DC395U/UW/F DC315U adapters nodevice adv # Advansys SCSI adapters nodevice adw # Advansys wide SCSI adapters nodevice aha # Adaptec 154x SCSI adapters nodevice bt # Buslogic/Mylex MultiMaster SCSI adapters nodevice ncv # NCR 53C500 nodevice nsp # Workbit Ninja SCSI-3 nodevice stg # TMC 18C30/18C50 # RAID controllers interfaced to the SCSI subsystem nodevice arcmsr # Areca SATA II RAID nodevice asr # DPT SmartRAID V, VI and Adaptec SCSI RAID nodevice dpt # DPT Smartcache III, IV - See NOTES for options nodevice hptmv # Highpoint RocketRAID 182x nodevice iir # Intel Integrated RAID nodevice ips # IBM (Adaptec) ServeRAID nodevice mly # Mylex AcceleRAID/eXtremeRAID nodevice twa # 3ware 9000 series PATA/SATA RAID # RAID controllers nodevice mlx # Mylex DAC960 family nodevice pst # Promise Supertrak SX6000 nodevice twe # 3ware ATA RAID # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support nodevice cbb # cardbus (yenta) bridge nodevice pccard # PC Card (16-bit) bus nodevice cardbus # CardBus (32-bit) bus # Parallel port nodevice ppc nodevice ppbus # Parallel port bus (required) nodevice lpt # Printer nodevice plip # TCP/IP over parallel nodevice ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. nodevice de # DEC/Intel DC21x4x (``Tulip'') nodevice txp # 3Com 3cR990 (``Typhoon'') nodevice vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! nodevice dc # DEC/Intel 21143 and various workalikes nodevice nve # nVidia nForce MCP on-board Ethernet Networking nodevice pcn # AMD Am79C97x PCI 10/100(precedence over 'lnc') nodevice re # RealTek 8139C+/8169/8169S/8110S nodevice rl # RealTek 8129/8139 nodevice sf # Adaptec AIC-6915 (``Starfire'') nodevice sis # Silicon Integrated Systems SiS 900/SiS 7016 nodevice sk # SysKonnect SK-984x & SK-982x gigabit Ethernet nodevice ste # Sundance ST201 (D-Link DFE-550TX) nodevice ti # Alteon Networks Tigon I/II gigabit Ethernet nodevice tl # Texas Instruments ThunderLAN nodevice tx # SMC EtherPower II (83c170 ``EPIC'') nodevice vge # VIA VT612x gigabit Ethernet nodevice vr # VIA Rhine, Rhine II nodevice wb # Winbond W89C840F nodevice xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard NICs included. nodevice cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' nodevice ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards nodevice ex # Intel EtherExpress Pro/10 and Pro/10+ nodevice ep # Etherlink III based cards nodevice fe # Fujitsu MB8696x based cards nodevice ie # EtherExpress 8/16, 3C507, StarLAN 10 etc. nodevice lnc # NE2100, NE32-VL Lance Ethernet cards nodevice sn # SMC's 9000 series of Ethernet chips nodevice xe # Xircom pccard Ethernet # Wireless NIC cards nodevice wlan # 802.11 support nodevice an # Aironet 4500/4800 802.11 wireless NICs. nodevice awi # BayStack 660 and others nodevice ral # Ralink Technology RT2500 wireless NICs. nodevice wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # USB support nodevice uhci # UHCI PCI->USB interface nodevice ohci # OHCI PCI->USB interface nodevice ehci # EHCI PCI->USB interface (USB 2.0) nodevice usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices nodevice ugen # Generic nodevice uhid # "Human Interface Devices" nodevice ukbd # Keyboard nodevice ulpt # Printer nodevice umass # Disks/Mass storage - Requires scbus and da nodevice ums # Mouse nodevice ural # Ralink Technology RT2500USB wireless NICs nodevice urio # Diamond Rio 500 MP3 player nodevice uscanner # Scanners # USB Ethernet, requires miibus nodevice aue # ADMtek USB Ethernet nodevice axe # ASIX Electronics USB Ethernet nodevice cdce # Generic USB over Ethernet nodevice cue # CATC USB Ethernet nodevice kue # Kawasaki LSI USB Ethernet nodevice rue # RealTek RTL8150 USB Ethernet # FireWire support nodevice firewire # FireWire bus code nodevice sbp # SCSI over FireWire (Requires scbus and da) nodevice fwe # Ethernet over FireWire (non-standard!) ################################################################################ # added from GENERIC ################################################################################ # altq(9). Enable the base part of the hooks with the ALTQ option. # Individual disciplines must be built into the base system and can not be # loaded as modules at this point. In order to build a SMP kernel you must # also have the ALTQ_NOPCC option. options ALTQ options ALTQ_CBQ # Class Bases Queueing options ALTQ_RED # Random Early Drop options ALTQ_RIO # RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler options ALTQ_CDNR # Traffic conditioner options ALTQ_PRIQ # Priority Queueing options ALTQ_NOPCC # Required for SMP build # The following options will let you change the default colors of syscons. options SC_KERNEL_CONS_ATTR=(FG_RED|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_BLACK|BG_RED) options VESA options SC_PIXEL_MODE options SMP device vlan device pf device pflog device pfsync device carp From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 14:58:25 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36C9A16A41F for ; Tue, 13 Dec 2005 14:58:25 +0000 (GMT) (envelope-from hk@alogis.com) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65A3B43D77 for ; Tue, 13 Dec 2005 14:58:23 +0000 (GMT) (envelope-from hk@alogis.com) Received: from alogis.com (localhost [127.0.0.1]) by alogis.com (8.13.1/8.13.1) with ESMTP id jBDEwLZ6094790; Tue, 13 Dec 2005 15:58:21 +0100 (CET) (envelope-from hk@alogis.com) Received: (from hk@localhost) by alogis.com (8.13.1/8.13.1/Submit) id jBDEwL9u094789; Tue, 13 Dec 2005 15:58:21 +0100 (CET) (envelope-from hk) Date: Tue, 13 Dec 2005 15:58:21 +0100 From: Holger Kipp To: Ronald Klop , petefrench@ticketswitch.com Message-ID: <20051213145821.GA93062@intserv.int1.b.intern> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: Any vital post 6.0 fixes gone into stable ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 14:58:25 -0000 On Mon, Dec 12, 2005 at 09:21:29PM +0100, Ronald Klop wrote: > On Mon, 12 Dec 2005 16:03:59 +0100, Pete French > wrote: > > >I'm about to start installing a whole new set of machines for production > >use with 6.0 on them. Normally I would just use -RELEASE, but as this is > >a dot-nought release I was wondering if there is anything vital which > >has been commited to stable, and if I should therefore sun the machines > >under stable instead. I havent seen anything go past which I regard as > >critical, though somebody did make a mention of some arp problem > >being fixed, which I could find a reference to the original problem for. > > > >Anything I need to know ? Am running release on a couple of machines here > >and it works fine for me so far, but always good to get other opinions. > > Try downloading an iso and search for release notes in it (RELNOTES.txt or > something like that.) > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/Dec_2005/ I do not know if this is relevant for you, but if you want to use mgetty with 6-STABLE (including 6.0-RELEASE), you will have a few problems. See http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/87208 I don't know if or when this will be fixed, though. Regards, Holger From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 15:14:43 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67A4B16A41F for ; Tue, 13 Dec 2005 15:14:43 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 653AC43D7F for ; Tue, 13 Dec 2005 15:14:38 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (szcdsd@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBDFEUI5025275 for ; Tue, 13 Dec 2005 16:14:31 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBDFEUcu025274; Tue, 13 Dec 2005 16:14:30 +0100 (CET) (envelope-from olli) Date: Tue, 13 Dec 2005 16:14:30 +0100 (CET) Message-Id: <200512131514.jBDFEUcu025274@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <439D3053.3020504@optusnet.com.au> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: puzzling "ipfw show" output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 15:14:43 -0000 Graham Menhennitt wrote: > I got the following output from "ipfw show" in my daily security run output email. > > +++ /tmp/security.yri47lgA Mon Dec 12 03:01:45 2005 > +00522 3530 1204158 deny ip from 10.0.0.0/8 to any via sis1 > +02522 18 784 deny tcp from any to any in via sis1 setup > +65530 0 0 deny ip from any to any > +65535 2 688 deny ip from any to any > > Could somebody please explain to me how those packets got past rule 65530 to be > stopped by (the identical) rule 65535? In addition to the explanations already given, the above output from "ipfw show" could also be caused by a rule saying "skip 65535" somewhere. ;-) Of course, I assume that you wrote the whole rule set yourself, so you would be aware of such a skip rule. I just wanted to mention the possibility that rules need not be evaluated in strict numerical order. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "C++ is the only current language making COBOL look good." -- Bertrand Meyer From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 16:10:23 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52A8916A41F for ; Tue, 13 Dec 2005 16:10:23 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF89943DB5 for ; Tue, 13 Dec 2005 16:10:07 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (gfelop@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBDGA069027337 for ; Tue, 13 Dec 2005 17:10:00 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBDGA0mK027336; Tue, 13 Dec 2005 17:10:00 +0100 (CET) (envelope-from olli) Date: Tue, 13 Dec 2005 17:10:00 +0100 (CET) Message-Id: <200512131610.jBDGA0mK027336@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <20051203214605.GB44199@outcold.yadt.co.uk> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: Data Loss with samba shared USB drive X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 16:10:23 -0000 David Taylor wrote: > I have a USB drive (SanDisk 1GB flash drive), which I have mounted > on a windows PC using samba 3.0. > > I recently discovered the copy of my files on my USB device were > corrupted (thankfully I had a backup), being filled entirely with > 0's (that's ASCII '0', not NUL). > > I should probably mention that this is with the drive formatted with > a FAT filesystem. That seems to be the problem documented in PR kern/39043: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/39043 It's a long-standing bug that still exists. It affects FAT32 filesystems exported via Samba. The workaround is to re-format the drive with UFS instead of FAT. I don't think anyone is actively working on fixing the bug. :-( Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "To this day, many C programmers believe that 'strong typing' just means pounding extra hard on the keyboard." -- Peter van der Linden From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 16:37:29 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E0C616A41F for ; Tue, 13 Dec 2005 16:37:29 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 6E55443D45 for ; Tue, 13 Dec 2005 16:37:28 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 13 Dec 2005 16:37:26 -0000 Received: from p54A7C94A.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.201.74] by mail.gmx.net (mp029) with SMTP; 13 Dec 2005 17:37:26 +0100 X-Authenticated: #5465401 Message-ID: <439EF8B5.4030702@gmx.de> Date: Tue, 13 Dec 2005 17:37:09 +0100 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 16:37:29 -0000 On my FreeBSD 6-stable (the last build is less then 24hours ago) my devfs doesn't apply permissions set in /etc/devfs.conf when I attach new devices. I have to call: /etc/rc.d/devfs restart manually for the settings to be applied. This is rather uncomfortable in some cases (especially with my PDA). I don't know weather this is the normal behaviour, anyway if it is, shouldn't devfs be restarted automatically as soon as external devices (usb, firewire, ir) are attached? From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 16:50:04 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2254316A41F for ; Tue, 13 Dec 2005 16:50:04 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EEB543D67 for ; Tue, 13 Dec 2005 16:49:48 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jBDGnlmk020474; Tue, 13 Dec 2005 08:49:47 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jBDGnlXk020473; Tue, 13 Dec 2005 08:49:47 -0800 Date: Tue, 13 Dec 2005 08:49:47 -0800 From: Brooks Davis To: "[LoN]Kamikaze" Message-ID: <20051213164947.GA17705@odin.ac.hmc.edu> References: <439EF8B5.4030702@gmx.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: <439EF8B5.4030702@gmx.de> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 16:50:04 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote: > On my FreeBSD 6-stable (the last build is less then 24hours ago) my > devfs doesn't apply permissions set in /etc/devfs.conf when I attach new > devices. I have to call: > /etc/rc.d/devfs restart > manually for the settings to be applied. This is rather uncomfortable in > some cases (especially with my PDA). >=20 > I don't know weather this is the normal behaviour, anyway if it is, > shouldn't devfs be restarted automatically as soon as external devices > (usb, firewire, ir) are attached? This is normal. devfs.conf is for boot only, you need devfs.rules for runtime. Unfortunatly, the documentation of this fact and the docuementation of devfs.rules sucks. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDnvuqXY6L6fI4GtQRAteOAKCDqLMLl8WB6p1yrtdr2Rcz27psiQCfRIM8 HSIGfD+2z5pcDMuWUw+Adjo= =iA40 -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 16:53:10 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D8AF16A424 for ; Tue, 13 Dec 2005 16:53:10 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FB8A43DF4 for ; Tue, 13 Dec 2005 16:51:20 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ydilcl@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBDGp2IE029497 for ; Tue, 13 Dec 2005 17:51:02 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBDGp2Lx029496; Tue, 13 Dec 2005 17:51:02 +0100 (CET) (envelope-from olli) Date: Tue, 13 Dec 2005 17:51:02 +0100 (CET) Message-Id: <200512131651.jBDGp2Lx029496@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <20051208001857.68ac4fef.torfinn.ingolfsen@broadpark.no> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: FreeBSD 6.0 as storage server with raid5? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 16:53:10 -0000 Sorry for the late reply ... Torfinn Ingolfsen wrote: > Highpoint RocketRAID 1640 (4 ports) > Promise FastTrak S150 SX4 (4 ports) > Promise FastTrak S150 SX4-M (4 ports) > Highpoint RocketRAID 1810A (4 ports) > Highpoint RocketRAID 1820A (8 ports) > Intel RAID Controller SRCS16 (6 ports) > [...] > 1) can I install several 4-port RAID controllers in one machine? Yes. There's no reason why you shouldn't be able to do that. > I can get two RocketRAID 1640's for the price of one RocketRAID 1820A. Note that the HPT 18x0A have an onboard processor which does the XOR (parity) calculations for RAID-5. For the non-A versions, the host CPU has to do those calculations (in the driver), which can be quite a noticable burden. > 3) disks - I understand the importance of using disks from different > production runs. Some people have suggested to use disks of different > brands as well, but there were no conclusions. Should I stick to the > same brand and model, or can I use disks of different brands as long > as they are of the same size? Well, both strategies have advantages and disadvantages. But given the fact that the "big" commercial appliance companies (such as NetApp) ship their filers with disks of the same brand, I guess it's not terrible mistake to do so. > 4) PSU considerations. How big a PSU do I need if I want to run two > controllers and eight disks in one machine? are there any rules of thumb > for sizing this? There are usually three numbers of power-usage provided for hard disks: power usage when idle, max power usage when busy during normal operation, and max poer usage during spin-up. The latter is the largest number, of course. If your disks all spin up at the same time, then you PSU have to be able to provide enough power for the sum of all of your disks (plus the rest of the system), which can be quite a lot. Some controllers have a setting to enable staged starting of the drives, i.e. one after the other. This can reduce the maximum PSU requirement considerably if you have a lot of disks. Best regards Oliver PS: I assume you already know this, but I'd like to note this for all readers: RAID (of any kind) does not replace reliable backups. Always make proper backups, independent of your RAID (if any). -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. (On the statement print "42 monkeys" + "1 snake":) By the way, both perl and Python get this wrong. Perl gives 43 and Python gives "42 monkeys1 snake", when the answer is clearly "41 monkeys and 1 fat snake". -- Jim Fulton From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 16:54:51 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B07DA16A41F for ; Tue, 13 Dec 2005 16:54:51 +0000 (GMT) (envelope-from feanor@pc5-179.lri.fr) Received: from lri.lri.fr (lri.lri.fr [129.175.15.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4587643D79 for ; Tue, 13 Dec 2005 16:54:26 +0000 (GMT) (envelope-from feanor@pc5-179.lri.fr) Received: from localhost (localhost.localdomain [127.0.0.1]) by lri.lri.fr (Postfix) with ESMTP id 574BC249C8C; Tue, 13 Dec 2005 17:54:17 +0100 (CET) Received: from lri.lri.fr ([127.0.0.1]) by localhost (lri.lri.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21150-06; Tue, 13 Dec 2005 17:54:17 +0100 (CET) Received: from pc5-179.lri.fr (pc5-179 [129.175.5.179]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lri.lri.fr (Postfix) with ESMTP id 38004249C8B; Tue, 13 Dec 2005 17:54:17 +0100 (CET) Received: from pc5-179.lri.fr (localhost.lri.fr [127.0.0.1]) by pc5-179.lri.fr (8.13.3/8.13.1) with ESMTP id jBDGsH4t014843; Tue, 13 Dec 2005 17:54:17 +0100 (CET) (envelope-from feanor@pc5-179.lri.fr) Received: (from feanor@localhost) by pc5-179.lri.fr (8.13.3/8.13.1/Submit) id jBDGsGOT014842; Tue, 13 Dec 2005 17:54:16 +0100 (CET) (envelope-from feanor) Date: Tue, 13 Dec 2005 17:54:16 +0100 From: Marwan Burelle To: "[LoN]Kamikaze" Message-ID: <20051213165416.GE71643@pc5-179.lri.fr> References: <439EF8B5.4030702@gmx.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="f+W+jCU1fRNres8c" Content-Disposition: inline In-Reply-To: <439EF8B5.4030702@gmx.de> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at lri.fr Cc: freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 16:54:51 -0000 --f+W+jCU1fRNres8c Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote: > On my FreeBSD 6-stable (the last build is less then 24hours ago) my > devfs doesn't apply permissions set in /etc/devfs.conf when I attach new > devices. I have to call: > /etc/rc.d/devfs restart > manually for the settings to be applied. This is rather uncomfortable in > some cases (especially with my PDA). >=20 > I don't know weather this is the normal behaviour, anyway if it is, > shouldn't devfs be restarted automatically as soon as external devices > (usb, firewire, ir) are attached? It is the normal behaviour, /etc/rc.d/devfs is a little script that parse /etc/devfs.conf and according to it and what it find in /dev it set permissions or create links, it's purely static. One possibility is to call /etc/rc.d/devfs when a device is attached in /etc/devd.conf (take a look at devd(8) and devd.conf(5)) For exemple, I have something like this in my /etc/devd.conf : attach 100 { device-name "umass[0-9]+" ; action "/bin/sleep 3; /etc/rc.d/devfs restart" ; }; "attach" : what kind of event "100" : as usual, for ordering rules "device-name ..." : the device concerned "action ... " : what to do, here I use sleep, because action is called when the attach event arrives, not when the device node is created. There maybe a better way, but "it works"=A9 ;) --=20 Burelle Marwan, Equipe Bases de Donnees - LRI http://www.cduce.org (burelle@lri.fr | Marwan.Burelle@ens.fr) --f+W+jCU1fRNres8c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDnvy4I+2UvUKfgvgRAoD8AJwMSKjANhbVe4gz3ETOLwJwsRA7VwCgo9oi w/Tfce97+u/lBcMF5I+9PYA= =Xy4e -----END PGP SIGNATURE----- --f+W+jCU1fRNres8c-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 17:20:06 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E696416A41F for ; Tue, 13 Dec 2005 17:20:06 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 1729A43D64 for ; Tue, 13 Dec 2005 17:20:05 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 13 Dec 2005 17:20:04 -0000 Received: from p54A7C94A.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.201.74] by mail.gmx.net (mp034) with SMTP; 13 Dec 2005 18:20:04 +0100 X-Authenticated: #5465401 Message-ID: <439F02B3.60707@gmx.de> Date: Tue, 13 Dec 2005 18:19:47 +0100 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <439EF8B5.4030702@gmx.de> <20051213165416.GE71643@pc5-179.lri.fr> In-Reply-To: <20051213165416.GE71643@pc5-179.lri.fr> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 17:20:07 -0000 It's a simple and working solution and I think it simply should be made default for ALL attach events. To me it makes more sense than having 2 different systems for the same thing. Anyway, now I'm going to set up a devfs.rules (and learn a new different syntax for doing exactly the same thing). This looks like something that could have been in the unix haters handbook. Brooks Davis wrote: > This is normal. devfs.conf is for boot only, you need devfs.rules for > runtime. Unfortunatly, the documentation of this fact and the > docuementation of devfs.rules sucks. > > -- Brooks Marwan Burelle wrote: > One possibility is to call /etc/rc.d/devfs when a device is attached > in /etc/devd.conf (take a look at devd(8) and devd.conf(5)) > > For exemple, I have something like this in my /etc/devd.conf : > > attach 100 { > device-name "umass[0-9]+" ; > action "/bin/sleep 3; /etc/rc.d/devfs restart" ; > }; > > "attach" : what kind of event > "100" : as usual, for ordering rules > "device-name ..." : the device concerned > "action ... " : what to do, here I use sleep, because action is called > when the attach event arrives, not when the device node is created. > > There maybe a better way, but "it works"Š ;) From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 17:21:17 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E17A16A41F for ; Tue, 13 Dec 2005 17:21:17 +0000 (GMT) (envelope-from marko.raiha@zendata.fi) Received: from mail.dataclub.fi (mail.dataclub.fi [194.240.247.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D80943D68 for ; Tue, 13 Dec 2005 17:21:15 +0000 (GMT) (envelope-from marko.raiha@zendata.fi) Received: from localhost (mail.private.dataclub.fi [192.168.123.3]) by mail.dataclub.fi (Postfix) with ESMTP id 9AFE343C1 for ; Tue, 13 Dec 2005 19:21:10 +0200 (EET) Received: from mail.dataclub.fi ([192.168.123.3]) by localhost (mail.dataclub.fi [192.168.123.3]) (amavisd-new, port 10024) with ESMTP id 90821-10 for ; Tue, 13 Dec 2005 19:21:09 +0200 (EET) Received: by mail.dataclub.fi (Postfix, from userid 701) id DA22643A6; Tue, 13 Dec 2005 19:21:09 +0200 (EET) Received: from [192.168.67.95] (unknown [83.145.214.193]) by mail.dataclub.fi (Postfix) with ESMTP id 94E1A42B7 for ; Tue, 13 Dec 2005 19:21:09 +0200 (EET) Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: quoted-printable Message-Id: Content-Type: text/plain; charset=ISO-8859-1; format=flowed To: freebsd-stable@freebsd.org From: =?ISO-8859-1?Q?R=E4ih=E4_Marko?= Date: Tue, 13 Dec 2005 19:21:10 +0200 X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: amavisd-new at dataclub.fi Subject: Crashing recent 6-STABLE, HP DL145G2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 17:21:17 -0000 Hi, I have installed i386 6.0-RELEASE to two HP DL145G2-servers and they crash soon after (1-2 minutes) booting up to login prompt. Sometimes they boot up without crashing and sometimes with crashing. I have now upgraded to RELENG_6 and crashing continues. What amazes me is that these two machines do the same so I don't believe it would be broken hardware. I have copied dmesg, uname -a and kgdb backtrace information to the following file on the web-site. http://www.zendata.fi/FreeBSD/debug_information.txt.gz I have core file so I can dig more information if it is needed. Regards, --=20 Marko R=E4ih=E4 From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 17:22:31 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6882516A41F for ; Tue, 13 Dec 2005 17:22:31 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2522A43D5F for ; Tue, 13 Dec 2005 17:22:07 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.4) with ESMTP id jBDHOWdl076117 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 13 Dec 2005 12:24:37 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-stable@freebsd.org Date: Tue, 13 Dec 2005 12:23:26 -0500 User-Agent: KMail/1.8.3 References: <439EF8B5.4030702@gmx.de> <20051213165416.GE71643@pc5-179.lri.fr> In-Reply-To: <20051213165416.GE71643@pc5-179.lri.fr> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4681211.6sWLXLe4Yc"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512131223.56159.mistry.7@osu.edu> X-Spam-Status: No, score=-5.0 required=5.0 tests=ALL_TRUSTED,BAYES_40, MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.87/1209/Mon Dec 12 10:48:01 2005 on mail.united-ware.com X-Virus-Status: Clean Cc: "\[LoN\]Kamikaze" Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 17:22:31 -0000 --nextPart4681211.6sWLXLe4Yc Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 13 December 2005 11:54 am, Marwan Burelle wrote: > On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote: > > On my FreeBSD 6-stable (the last build is less then 24hours ago) > > my devfs doesn't apply permissions set in /etc/devfs.conf when I > > attach new devices. I have to call: > > /etc/rc.d/devfs restart > > manually for the settings to be applied. This is rather > > uncomfortable in some cases (especially with my PDA). > > > > I don't know weather this is the normal behaviour, anyway if it > > is, shouldn't devfs be restarted automatically as soon as > > external devices (usb, firewire, ir) are attached? > > It is the normal behaviour, /etc/rc.d/devfs is a little script that > parse /etc/devfs.conf and according to it and what it find in /dev > it set permissions or create links, it's purely static. > > One possibility is to call /etc/rc.d/devfs when a device is > attached in /etc/devd.conf (take a look at devd(8) and > devd.conf(5)) > > For exemple, I have something like this in my /etc/devd.conf : > > attach 100 { > device-name "umass[0-9]+" ; > action "/bin/sleep 3; /etc/rc.d/devfs restart" ; > }; > > "attach" : what kind of event > "100" : as usual, for ordering rules > "device-name ..." : the device concerned > "action ... " : what to do, here I use sleep, because action is > called when the attach event arrives, not when the device node is > created. > > There maybe a better way, but "it works"=A9 ;) You should be using /etc/devfs.rules Search the mailing list for examples and setup. =2D-=20 Anish Mistry --nextPart4681211.6sWLXLe4Yc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDnwOsxqA5ziudZT0RAkpqAKCWzcCC0dLMc/SZZFgNyQJtu48zmQCdEdFS Ur8l9BBrJ0xq4Ps6O6Lghrs= =T2ks -----END PGP SIGNATURE----- --nextPart4681211.6sWLXLe4Yc-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 17:37:19 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E0F516A41F for ; Tue, 13 Dec 2005 17:37:19 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal4.es.net (postal4.es.net [198.124.252.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EC2043D5D for ; Tue, 13 Dec 2005 17:37:19 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id IBA74465; Tue, 13 Dec 2005 09:37:17 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id C15515D07; Tue, 13 Dec 2005 09:37:14 -0800 (PST) To: Brooks Davis In-reply-to: Your message of "Tue, 13 Dec 2005 08:49:47 PST." <20051213164947.GA17705@odin.ac.hmc.edu> Date: Tue, 13 Dec 2005 09:37:13 -0800 From: "Kevin Oberman" Message-Id: <20051213173714.C15515D07@ptavv.es.net> Cc: "\[LoN\]Kamikaze" , freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 17:37:19 -0000 > Date: Tue, 13 Dec 2005 08:49:47 -0800 > From: Brooks Davis > Sender: owner-freebsd-stable@freebsd.org > > On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote: > > On my FreeBSD 6-stable (the last build is less then 24hours ago) my > > devfs doesn't apply permissions set in /etc/devfs.conf when I attach new > > devices. I have to call: > > /etc/rc.d/devfs restart > > manually for the settings to be applied. This is rather uncomfortable in > > some cases (especially with my PDA). > > > > I don't know weather this is the normal behaviour, anyway if it is, > > shouldn't devfs be restarted automatically as soon as external devices > > (usb, firewire, ir) are attached? > > This is normal. devfs.conf is for boot only, you need devfs.rules for > runtime. Unfortunatly, the documentation of this fact and the > docuementation of devfs.rules sucks. Brooks, You are being entirely too kind. The documentation for the practical use of devfs at all sucks! Nothing I could find in the handbook, either. It's a classic case of documentation written by programmers in that the author can't look at his software from the standpoint of someone who does not know anything about it. Good documentation really needs to be written by someone sitting "on the outside" of the development process. But this is a huge problem for commercial applications where they actually hire writers, let alone for a volunteer project. I thought that the devfs.rules page was pretty helpful, but neither the devfs(8) nor the devfs(5) man pages mention either devfs.conf or devfs.rules in "SEE ALSO" (although devfs.rules is mentioned in "FILES"). No indication of how to use it or that there is actually a man page for it. No mention of devfs.conf at all. devfs(5) provides no clue at all that devfs does this sort of thing, either. While much of the contents of devfs.rules made little sense to me, it was enough for me to do what I was trying to do and it works fine. I also had to read /etc/rc.d/devfs in order to get it right as the comments in /etc/defaults/rc.conf are wrong and/or incomplete. But the real problem is finding the man page at all. Guess I'll try putting something together. Other than putting it in a PR, should I do anything else with it? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 17:38:33 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B17B516A41F for ; Tue, 13 Dec 2005 17:38:33 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80F4443D80 for ; Tue, 13 Dec 2005 17:38:28 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jBDHcMUa025621; Tue, 13 Dec 2005 09:38:22 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jBDHcL7F025620; Tue, 13 Dec 2005 09:38:21 -0800 Date: Tue, 13 Dec 2005 09:38:21 -0800 From: Brooks Davis To: "[LoN]Kamikaze" Message-ID: <20051213173821.GA25217@odin.ac.hmc.edu> References: <439EF8B5.4030702@gmx.de> <20051213165416.GE71643@pc5-179.lri.fr> <439F02B3.60707@gmx.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline In-Reply-To: <439F02B3.60707@gmx.de> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 17:38:33 -0000 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 06:19:47PM +0100, [LoN]Kamikaze wrote: > It's a simple and working solution and I think it simply should be made > default for ALL attach events. To me it makes more sense than having 2 > different systems for the same thing. >=20 > Anyway, now I'm going to set up a devfs.rules (and learn a new different > syntax for doing exactly the same thing). This looks like something that > could have been in the unix haters handbook. The devfs.conf method is inappropriate for runtime because if you don't do this in the kernel (as devfs(8) does) there is a race where the device initially has the wrong permissions. IMO, devfs.conf should either be taken out and shot or a parser to turn it into devfs(8) rules should be written. The current situation is utterly lame. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDnwcNXY6L6fI4GtQRAt7rAJ4zX4QiZjl2bctlwHvn2/uTPPhUpQCgmsKB Nny8BiMjn4+X+R9syTI8AVY= =OfSL -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 17:50:15 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D75716A541 for ; Tue, 13 Dec 2005 17:50:15 +0000 (GMT) (envelope-from fredthetree@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6063143D98 for ; Tue, 13 Dec 2005 17:49:53 +0000 (GMT) (envelope-from fredthetree@gmail.com) Received: by wproxy.gmail.com with SMTP id 36so180358wra for ; Tue, 13 Dec 2005 09:49:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ZHM3YRV+zfrvg+xuE5Dd36oSwrh7cTnTvnBrUxi1eKKtgkRuN/0GRDyQ2ZXVEyqRj4+0KdBXCxVfrI3b/FoTccDNl9a62TXHiUuMv06es7B7ARgi9IKMgp9CXIhG2EaQ3ybKJdO0FyM6m6LOrBBnitFvsfJ9W4Y+C5R61GEVkU0= Received: by 10.54.160.18 with SMTP id i18mr1129212wre; Tue, 13 Dec 2005 09:49:47 -0800 (PST) Received: by 10.54.146.19 with HTTP; Tue, 13 Dec 2005 09:49:47 -0800 (PST) Message-ID: Date: Tue, 13 Dec 2005 13:49:47 -0400 From: fredthetree To: freebsd-stable@freebsd.org In-Reply-To: MIME-Version: 1.0 References: <439DE88B.1090407@asd.aplus.net> <439E0B23.3060304@asd.aplus.net> <20051213025028.GC77268@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 17:50:15 -0000 On 12/13/05, fredthetree wrote: > > On 12/12/05, Peter Jeremy wrote: > > > On Mon, 2005-Dec-12 22:21:52 -0400, fredthetree wrote: > > >I just wanted to chime in and say I've had my 6.0-RELEASE #0 freeze up > > twice > > >in the past few days. never once had it happen with 5.x. everything > > locks, > > >no keyboard response, no mouse, and after several minutes it reboots > > itself, > > >and savecore starts up during boot.. > > > > This suggests you've had a panic (or something that develops into > > one). If you've got a crashdump, you can probably get enough > > information out of it for people to get an idea of what is wrong. > > Please have a look at: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ke= rneldebg-gdb.html > > > > > > -- > > Peter Jeremy > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kern= eldebug-gdb.html > (fixed the link) > > > does the following help? > > [/var/crash/vmcore.1] > ---------------------------------- > Unread portion of the kernel message buffer: > > > Fatal trap 12: page fault while in kernel mode > fault virtual address =3D 0x10 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x20:0xc0a7cf08 > stack pointer =3D 0x28:0xd56a694c > frame pointer =3D 0x28:0x0 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 29 (swi1: net) > trap number =3D 12 > panic: page fault > Uptime: 1d23h40m51s > Dumping 511 MB (2 chunks) > chunk 0: 1MB (159 pages) ... ok > chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 > 335 319 303 287 271 255 239 223 207 (CTRL-C to abort) (CTRL-C to abort) > (CTRL-C to abort) 191 175 159 143 127 111 95 79 63 47 31 15 > > #0 doadump () at pcpu.h:165 > 165 pcpu.h: No such file or directory. > in pcpu.h > ---------------------------------- > > [vmcore.0] > ---------------------------------- > Unread portion of the kernel message buffer: > =C3w=C40=BF=C10=C2=C1"=C0=ED=C1=C0J=F0=C2=C4=FC=C23=C4=D3=C2=C0=ED=C1=C0= =F3=C2D=FE=C1=C0=F3=C2=F0C=C2=C0=ED=C11=C4 > =C3=F0=DA=C3=C0=ED=C1=B4=C2=C4B=F0=C2=B0=C4=C1=C0=ED=C1"=C1DH=F0=C2=C0=C4= =C1=C0=ED=C1=C0=C4=C4=B9=C2=D0=C4=C1=C0=ED=C1@=FE=C1j.=C3@ > ---------------------------------- > (after this text displays, i am unable to view the kgdb prompt... type > exit [return] three times and i get back to the shell...) > > > From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 18:04:35 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D8A216A41F for ; Tue, 13 Dec 2005 18:04:35 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr5.xs4all.nl (smtp-vbr5.xs4all.nl [194.109.24.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B78543D80 for ; Tue, 13 Dec 2005 18:04:22 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr5.xs4all.nl (8.13.3/8.13.3) with ESMTP id jBDI4IbN028575; Tue, 13 Dec 2005 19:04:18 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 50413B827; Tue, 13 Dec 2005 19:04:18 +0100 (CET) Date: Tue, 13 Dec 2005 19:04:18 +0100 From: Roland Smith To: Brooks Davis Message-ID: <20051213180418.GA20852@slackbox.xs4all.nl> Mail-Followup-To: Brooks Davis , "[LoN]Kamikaze" , freebsd-stable@freebsd.org References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <20051213164947.GA17705@odin.ac.hmc.edu> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: "\[LoN\]Kamikaze" , freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 18:04:35 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 08:49:47AM -0800, Brooks Davis wrote: > On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote: > > On my FreeBSD 6-stable (the last build is less then 24hours ago) my > > devfs doesn't apply permissions set in /etc/devfs.conf when I attach new > > devices. I have to call: > > /etc/rc.d/devfs restart > > manually for the settings to be applied. This is rather uncomfortable in > > some cases (especially with my PDA). > >=20 > > I don't know weather this is the normal behaviour, anyway if it is, > > shouldn't devfs be restarted automatically as soon as external devices > > (usb, firewire, ir) are attached? >=20 > This is normal. devfs.conf is for boot only, you need devfs.rules for > runtime. Unfortunatly, the documentation of this fact and the > docuementation of devfs.rules sucks. Hmm, it's quite explicitly mentioned in the manual pages for devfs.conf and devfs.rules.=20 Feel free to suggest improvements... Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDnw0iEnfvsMMhpyURAgWVAJoC25tsvxHHgijbyakG0yXjjoaGKACdFtjF HnH+NrOwvhA40BuAnn/Jtyw= =LNa8 -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 18:13:02 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6C6E16A426 for ; Tue, 13 Dec 2005 18:13:02 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr9.xs4all.nl (smtp-vbr9.xs4all.nl [194.109.24.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB9B543D5D for ; Tue, 13 Dec 2005 18:12:54 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr9.xs4all.nl (8.13.3/8.13.3) with ESMTP id jBDICYnw051200; Tue, 13 Dec 2005 19:12:35 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 7573FB827; Tue, 13 Dec 2005 19:12:34 +0100 (CET) Date: Tue, 13 Dec 2005 19:12:34 +0100 From: Roland Smith To: Kevin Oberman Message-ID: <20051213181234.GB20852@slackbox.xs4all.nl> Mail-Followup-To: Kevin Oberman , Brooks Davis , "[LoN]Kamikaze" , freebsd-stable@freebsd.org References: <20051213164947.GA17705@odin.ac.hmc.edu> <20051213173714.C15515D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TRYliJ5NKNqkz5bu" Content-Disposition: inline In-Reply-To: <20051213173714.C15515D07@ptavv.es.net> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: "\[LoN\]Kamikaze" , freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 18:13:03 -0000 --TRYliJ5NKNqkz5bu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 09:37:13AM -0800, Kevin Oberman wrote: >=20 > You are being entirely too kind. The documentation for the practical use > of devfs at all sucks! Nothing I could find in the handbook, > either. It's a classic case of documentation written by programmers in > that the author can't look at his software from the standpoint of > someone who does not know anything about it. Good documentation really > needs to be written by someone sitting "on the outside" of the > development process. But this is a huge problem for commercial > applications where they actually hire writers, let alone for a volunteer > project.=20 The manual pages for devfs.conf and devfs.rules were definitely written "on= the outside". :-) > I thought that the devfs.rules page was pretty helpful, but neither the > devfs(8) nor the devfs(5) man pages mention either devfs.conf or > devfs.rules in "SEE ALSO" (although devfs.rules is mentioned in > "FILES"). No indication of how to use it or that there is actually a man > page for it. No mention of devfs.conf at all. devfs(5) provides no clue > at all that devfs does this sort of thing, either. Listing devfs.(conf|rules) in the SEE ALSO sections of devfs(5|8) sounds like a good idea. > Guess I'll try putting something together. Other than putting it in a > PR, should I do anything else with it? Putting in a PR, preferredly with a patch for the relevant manual pages, would be fine, I think. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --TRYliJ5NKNqkz5bu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDnw8SEnfvsMMhpyURAp3DAJ4l6WnndhFKuPOwXorMlMO7eVZ2bwCfVCoS TCZFdiyihcQsiweLHT7VxNo= =hgV9 -----END PGP SIGNATURE----- --TRYliJ5NKNqkz5bu-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 19:21:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDAED16A41F for ; Tue, 13 Dec 2005 19:21:44 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3702743D55 for ; Tue, 13 Dec 2005 19:21:44 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jBDJLhj1007669; Tue, 13 Dec 2005 11:21:43 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jBDJLhAO007665; Tue, 13 Dec 2005 11:21:43 -0800 Date: Tue, 13 Dec 2005 11:21:43 -0800 From: Brooks Davis To: Brooks Davis , "[LoN]Kamikaze" , freebsd-stable@freebsd.org Message-ID: <20051213192143.GA5926@odin.ac.hmc.edu> References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> <20051213180418.GA20852@slackbox.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline In-Reply-To: <20051213180418.GA20852@slackbox.xs4all.nl> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 19:21:44 -0000 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 07:04:18PM +0100, Roland Smith wrote: > On Tue, Dec 13, 2005 at 08:49:47AM -0800, Brooks Davis wrote: > > On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote: > > > On my FreeBSD 6-stable (the last build is less then 24hours ago) my > > > devfs doesn't apply permissions set in /etc/devfs.conf when I attach = new > > > devices. I have to call: > > > /etc/rc.d/devfs restart > > > manually for the settings to be applied. This is rather uncomfortable= in > > > some cases (especially with my PDA). > > >=20 > > > I don't know weather this is the normal behaviour, anyway if it is, > > > shouldn't devfs be restarted automatically as soon as external devices > > > (usb, firewire, ir) are attached? > >=20 > > This is normal. devfs.conf is for boot only, you need devfs.rules for > > runtime. Unfortunatly, the documentation of this fact and the > > docuementation of devfs.rules sucks. >=20 > Hmm, it's quite explicitly mentioned in the manual pages for devfs.conf a= nd > devfs.rules.=20 >=20 > Feel free to suggest improvements... 90% of the problem is the existence of devfs.conf. devfs(8) appears capable of everything it does, but we still have two ways to do it which is gratuitously confusing. The devfs(8) documentation is lacking in a complete, working example, any documentation of the rc.conf variables (which also aren't documented in rc.conf(5) either), and any mention of that the purpose or usage of lines like: [devfsrules_unhide_basic=3D2] Setting the mode of a device node really ought to be trivial, but last time I looked at it I was clearly missing something and couldn't get it working. I decided the device in question really ought to be attached at boot and thus gave up and used devfs.conf since I had productive work to do. Some cook easy to use cookbook example would be really helpful for those who don't have time to figure out all the details. Comparativly few people will want to do anything more than make a device or two more accessable. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDnx9GXY6L6fI4GtQRAqrDAJ0eNNBxca5Sac7w3HS7tJyhOdAeRQCdEHLV mHB2xd8oHpYImTpWmeHoLV4= =jWnE -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 19:44:48 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C678E16A422 for ; Tue, 13 Dec 2005 19:44:48 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6648743D46 for ; Tue, 13 Dec 2005 19:44:44 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Tue, 13 Dec 2005 11:44:40 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 9F5EF5D09; Tue, 13 Dec 2005 11:44:38 -0800 (PST) To: Brooks Davis In-reply-to: Your message of "Tue, 13 Dec 2005 11:21:43 PST." <20051213192143.GA5926@odin.ac.hmc.edu> Date: Tue, 13 Dec 2005 11:44:38 -0800 From: "Kevin Oberman" Message-Id: <20051213194438.9F5EF5D09@ptavv.es.net> Cc: "\[LoN\]Kamikaze" , freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 19:44:49 -0000 > Date: Tue, 13 Dec 2005 11:21:43 -0800 > From: Brooks Davis > Sender: owner-freebsd-stable@freebsd.org > > On Tue, Dec 13, 2005 at 07:04:18PM +0100, Roland Smith wrote: > > On Tue, Dec 13, 2005 at 08:49:47AM -0800, Brooks Davis wrote: > > > On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote: > > > > On my FreeBSD 6-stable (the last build is less then 24hours ago) my > > > > devfs doesn't apply permissions set in /etc/devfs.conf when I attach > new > > > > devices. I have to call: > > > > /etc/rc.d/devfs restart > > > > manually for the settings to be applied. This is rather uncomfortable> in > > > > some cases (especially with my PDA). > > > > > > > > I don't know weather this is the normal behaviour, anyway if it is, > > > > shouldn't devfs be restarted automatically as soon as external devices > > > > (usb, firewire, ir) are attached? > > > > > > This is normal. devfs.conf is for boot only, you need devfs.rules for > > > runtime. Unfortunatly, the documentation of this fact and the > > > docuementation of devfs.rules sucks. > > > > Hmm, it's quite explicitly mentioned in the manual pages for devfs.conf > > and devfs.rules. > > > > Feel free to suggest improvements... > > 90% of the problem is the existence of devfs.conf. devfs(8) appears > capable of everything it does, but we still have two ways to do it which > is gratuitously confusing. The devfs(8) documentation is lacking in a > complete, working example, any documentation of the rc.conf variables > (which also aren't documented in rc.conf(5) either), and any mention of > that the purpose or usage of lines like: > > [devfsrules_unhide_basic=2] Thee is clearly the big issues, but devfs.conf seems to have one capability that devfs.rules lacks...the ability to create symlinks in the devfs. Lots of folks create symlinks to /dev/cdrom and/or /dev/dvd, among others and I can't see any way to make devfs.rules do this. I suspect that the capability could be added, though, which would make devfs.conf totally redundant. I have been hacking away at the various devd and devfs man pages this morning to make them a bit better. /etc/defaults/rc.conf and rc.conf(5) also need to be fixed. (Those are next on my hit list.) > Setting the mode of a device node really ought to be trivial, but last > time I looked at it I was clearly missing something and couldn't get it > working. I decided the device in question really ought to be attached > at boot and thus gave up and used devfs.conf since I had productive > work to do. Some cook easy to use cookbook example would be really > helpful for those who don't have time to figure out all the details. > Comparativly few people will want to do anything more than make a device > or two more accessable. I have not had any problem setting the mode of devices in devfs.rules. In fact, at this time, it's the only thing I use devfs.rules for. I thought that the example in devfs.rules(5) was pretty clear and I just added them (I had a couple) and they worked! It may be setting the mode (or anything else) at boot time as opposed to when a devfs entry is created on the fly does not work correctly (and, hence, the need for devfs.conf). -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 19:45:15 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E843416A41F for ; Tue, 13 Dec 2005 19:45:15 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id B0BD943D8E for ; Tue, 13 Dec 2005 19:45:09 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 13 Dec 2005 19:45:07 -0000 Received: from p54A7C94A.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.201.74] by mail.gmx.net (mp037) with SMTP; 13 Dec 2005 20:45:07 +0100 X-Authenticated: #5465401 Message-ID: <439F24B2.1080408@gmx.de> Date: Tue, 13 Dec 2005 20:44:50 +0100 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> <20051213180418.GA20852@slackbox.xs4all.nl> <20051213192143.GA5926@odin.ac.hmc.edu> In-Reply-To: <20051213192143.GA5926@odin.ac.hmc.edu> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 19:45:16 -0000 Well, here are my conclusions. 1) The manpage for devfs.rules should mention that you have to set devfs_system_ruleset="yourruleset" in /etc/rc.conf . I didn't see it anywhere. 2) I have transferred all the rules in /etc/devfs.conf to /etc/devfs.rules, because I don't like to have 2 solutions for one task and because of the race condition mentioned in this list. 3) There is one kind of thing I cannot do in /etc/devfs.rules, creating links. So I am still doing this in /etc/devfs.conf (links don't cause race conditions anyway, I hope). One would think that "link ttyU0 pilot" would simply be translated to "ln -s /dev/ttyU0 /dev/pilot" which would simply create the link and it would work as soon as a ttyU0 device (my PDA) is there. But instead it checks weather the device exists (of course it doesn't since I didn't press the hotsync button during boot) and omits the creation of the link. So either the behaviour of /etc/rc.d/devfs has to be changed or it has to be dumped entirely and /sbin/devfs has to implement a way to create links (the solution I would prefer). - Dominic From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 19:52:23 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4940916A41F for ; Tue, 13 Dec 2005 19:52:23 +0000 (GMT) (envelope-from sperber@deinprogramm.de) Received: from h615406.serverkompetenz.net (h615406.serverkompetenz.net [81.169.143.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB90243D46 for ; Tue, 13 Dec 2005 19:52:22 +0000 (GMT) (envelope-from sperber@deinprogramm.de) Received: from h615406.serverkompetenz.net (localhost [127.0.0.1]) by h615406.serverkompetenz.net (Postfix) with ESMTP id 708F417108 for ; Tue, 13 Dec 2005 20:49:53 +0100 (MET) Received: from Michael-Sperbers-Computer.deinprogramm.de (p54A0C144.dip0.t-ipconnect.de [84.160.193.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by h615406.serverkompetenz.net (Postfix) with ESMTP id 2125217107 for ; Tue, 13 Dec 2005 20:49:53 +0100 (MET) Received: by Michael-Sperbers-Computer.deinprogramm.de (Postfix, from userid 2246) id A069E37D5FF; Tue, 13 Dec 2005 20:52:16 +0100 (CET) From: Michael Sperber To: freebsd-stable@freebsd.org Date: Tue, 13 Dec 2005 20:52:16 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) XEmacs/21.5-b21 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: mountd fails intermittently X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 19:52:23 -0000 I'm running 5.4-STABLE (about two weeks old), and have just set up an NFS server for the first time. Remote mounts sometimes work fine, and sometimes fail. The symptoms are that "showmount -e" sez showmount: can't do exports rpc and that "rpcinfo -u mountd" often works fine n times in a row, and then stops working, like so: ... Michael-Sperbers-Computer[105] rpcinfo -u matt mountd program 100005 version 1 ready and waiting rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 program 100005 version 2 is not available program 100005 version 3 ready and waiting Michael-Sperbers-Computer[106] rpcinfo -u matt mountd program 100005 version 1 ready and waiting rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 program 100005 version 2 is not available program 100005 version 3 ready and waiting Michael-Sperbers-Computer[107] rpcinfo -u matt mountd program 100005 version 1 ready and waiting rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 program 100005 version 2 is not available program 100005 version 3 ready and waiting Michael-Sperbers-Computer[108] rpcinfo -u matt mountd program 100005 version 1 ready and waiting rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 program 100005 version 2 is not available program 100005 version 3 ready and waiting Michael-Sperbers-Computer[109] rpcinfo -u matt mountd rpcinfo: RPC: Timed out program 100005 version 0 is not available >From then on, it'll keep failing. ... and, of course, doing it from the machine I really want to be doing it from reliably switches it to failure mode. Any ideas on what I should do? -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 20:07:20 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E59F716A420 for ; Tue, 13 Dec 2005 20:07:20 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 8B11F43D9A for ; Tue, 13 Dec 2005 20:07:05 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 13 Dec 2005 20:07:01 -0000 Received: from p54A7C94A.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.201.74] by mail.gmx.net (mp007) with SMTP; 13 Dec 2005 21:07:01 +0100 X-Authenticated: #5465401 Message-ID: <439F29CA.3020103@gmx.de> Date: Tue, 13 Dec 2005 21:06:34 +0100 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 CC: freebsd-stable@freebsd.org References: <20051213194438.9F5EF5D09@ptavv.es.net> In-Reply-To: <20051213194438.9F5EF5D09@ptavv.es.net> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 20:07:21 -0000 Here is a small patch for /etc/rc.d/devfs which makes it behave the way I suggested in my last mail. --- devfs.old Tue Dec 13 20:58:52 2005 +++ devfs Tue Dec 13 21:00:57 2005 @@ -43,8 +43,8 @@ cd /dev while read action device parameter; do case "${action}" in - l*) if [ -c ${device} -a ! -e ${parameter} ]; then - ln -fs ${device} ${parameter} + l*) if [ ! -e ${parameter} ]; then + ln -s ${device} ${parameter} fi ;; o*) if [ -c ${device} ]; then From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 20:13:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31F7A16A41F for ; Tue, 13 Dec 2005 20:13:03 +0000 (GMT) (envelope-from LukeD@pobox.com) Received: from thorn.pobox.com (vds.fauxbox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B8AC43D60 for ; Tue, 13 Dec 2005 20:13:01 +0000 (GMT) (envelope-from LukeD@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id EF140149; Tue, 13 Dec 2005 15:13:22 -0500 (EST) Received: from pool-71-112-202-40.sttlwa.dsl-w.verizon.net (pool-71-112-202-40.sttlwa.dsl-w.verizon.net [71.112.202.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 3CC2527DA; Tue, 13 Dec 2005 15:13:20 -0500 (EST) Date: Tue, 13 Dec 2005 12:12:52 -0800 (PST) From: Luke Dean X-X-Sender: lukas@border.crystalsphere.multiverse To: Atanas In-Reply-To: <439E8103.7020106@asd.aplus.net> Message-ID: <20051213114921.Q72503@border.crystalsphere.multiverse> References: <439DE88B.1090407@asd.aplus.net> <20051212214003.GA77268@cirb503493.alcatel.com.au> <439E3894.6060901@asd.aplus.net> <439E8103.7020106@asd.aplus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Luke Dean List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 20:13:03 -0000 On Tue, 13 Dec 2005, Atanas wrote: > Atanas said the following on 12/12/05 18:57: >> Peter Jeremy said the following on 12/12/05 13:40: >>> >>> When it hangs, break into DDB (Ctrl-Alt-Esc on the console or BREAK on >>> a serial console). >>> >> But if I have no keyboard response I won't be able to save it, right? >> > (replying to myself) > This is exactly what I was afraid would happen. The SATA based box just hung > up again, with all of the kernel debugging options in place: > > makeoptions DEBUG=-g > options KDB > options DDB > > But I wasn't able to do anything with the keyboard in order to save a > crashdump, so I got no other choices than hitting the reset button. > > Regards, > Atanas I posted this same problem recently. My latest attempt to troubleshoot the freezes was to snatch the SATA card out of the box. The machine has been running without any problems since. That was six days, 12 hours ago - the longest uptime I've had since I upgraded the machine to version 6. The only reason I added the SATA controller to the box was to set up a gmirror to make backups to, and since the machine kept freezing all the time I couldn't make decent backups anyway, so removing the SATA card didn't change the machine's duties at all. The reason I suspected the card might be the problem is that I installed it at the same time I upgraded to FreeBSD 6 (when the problems started), the card only cost $20, and the drives attached to the card were getting corrupted during crashes even though they weren't in use. The card was a SYBA SD-SATA-4P. I've also got an rl0 ethernet interface on the PCI bus also, and I wondered if it might be some kind of bus-mastering conflict or something. I still don't know if the problem was bad cheap hardware, bad interactions between cheap hardware, or a software problem. I suppose downgrading to 5.4 again might give some clues, but I don't really want to do that right now since the system finally seems to be stable again, albeit without my large disk array. This may easily have nothing to do with your problem, since we have so little information to go on, but the symptoms sound the same. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 20:23:01 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FE1A16A41F for ; Tue, 13 Dec 2005 20:23:01 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr9.xs4all.nl (smtp-vbr9.xs4all.nl [194.109.24.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D36043D6A for ; Tue, 13 Dec 2005 20:22:47 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr9.xs4all.nl (8.13.3/8.13.3) with ESMTP id jBDKMYpM026555; Tue, 13 Dec 2005 21:22:35 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 8D8DBB827; Tue, 13 Dec 2005 21:22:34 +0100 (CET) Date: Tue, 13 Dec 2005 21:22:34 +0100 From: Roland Smith To: Brooks Davis Message-ID: <20051213202234.GB23420@slackbox.xs4all.nl> Mail-Followup-To: Brooks Davis , "[LoN]Kamikaze" , freebsd-stable@freebsd.org References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> <20051213180418.GA20852@slackbox.xs4all.nl> <20051213192143.GA5926@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yNb1oOkm5a9FJOVX" Content-Disposition: inline In-Reply-To: <20051213192143.GA5926@odin.ac.hmc.edu> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: "\[LoN\]Kamikaze" , freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 20:23:01 -0000 --yNb1oOkm5a9FJOVX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 11:21:43AM -0800, Brooks Davis wrote: > > > This is normal. devfs.conf is for boot only, you need devfs.rules for > > > runtime. Unfortunatly, the documentation of this fact and the > > > docuementation of devfs.rules sucks. > >=20 > > Hmm, it's quite explicitly mentioned in the manual pages for devfs.conf= and > > devfs.rules.=20 > >=20 > > Feel free to suggest improvements... >=20 > 90% of the problem is the existence of devfs.conf. devfs(8) appears > capable of everything it does, but we still have two ways to do it which > is gratuitously confusing.=20 Hmm, I can mostly agree with that. The only real use I can think of for devfs.conf is when the devfs binary is corrupt. > The devfs(8) documentation is lacking in a > complete, working example,=20 What's wrong with the EXAMPLES section in devfs(8)? > any documentation of the rc.conf variables > (which also aren't documented in rc.conf(5) either), and any mention of > that the purpose or usage of lines like: >=20 > [devfsrules_unhide_basic=3D2] See devfs.rules(5), third para of DESCRIPTION. I agree it could use an example, and some explanation that you have to enable the ruleset in /etc/rc.conf. There is an example on my website: http://www.xs4all.nl/~rsmith/freebsd/#hotplug=20 Following is a patch for devfs.rules.5. Comments? Otherwise I'll submit it. ------------------ devfs.rules.5 patch -------------------------- --- devfs.rules.5 2005/12/13 19:59:29 1.6 +++ devfs.rules.5 2005/12/13 20:16:40 @@ -24,7 +24,7 @@ .\" .\" $FreeBSD: /repoman/r/ncvs/src/share/man/man5/devfs.rules.5,v 1.2.4.1 2= 005/07/27 12:03:48 keramida Exp $ .\" -.Dd May 17, 2005 +.Dd Dec 13, 2005 .Dt DEVFS.RULES 5 .Os .Sh NAME @@ -72,8 +72,22 @@ .Dq Li usb group, the following rule may be used: .Pp +.Dl "[localrules=3D10]" .Dl "add path 'da*s*' mode 0660 group usb" .Pp +The first line declares and starts a new ruleset, with the name +.Va localrules +and the number 10. Rulesets should have a unique name and number. All +rules that follow a ruleset declaration belong to that ruleset, untill a +new ruleset is started. This ruleset has to be enabled in +.Pa /etc/rc.conf=20 +to be the ruleset for the=20 +.Pa /dev=20 +filesystem. This is done by putting the following line in=20 +.Pa /etc/rc.conf : +.Pp +.Dl "devfs_system_ruleset=3D""localrules""" +.Pp To make all the .Xr uscanner 4 devices accessible to their owner and the @@ -81,6 +95,7 @@ group, a similar rule may be used: .Pp .Dl "add path 'uscanner*' mode 0660 group usb" +.Pp .Sh SEE ALSO .Xr glob 3 , .Xr devfs 5 , ------------------ devfs.rules.5 patch -------------------------- > Setting the mode of a device node really ought to be trivial, but last > time I looked at it I was clearly missing something and couldn't get it > working. I decided the device in question really ought to be attached > at boot and thus gave up and used devfs.conf since I had productive > work to do. Some cook easy to use cookbook example would be really > helpful for those who don't have time to figure out all the details. Maybe my freebsd page can help. Most of the things I learned while configuring FreeBSD are documented here. http://www.xs4all.nl/~rsmith/freebsd > Comparativly few people will want to do anything more than make a device > or two more accessable. Agreed. But the mechanism is more general because devfs can be used in multiple places (e.g. jails). Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --yNb1oOkm5a9FJOVX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDny2KEnfvsMMhpyURAtwSAJ9Q4KZE/NNfQOad2eAz9n4TaX11vQCfe5bu 4UrVyQJei+Eb1zxz4qOeZg0= =JRmz -----END PGP SIGNATURE----- --yNb1oOkm5a9FJOVX-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 20:30:10 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 649D916A41F for ; Tue, 13 Dec 2005 20:30:10 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr3.xs4all.nl (smtp-vbr3.xs4all.nl [194.109.24.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B48943D91 for ; Tue, 13 Dec 2005 20:29:35 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr3.xs4all.nl (8.13.3/8.13.3) with ESMTP id jBDKTPe7069811; Tue, 13 Dec 2005 21:29:29 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id C6A3BB827; Tue, 13 Dec 2005 21:29:24 +0100 (CET) Date: Tue, 13 Dec 2005 21:29:24 +0100 From: Roland Smith To: "[LoN]Kamikaze" Message-ID: <20051213202924.GC23420@slackbox.xs4all.nl> Mail-Followup-To: "[LoN]Kamikaze" , freebsd-stable@freebsd.org References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> <20051213180418.GA20852@slackbox.xs4all.nl> <20051213192143.GA5926@odin.ac.hmc.edu> <439F24B2.1080408@gmx.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KN5l+BnMqAQyZLvT" Content-Disposition: inline In-Reply-To: <439F24B2.1080408@gmx.de> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 20:30:10 -0000 --KN5l+BnMqAQyZLvT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 08:44:50PM +0100, [LoN]Kamikaze wrote: > Well, here are my conclusions. >=20 > 1) > The manpage for devfs.rules should mention that you have to set >=20 > devfs_system_ruleset=3D"yourruleset" >=20 > in /etc/rc.conf . I didn't see it anywhere. Agreed. I've posted a patch in this thread for that. If there are no comments, I'll send-pr it. =20 > 3) > There is one kind of thing I cannot do in /etc/devfs.rules, creating > links. So I am still doing this in /etc/devfs.conf (links don't cause > race conditions anyway, I hope). Maybe devd could be used for that. > One would think that "link ttyU0 pilot" would simply be translated to > "ln -s /dev/ttyU0 /dev/pilot" which would simply create the link and it > would work as soon as a ttyU0 device (my PDA) is there. But instead it > checks weather the device exists (of course it doesn't since I didn't > press the hotsync button during boot) and omits the creation of the link. >=20 > So either the behaviour of /etc/rc.d/devfs has to be changed or it has > to be dumped entirely and /sbin/devfs has to implement a way to create > links (the solution I would prefer). And maybe there should be a combination with devd? Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --KN5l+BnMqAQyZLvT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDny8kEnfvsMMhpyURAtsJAJ9g9Sb9iP8eL1hrsi858qcl/VwYNQCeJupT 9IaxTqJNVOtMTCdxvwFrfsM= =tNQu -----END PGP SIGNATURE----- --KN5l+BnMqAQyZLvT-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 20:41:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A228216A426 for ; Tue, 13 Dec 2005 20:41:44 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail1.fluidhosting.com (mail1.fluidhosting.com [204.14.90.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 23FE943D8B for ; Tue, 13 Dec 2005 20:41:36 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 96304 invoked by uid 399); 13 Dec 2005 20:41:34 -0000 Received: from unknown (HELO ?192.168.0.6?) (dougb@dougbarton.net@127.0.0.1) by 127.0.0.1 with SMTP; 13 Dec 2005 20:41:34 -0000 Message-ID: <439F31FB.1040209@FreeBSD.org> Date: Tue, 13 Dec 2005 12:41:31 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <439EF8B5.4030702@gmx.de> <20051213165416.GE71643@pc5-179.lri.fr> <439F02B3.60707@gmx.de> <20051213173821.GA25217@odin.ac.hmc.edu> In-Reply-To: <20051213173821.GA25217@odin.ac.hmc.edu> X-Enigmail-Version: 0.93.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 20:41:44 -0000 I hacked together the current mess over two and a half years ago for one simple reason, so that the functionality that used to be in the system prior to rcNG would still be there. Since then, we've had roughly 18 rounds of this same discussion, but no one has actually stepped up to do the work of converting /etc/rc.d/devfs to use rules. (Oh, and as someone else already pointed out, whatever you replace it with has to be able to add symlinks as well.) If someone wants to do that, great! If not, whining about it isn't really all that useful of an exercise. Everyone already knows it needs to be updated. Same goes for the documentation btw. Patches are welcome, complaining that "it should be better" is not. Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 20:43:19 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27CBB16A41F for ; Tue, 13 Dec 2005 20:43:19 +0000 (GMT) (envelope-from marko.raiha@zendata.fi) Received: from mail.dataclub.fi (mail.dataclub.fi [194.240.247.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0063443D8A for ; Tue, 13 Dec 2005 20:42:58 +0000 (GMT) (envelope-from marko.raiha@zendata.fi) Received: from localhost (mail.private.dataclub.fi [192.168.123.3]) by mail.dataclub.fi (Postfix) with ESMTP id 8CF3E44C5 for ; Tue, 13 Dec 2005 22:42:52 +0200 (EET) Received: from mail.dataclub.fi ([192.168.123.3]) by localhost (mail.dataclub.fi [192.168.123.3]) (amavisd-new, port 10024) with ESMTP id 95933-01 for ; Tue, 13 Dec 2005 22:42:51 +0200 (EET) Received: by mail.dataclub.fi (Postfix, from userid 701) id 1E2C144E1; Tue, 13 Dec 2005 22:42:51 +0200 (EET) Received: from [192.168.67.95] (unknown [83.145.214.193]) by mail.dataclub.fi (Postfix) with ESMTP id 9286143A6 for ; Tue, 13 Dec 2005 22:42:50 +0200 (EET) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: References: Content-Type: multipart/mixed; boundary=Apple-Mail-12--566936033 Message-Id: From: =?ISO-8859-1?Q?R=E4ih=E4_Marko?= Date: Tue, 13 Dec 2005 22:42:50 +0200 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: amavisd-new at dataclub.fi Subject: Re: Crashing recent 6-STABLE, HP DL145G2 - LOR X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 20:43:19 -0000 --Apple-Mail-12--566936033 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Hi, On 13.12.2005, at 19.21, R=E4ih=E4 Marko wrote: > I have installed i386 6.0-RELEASE to two HP DL145G2-servers and they > crash soon after (1-2 minutes) booting up to login prompt. Sometimes > they boot up without crashing and sometimes with crashing. > > I have now upgraded to RELENG_6 and crashing continues. What amazes > me is that these two machines do the same so I don't believe it would > be broken hardware. > > I have copied dmesg, uname -a and kgdb backtrace information to > the following file on the web-site. > > http://www.zendata.fi/FreeBSD/debug_information.txt.gz > > I have core file so I can dig more information if it is needed. I have now compiled new kernel with INVARIANTS and WITNESS. Reason for crashing seems to be lock order reversal in ipf-module. lock order reversal: (sleepable after non-sleepable) 1st 0xc4e42b40 ipf IP state rwlock (ipf IP state rwlock) @ /usr/src/=20 sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_state.c:2808 2nd 0xc0911744 user map (user map) @ /usr/src/sys/vm/vm_map.c:2997 How this should be fixed? --Apple-Mail-12--566936033 Content-Transfer-Encoding: 7bit Content-Type: text/plain; x-unix-mode=0644; name="debug_information2.txt" Content-Disposition: attachment; filename=debug_information2.txt rigel# kgdb kernel.debug.6 vmcore.6 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: lock order reversal: (sleepable after non-sleepable) 1st 0xc4e42b40 ipf IP state rwlock (ipf IP state rwlock) @ /usr/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_state.c:2808 2nd 0xc0911744 user map (user map) @ /usr/src/sys/vm/vm_map.c:2997 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x88 fault code = supervisor read, page not present instruction pointer = 0x20:0xc4e38dbf stack pointer = 0x28:0xe5000c6c frame pointer = 0x28:0xe5000c74 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 = 48 (swi4: clock) trap number = 12 panic: page fault Uptime: 56s Dumping 1022 MB (2 chunks) chunk 0: 1MB (151 pages) ... ok chunk 1: 1023MB (261664 pages) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) ================================================================================ (kgdb) where #0 doadump () at pcpu.h:165 #1 0xc0630754 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc06309d2 in panic (fmt=0xc0832f51 "%s") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc07e96c8 in trap_fatal (frame=0xe5000c2c, eva=136) at /usr/src/sys/i386/i386/trap.c:836 #4 0xc07e942f in trap_pfault (frame=0xe5000c2c, usermode=0, eva=136) at /usr/src/sys/i386/i386/trap.c:744 #5 0xc07e90c1 in trap (frame= {tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = 0, tf_esi = -992533416, tf_ebp = -452981644, tf_isp = -452981672, tf_ebx = -991469056, tf_edx = -995095936, tf_ecx = 4, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -991720001, tf_cs = 32, tf_eflags = 590406, tf_esp = -992533504, tf_ss = -992533504}) at /usr/src/sys/i386/i386/trap.c:434 #6 0xc07d8eba in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc4e38dbf in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) --Apple-Mail-12--566936033 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1; format=flowed Regards, --=20 Marko R=E4ih=E4 --Apple-Mail-12--566936033-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 20:55:58 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B8CE16A41F for ; Tue, 13 Dec 2005 20:55:58 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17F8843D77 for ; Tue, 13 Dec 2005 20:55:40 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jBDKtd8R021421; Tue, 13 Dec 2005 12:55:39 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jBDKtdc5021420; Tue, 13 Dec 2005 12:55:39 -0800 Date: Tue, 13 Dec 2005 12:55:39 -0800 From: Brooks Davis To: Brooks Davis , "[LoN]Kamikaze" , freebsd-stable@freebsd.org Message-ID: <20051213205539.GA17830@odin.ac.hmc.edu> References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> <20051213180418.GA20852@slackbox.xs4all.nl> <20051213192143.GA5926@odin.ac.hmc.edu> <20051213202234.GB23420@slackbox.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline In-Reply-To: <20051213202234.GB23420@slackbox.xs4all.nl> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.5 required=8.0 tests=WEIRD_QUOTING autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 20:55:58 -0000 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 09:22:34PM +0100, Roland Smith wrote: > On Tue, Dec 13, 2005 at 11:21:43AM -0800, Brooks Davis wrote: > > > > > This is normal. devfs.conf is for boot only, you need devfs.rules = for > > > > runtime. Unfortunatly, the documentation of this fact and the > > > > docuementation of devfs.rules sucks. > > >=20 > > > Hmm, it's quite explicitly mentioned in the manual pages for devfs.co= nf and > > > devfs.rules.=20 > > >=20 > > > Feel free to suggest improvements... > >=20 > > 90% of the problem is the existence of devfs.conf. devfs(8) appears > > capable of everything it does, but we still have two ways to do it which > > is gratuitously confusing.=20 >=20 > Hmm, I can mostly agree with that. The only real use I can think of > for devfs.conf is when the devfs binary is corrupt. That seems like a non issue. In that case you're in recovery mode and presumably need to know how to drive chown and chmod. :) > > The devfs(8) documentation is lacking in a > > complete, working example,=20 >=20 > What's wrong with the EXAMPLES section in devfs(8)? It's fine. Referring to devfs(8) was poor word choice on my part. I meant the system as a whole including devfs.rules. > > any documentation of the rc.conf variables > > (which also aren't documented in rc.conf(5) either), and any mention of > > that the purpose or usage of lines like: > >=20 > > [devfsrules_unhide_basic=3D2] >=20 > See devfs.rules(5), third para of DESCRIPTION. I agree it could use an > example, and some explanation that you have to enable the ruleset in > /etc/rc.conf. That's quite easy to miss. I saw the bit about comments and my eyes glazed over and skipped the rest. Breaking out the paragraph into bullets might be an improvement. > There is an example on my website: > http://www.xs4all.nl/~rsmith/freebsd/#hotplug=20 > > Following is a patch for devfs.rules.5. Comments? Otherwise I'll submit i= t. Content looks good to me. > ------------------ devfs.rules.5 patch -------------------------- > --- devfs.rules.5 2005/12/13 19:59:29 1.6 > +++ devfs.rules.5 2005/12/13 20:16:40 > @@ -24,7 +24,7 @@ > .\" > .\" $FreeBSD: /repoman/r/ncvs/src/share/man/man5/devfs.rules.5,v 1.2.4.1= 2005/07/27 12:03:48 keramida Exp $ > .\" > -.Dd May 17, 2005 > +.Dd Dec 13, 2005 > .Dt DEVFS.RULES 5 > .Os > .Sh NAME > @@ -72,8 +72,22 @@ > .Dq Li usb > group, the following rule may be used: > .Pp > +.Dl "[localrules=3D10]" > .Dl "add path 'da*s*' mode 0660 group usb" > .Pp > +The first line declares and starts a new ruleset, with the name > +.Va localrules > +and the number 10. Rulesets should have a unique name and number. All > +rules that follow a ruleset declaration belong to that ruleset, untill a > +new ruleset is started. This ruleset has to be enabled in > +.Pa /etc/rc.conf=20 > +to be the ruleset for the=20 > +.Pa /dev=20 > +filesystem. This is done by putting the following line in=20 > +.Pa /etc/rc.conf : > +.Pp > +.Dl "devfs_system_ruleset=3D""localrules""" =46rom looking in rc.conf(5), I think this should be: =2EPa /etc/rc.conf : =2EBd -literal devfs_system_ruleset=3D"localrules" =2EEd > +.Pp > To make all the > .Xr uscanner 4 > devices accessible to their owner and the > @@ -81,6 +95,7 @@ > group, a similar rule may be used: > .Pp > .Dl "add path 'uscanner*' mode 0660 group usb" > +.Pp I think this is unnecessary. It's certainly not common practice. > .Sh SEE ALSO > .Xr glob 3 , > .Xr devfs 5 , > ------------------ devfs.rules.5 patch -------------------------- >=20 > > Setting the mode of a device node really ought to be trivial, but last > > time I looked at it I was clearly missing something and couldn't get it > > working. I decided the device in question really ought to be attached > > at boot and thus gave up and used devfs.conf since I had productive > > work to do. Some cook easy to use cookbook example would be really > > helpful for those who don't have time to figure out all the details. >=20 > Maybe my freebsd page can help. Most of the things I learned while > configuring FreeBSD are documented here. >=20 > http://www.xs4all.nl/~rsmith/freebsd The example you site looks like excellent handbook fodder. > > Comparativly few people will want to do anything more than make a device > > or two more accessable. >=20 > Agreed. But the mechanism is more general because devfs can be used in > multiple places (e.g. jails). Definitely. The full features look quite cool and useful. My concern is simply that it's easy to find out how to do the common thing without having to understand all the complex things you can do. Thanks for writing this manpage and working to improve it! -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDnzVKXY6L6fI4GtQRAtmzAJ9WCYsbviI5/6qZUrdC57uNUTpksQCgy6Z0 2dnIy01UabztyQwK2nfYw38= =7BkT -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 21:31:42 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0127F16A41F for ; Tue, 13 Dec 2005 21:31:42 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr14.xs4all.nl (smtp-vbr14.xs4all.nl [194.109.24.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id B42DF43D73 for ; Tue, 13 Dec 2005 21:31:27 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr14.xs4all.nl (8.13.3/8.13.3) with ESMTP id jBDLVLqD012230; Tue, 13 Dec 2005 22:31:22 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id AA787B827; Tue, 13 Dec 2005 22:31:21 +0100 (CET) Date: Tue, 13 Dec 2005 22:31:21 +0100 From: Roland Smith To: Brooks Davis Message-ID: <20051213213121.GA26709@slackbox.xs4all.nl> Mail-Followup-To: Brooks Davis , "[LoN]Kamikaze" , freebsd-stable@freebsd.org References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> <20051213180418.GA20852@slackbox.xs4all.nl> <20051213192143.GA5926@odin.ac.hmc.edu> <20051213202234.GB23420@slackbox.xs4all.nl> <20051213205539.GA17830@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline In-Reply-To: <20051213205539.GA17830@odin.ac.hmc.edu> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: "\[LoN\]Kamikaze" , freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 21:31:42 -0000 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 12:55:39PM -0800, Brooks Davis wrote: > > What's wrong with the EXAMPLES section in devfs(8)? >=20 > It's fine. Referring to devfs(8) was poor word choice on my part. I > meant the system as a whole including devfs.rules. >=20 > > > any documentation of the rc.conf variables > > > (which also aren't documented in rc.conf(5) either), and any mention = of > > > that the purpose or usage of lines like: > > >=20 > > > [devfsrules_unhide_basic=3D2] > >=20 > > See devfs.rules(5), third para of DESCRIPTION. I agree it could use an > > example, and some explanation that you have to enable the ruleset in > > /etc/rc.conf. >=20 > That's quite easy to miss. I saw the bit about comments and my eyes > glazed over and skipped the rest. Breaking out the paragraph into > bullets might be an improvement. >=20 > > There is an example on my website: > > http://www.xs4all.nl/~rsmith/freebsd/#hotplug=20 > > > > Following is a patch for devfs.rules.5. Comments? Otherwise I'll submit= it. >=20 > Content looks good to me. > From looking in rc.conf(5), I think this should be: >=20 > .Pa /etc/rc.conf : > .Bd -literal > devfs_system_ruleset=3D"localrules" > .Ed Ok, I'll incorporate that, and send-pr it. > > +.Pp > > To make all the > > .Xr uscanner 4 > > devices accessible to their owner and the > > @@ -81,6 +95,7 @@ > > group, a similar rule may be used: > > .Pp > > .Dl "add path 'uscanner*' mode 0660 group usb" > > +.Pp >=20 > I think this is unnecessary. It's certainly not common practice. It's just another example. =20 > > .Sh SEE ALSO > > .Xr glob 3 , > > .Xr devfs 5 , > > ------------------ devfs.rules.5 patch -------------------------- > >=20 > > > Setting the mode of a device node really ought to be trivial, but last > > > time I looked at it I was clearly missing something and couldn't get = it > > > working. I decided the device in question really ought to be attached > > > at boot and thus gave up and used devfs.conf since I had productive > > > work to do. Some cook easy to use cookbook example would be really > > > helpful for those who don't have time to figure out all the details. > >=20 > > Maybe my freebsd page can help. Most of the things I learned while > > configuring FreeBSD are documented here. > >=20 > > http://www.xs4all.nl/~rsmith/freebsd >=20 > The example you site looks like excellent handbook fodder. Do you want to submit it? I won't have time to do it before mid-januari at least. =20 > > > Comparativly few people will want to do anything more than make a dev= ice > > > or two more accessable. > >=20 > > Agreed. But the mechanism is more general because devfs can be used in > > multiple places (e.g. jails). >=20 > Definitely. The full features look quite cool and useful. My concern is > simply that it's easy to find out how to do the common thing without > having to understand all the complex things you can do. Thanks for > writing this manpage and working to improve it! Thanks! Actually, my motivation for writing the manpages was to stop the tide of "how do I configure devfs" postings on -questions. Unfortunately, once you understand the details of the system well enough to document it, some of the details will seem so obvious that you don't document them. :-) Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDnz2pEnfvsMMhpyURAhJ3AJsEy24dGk07i5IFJZdzcl2f0+0tQgCcDdCM ZFuhjB2aObj7p1mh8fALMEw= =FYyP -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 22:00:16 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF0AD16A41F for ; Tue, 13 Dec 2005 22:00:16 +0000 (GMT) (envelope-from jakub.laszczynski@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60DFC43D45 for ; Tue, 13 Dec 2005 22:00:16 +0000 (GMT) (envelope-from jakub.laszczynski@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1750843nzo for ; Tue, 13 Dec 2005 14:00:15 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=NgKPyXjJSOxIgIV+ZParESs6y4LHFPAwv90DJ+lSgOSSCLNFd8NRnLsCTB7zorow3Ohp9sEvFIJDZb0D08m04YRUIZTMqpaVi0DBfSjkUPYF0Of6MKeYjDYKvYdyGK3OCF/XkSxYuWh1+sy11vuU1SO2GiiD4bJUBoVMB2Ozslw= Received: by 10.65.234.5 with SMTP id l5mr13301qbr; Tue, 13 Dec 2005 14:00:12 -0800 (PST) Received: by 10.64.213.8 with HTTP; Tue, 13 Dec 2005 14:00:12 -0800 (PST) Message-ID: Date: Tue, 13 Dec 2005 23:00:12 +0100 From: =?ISO-8859-2?Q?Jakub_=A3aszczy=F1ski?= To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: problems with usb keyboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 22:00:16 -0000 hi. i bought recently an usb keyboard. but when i connected it and started up fbsd-6.0-stable(ukbd is in kernel). when i tried to login, and enter my log/pass, it just did the ' ' (space character) instead of normal chars. my next step was editing /boot/loader.conf and inserting: hint.atkbd.0.flags=3D"0x1" reboot, and the same thing is happening. after inserting: ukbd_load=3D"YES" to /boot/loader.conf, the system just freezes after loading driver atkbd, i made some experiments connecting, plugged in my old ps2 keyboard and run simple loop doing ls /dev/kbd*, after i plugged in device appeared, and then i tried to do: kbdcontrol -k /dev/ukbd0 < /dev/console, but both keyboard freezed. do you have any suggestions, what might be wrong, what can i check or just what to do to make it work. the keyboard is: http://www.geniusnet.com.tw/product/product-1.asp?pdtno=3D548 From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 22:08:31 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B609316A420 for ; Tue, 13 Dec 2005 22:08:31 +0000 (GMT) (envelope-from feanor@kh405.net) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A12B43D5A for ; Tue, 13 Dec 2005 22:08:30 +0000 (GMT) (envelope-from feanor@kh405.net) Received: from melkor.kh405.net (plb95-2-82-236-78-224.fbx.proxad.net [82.236.78.224]) by smtp3-g19.free.fr (Postfix) with ESMTP id 7EBE040533; Tue, 13 Dec 2005 23:08:29 +0100 (CET) Received: by melkor.kh405.net (Postfix, from userid 1001) id 910B0678C; Tue, 13 Dec 2005 23:09:21 +0100 (CET) Date: Tue, 13 Dec 2005 23:09:21 +0100 From: Marwan Burelle To: Anish Mistry Message-ID: <20051213220921.GA924@melkor.kh405.net> References: <439EF8B5.4030702@gmx.de> <20051213165416.GE71643@pc5-179.lri.fr> <200512131223.56159.mistry.7@osu.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline In-Reply-To: <200512131223.56159.mistry.7@osu.edu> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, "\[LoN\]Kamikaze" Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 22:08:31 -0000 --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 12:23:26PM -0500, Anish Mistry wrote: > > There maybe a better way, but "it works"=A9 ;) > You should be using /etc/devfs.rules >=20 > Search the mailing list for examples and setup. Yes, I know, some month ago I wrote a little documentation (in french [1]) for using USB keys on a FreeBSD worstation. Someone point me out to devfs.rules, but at that time I couldn't find any clear documentation, nor any clear way of doing some more complex things. My goal was to simulate Linux+Gnome behaviour when USB key are plugged, that is, transparently mount it with the user id so that Gnome desktop shows it with an appropriate icon[2]. Using devfs.conf was a simple way of fixing permissions but in the context not the only one. I used devd.conf, since I want some other task to do, mainly a script that find if a user is logged with X, and mount the right device with its id, this involve also testing if the device use da0 or da0s1 and also manage the possibility of plugin more than one umass devices at the same time. In that context using devfs.conf or devfs.rules doesn't realy change (as a user point of view, in particular when you don't realy know the difference.) I know now that I was wrong, but as the current discussion shows, there is (was ? ;) a lack of good documentation on the subject. [1] : http://www.lri.fr/~burelle/BSD/USBKey-FreeBSD.html [2] : My starting was point here : http://caia.swin.edu.au/reports/041130A/ --=20 Marwan Burelle, http://www.lri.fr/~burelle ( burelle@lri.fr | Marwan.Burelle@ens.fr ) http://www.cduce.org --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDn0aRI+2UvUKfgvgRAuqGAJ9r0u1hD2/5+Y9kuGYB+X18PMaXPQCghrvg +QCRn6kYbMf0tT3VS++Rguk= =6G+D -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 22:23:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA2EE16A41F for ; Tue, 13 Dec 2005 22:23:44 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2E5C43D4C for ; Tue, 13 Dec 2005 22:23:43 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IRG00LO1JQVIZ80@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Tue, 13 Dec 2005 23:28:07 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IRG00M6OJO1PD90@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Tue, 13 Dec 2005 23:26:25 +0100 (CET) Date: Tue, 13 Dec 2005 21:37:04 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <200512131651.jBDGp2Lx029496@lurza.secnetix.de> To: freebsd-stable@freebsd.org Message-id: <20051213213704.7b4fb83a.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20051208001857.68ac4fef.torfinn.ingolfsen@broadpark.no> <200512131651.jBDGp2Lx029496@lurza.secnetix.de> Subject: Re: FreeBSD 6.0 as storage server with raid5? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 22:23:44 -0000 On Tue, 13 Dec 2005 17:51:02 +0100 (CET) Oliver Fromme wrote: > There's no reason why you shouldn't be able to do that. Noted. Good to know. :-) > Note that the HPT 18x0A have an onboard processor which > does the XOR (parity) calculations for RAID-5. For the > non-A versions, the host CPU has to do those calculations > (in the driver), which can be quite a noticable burden. Noted, this is valuable information, thanks! I found a test: http://www6.tomshardware.com/storage/20040625/sata-raid-04.html and this test confirms that the RocketRAID 1640 is software raid only. > Some controllers have a setting to enable staged starting > of the drives, i.e. one after the other. This can reduce > the maximum PSU requirement considerably if you have a > lot of disks. Noted, I'll look out for this. > PS: I assume you already know this, but I'd like to note > this for all readers: RAID (of any kind) does not replace > reliable backups. Always make proper backups, independent > of your RAID (if any). I agree 100%, and this cannot be told to often. In my case, the backup server will probably be another FreeBSD box with external firewire drives, to keep costs down. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 22:26:47 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82C5816A41F for ; Tue, 13 Dec 2005 22:26:47 +0000 (GMT) (envelope-from lonewolf-freebsd@earthmagic.org) Received: from ppp162-248.static.internode.on.net (ppp162-248.static.internode.on.net [150.101.162.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8166443D55 for ; Tue, 13 Dec 2005 22:26:46 +0000 (GMT) (envelope-from lonewolf-freebsd@earthmagic.org) Received: from [192.168.2.3] (sarah.zone2.earthmagic.org [192.168.2.3]) by ppp162-248.static.internode.on.net (Postfix-MSA) with ESMTP id 520BE91F1; Wed, 14 Dec 2005 09:26:45 +1100 (EST) Message-ID: <439F4AA4.5070500@earthmagic.org> Date: Wed, 14 Dec 2005 09:26:44 +1100 From: Johny Mattsson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051003) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "[LoN]Kamikaze" , freebsd-stable@freebsd.org References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> <20051213180418.GA20852@slackbox.xs4all.nl> <20051213192143.GA5926@odin.ac.hmc.edu> <439F24B2.1080408@gmx.de> In-Reply-To: <439F24B2.1080408@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 22:26:47 -0000 On 12/14/05 06:44, [LoN]Kamikaze wrote: > 3) > There is one kind of thing I cannot do in /etc/devfs.rules, creating > links. So I am still doing this in /etc/devfs.conf (links don't cause > race conditions anyway, I hope). > > One would think that "link ttyU0 pilot" would simply be translated to > "ln -s /dev/ttyU0 /dev/pilot" which would simply create the link and it > would work as soon as a ttyU0 device (my PDA) is there. But instead it > checks weather the device exists (of course it doesn't since I didn't > press the hotsync button during boot) and omits the creation of the link. Note that while for you it might be sufficient to have a hard coded link from /dev/pilot to /dev/ttyU0, that is not necessarily the case if you have multiple USB serial gadgets. The way I handled it is by using an entry in /etc/usbd.conf: # # Fixup permissions for Palm Handheld ucom devices # (set here and not in devfs.rules since we only want to apply # the change to Palm com ports, not all USB com ports) device "PalmHandheld" devname "ucom[0-9]+" vendor 0x0830 attach "/bin/chmod 0666 /dev/${DEVNAME} ; /bin/ln -s /dev/${DEVNAME} /dev/pilot" detach "rm -f /dev/pilot Having said that, it would be great to be able to create links from devfs.rules - I'd certainly use it for my /dev/cdrom entry! Cheers, /Johny -- Johny Mattsson - Making IT work ,-. ,-. ,-. When all else fails, http://www.earthmagic.org _.' `-' `-' Murphy's Law still works! From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 23:17:26 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5D6416A41F for ; Tue, 13 Dec 2005 23:17:26 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01A8C43D55 for ; Tue, 13 Dec 2005 23:17:12 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jBDNHB9M012321; Tue, 13 Dec 2005 15:17:12 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jBDNHBAV012320; Tue, 13 Dec 2005 15:17:11 -0800 Date: Tue, 13 Dec 2005 15:17:11 -0800 From: Brooks Davis To: Brooks Davis , "[LoN]Kamikaze" , freebsd-stable@freebsd.org Message-ID: <20051213231711.GB17830@odin.ac.hmc.edu> References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> <20051213180418.GA20852@slackbox.xs4all.nl> <20051213192143.GA5926@odin.ac.hmc.edu> <20051213202234.GB23420@slackbox.xs4all.nl> <20051213205539.GA17830@odin.ac.hmc.edu> <20051213213121.GA26709@slackbox.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uZ3hkaAS1mZxFaxD" Content-Disposition: inline In-Reply-To: <20051213213121.GA26709@slackbox.xs4all.nl> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 23:17:27 -0000 --uZ3hkaAS1mZxFaxD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 10:31:21PM +0100, Roland Smith wrote: > On Tue, Dec 13, 2005 at 12:55:39PM -0800, Brooks Davis wrote: > > > > What's wrong with the EXAMPLES section in devfs(8)? > >=20 > > It's fine. Referring to devfs(8) was poor word choice on my part. I > > meant the system as a whole including devfs.rules. > >=20 > > > > any documentation of the rc.conf variables > > > > (which also aren't documented in rc.conf(5) either), and any mentio= n of > > > > that the purpose or usage of lines like: > > > >=20 > > > > [devfsrules_unhide_basic=3D2] > > >=20 > > > See devfs.rules(5), third para of DESCRIPTION. I agree it could use an > > > example, and some explanation that you have to enable the ruleset in > > > /etc/rc.conf. > >=20 > > That's quite easy to miss. I saw the bit about comments and my eyes > > glazed over and skipped the rest. Breaking out the paragraph into > > bullets might be an improvement. > >=20 > > > There is an example on my website: > > > http://www.xs4all.nl/~rsmith/freebsd/#hotplug=20 > > > > > > Following is a patch for devfs.rules.5. Comments? Otherwise I'll subm= it it. > >=20 > > Content looks good to me. > > > From looking in rc.conf(5), I think this should be: > >=20 > > .Pa /etc/rc.conf : > > .Bd -literal > > devfs_system_ruleset=3D"localrules" > > .Ed >=20 > Ok, I'll incorporate that, and send-pr it. Great. > > > +.Pp > > > To make all the > > > .Xr uscanner 4 > > > devices accessible to their owner and the > > > @@ -81,6 +95,7 @@ > > > group, a similar rule may be used: > > > .Pp > > > .Dl "add path 'uscanner*' mode 0660 group usb" > > > +.Pp > >=20 > > I think this is unnecessary. It's certainly not common practice. >=20 > It's just another example. I was referring to the .Pp before the .Sh below. > > > .Sh SEE ALSO > > > .Xr glob 3 , > > > .Xr devfs 5 , > > > ------------------ devfs.rules.5 patch -------------------------- > > >=20 > > > > Setting the mode of a device node really ought to be trivial, but l= ast > > > > time I looked at it I was clearly missing something and couldn't ge= t it > > > > working. I decided the device in question really ought to be attac= hed > > > > at boot and thus gave up and used devfs.conf since I had productive > > > > work to do. Some cook easy to use cookbook example would be really > > > > helpful for those who don't have time to figure out all the details. > > >=20 > > > Maybe my freebsd page can help. Most of the things I learned while > > > configuring FreeBSD are documented here. > > >=20 > > > http://www.xs4all.nl/~rsmith/freebsd > >=20 > > The example you site looks like excellent handbook fodder. >=20 > Do you want to submit it? I won't have time to do it before mid-januari > at least. > =20 > > > > Comparativly few people will want to do anything more than make a d= evice > > > > or two more accessable. > > >=20 > > > Agreed. But the mechanism is more general because devfs can be used in > > > multiple places (e.g. jails). > >=20 > > Definitely. The full features look quite cool and useful. My concern = is > > simply that it's easy to find out how to do the common thing without > > having to understand all the complex things you can do. Thanks for > > writing this manpage and working to improve it! >=20 > Thanks! Actually, my motivation for writing the manpages was to stop the > tide of "how do I configure devfs" postings on -questions. >=20 > Unfortunately, once you understand the details of the system well enough > to document it, some of the details will seem so obvious that you don't > document them. :-) Yes, that's always a problem. I haven't mastered the necessary xen-like state where I can forget what I know when I'm reading my own work. :) -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --uZ3hkaAS1mZxFaxD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDn1Z3XY6L6fI4GtQRAohcAJ0ZSVzHxAZin55hIiuemWqEaZgPxACfdHdy p2UxsG3h0bgZsGdBClGhfG0= =TCBq -----END PGP SIGNATURE----- --uZ3hkaAS1mZxFaxD-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 23:32:14 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05E5316A41F for ; Tue, 13 Dec 2005 23:32:14 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id E7B6D43D69 for ; Tue, 13 Dec 2005 23:32:11 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 13 Dec 2005 23:32:09 -0000 Received: from p54A7DBAF.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.219.175] by mail.gmx.net (mp017) with SMTP; 14 Dec 2005 00:32:09 +0100 X-Authenticated: #5465401 Message-ID: <439F59E8.9050505@gmx.de> Date: Wed, 14 Dec 2005 00:31:52 +0100 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> <20051213180418.GA20852@slackbox.xs4all.nl> <20051213192143.GA5926@odin.ac.hmc.edu> <439F24B2.1080408@gmx.de> <439F4AA4.5070500@earthmagic.org> In-Reply-To: <439F4AA4.5070500@earthmagic.org> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 23:32:14 -0000 I agree that a more flexible approach is generally better, but since it's not necessary I don't want to create an extra entry in my /etc/usbd.conf (one more file to worry about during mergemaster). Thus I think the best solution would be to dump devfs.conf and /etc/rc.d/devfs entirely (or leave it optional for backwards compatibility) and give devfs the ability to create links. I have a dislike for inconsistent solutions and I think most people here share this dislike. It's just what happens when software grows. Sooner or later you get to the point where you should throw away 80% of what's there and turn the rest into something that does what needs to be done. Johny Mattsson wrote: > Note that while for you it might be sufficient to have a hard coded link > from /dev/pilot to /dev/ttyU0, that is not necessarily the case if you > have multiple USB serial gadgets. > The way I handled it is by using an entry in /etc/usbd.conf: > > # > # Fixup permissions for Palm Handheld ucom devices > # (set here and not in devfs.rules since we only want to apply > # the change to Palm com ports, not all USB com ports) > device "PalmHandheld" > devname "ucom[0-9]+" > vendor 0x0830 > attach "/bin/chmod 0666 /dev/${DEVNAME} ; /bin/ln -s > /dev/${DEVNAME} /dev/pilot" > detach "rm -f /dev/pilot > > > Having said that, it would be great to be able to create links from > devfs.rules - I'd certainly use it for my /dev/cdrom entry! > > Cheers, > /Johny From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 00:07:41 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52AEF16A420 for ; Wed, 14 Dec 2005 00:07:41 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr8.xs4all.nl (smtp-vbr8.xs4all.nl [194.109.24.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9902043D58 for ; Wed, 14 Dec 2005 00:07:40 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr8.xs4all.nl (8.13.3/8.13.3) with ESMTP id jBE07c5E034065; Wed, 14 Dec 2005 01:07:39 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 856C6B827; Wed, 14 Dec 2005 01:07:38 +0100 (CET) Date: Wed, 14 Dec 2005 01:07:38 +0100 From: Roland Smith To: "[LoN]Kamikaze" Message-ID: <20051214000738.GB30810@slackbox.xs4all.nl> Mail-Followup-To: "[LoN]Kamikaze" , freebsd-stable@freebsd.org References: <439EF8B5.4030702@gmx.de> <20051213164947.GA17705@odin.ac.hmc.edu> <20051213180418.GA20852@slackbox.xs4all.nl> <20051213192143.GA5926@odin.ac.hmc.edu> <439F24B2.1080408@gmx.de> <439F4AA4.5070500@earthmagic.org> <439F59E8.9050505@gmx.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y7xTucakfITjPcLV" Content-Disposition: inline In-Reply-To: <439F59E8.9050505@gmx.de> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 00:07:41 -0000 --Y7xTucakfITjPcLV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 14, 2005 at 12:31:52AM +0100, [LoN]Kamikaze wrote: > I agree that a more flexible approach is generally better, but since > it's not necessary I don't want to create an extra entry in my > /etc/usbd.conf (one more file to worry about during mergemaster). IIRC, usbd is/will be deprecated in favor of devd. =20 > Thus I think the best solution would be to dump devfs.conf and > /etc/rc.d/devfs entirely (or leave it optional for backwards > compatibility) and give devfs the ability to create links. Yeah, I agree that would be best. I'd be willing to look into that, but not before mid-januari. > I have a dislike for inconsistent solutions and I think most people here > share this dislike. It's just what happens when software grows. Sooner > or later you get to the point where you should throw away 80% of what's > there and turn the rest into something that does what needs to be done. Well, an adequate solution now always beats a perfect solution later. :-) =20 Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --Y7xTucakfITjPcLV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDn2JKEnfvsMMhpyURAvwuAJ963W7Rl8cX81ia1PcNTsPuDFFINgCdF4Uz d9gPvGxp7giIzrdj3cs4YUM= =Zwgd -----END PGP SIGNATURE----- --Y7xTucakfITjPcLV-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 00:54:52 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9A9016A41F for ; Wed, 14 Dec 2005 00:54:52 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE4FD43D5A for ; Wed, 14 Dec 2005 00:54:51 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.4) with ESMTP id jBE0vS6F080994 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 13 Dec 2005 19:57:34 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-stable@freebsd.org Date: Tue, 13 Dec 2005 19:56:43 -0500 User-Agent: KMail/1.8.3 References: <439EF8B5.4030702@gmx.de> <439F24B2.1080408@gmx.de> <439F4AA4.5070500@earthmagic.org> In-Reply-To: <439F4AA4.5070500@earthmagic.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4031399.fXJWB8Hav3"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512131956.51785.mistry.7@osu.edu> X-Spam-Status: No, score=-4.9 required=5.0 tests=ALL_TRUSTED,BAYES_20, J_CHICKENPOX_55,MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.87/1209/Mon Dec 12 10:48:01 2005 on mail.united-ware.com X-Virus-Status: Clean Cc: "\[LoN\]Kamikaze" , Johny Mattsson Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 00:54:52 -0000 --nextPart4031399.fXJWB8Hav3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 13 December 2005 05:26 pm, Johny Mattsson wrote: > On 12/14/05 06:44, [LoN]Kamikaze wrote: > > 3) > > There is one kind of thing I cannot do in /etc/devfs.rules, > > creating links. So I am still doing this in /etc/devfs.conf > > (links don't cause race conditions anyway, I hope). > > > > One would think that "link ttyU0 pilot" would simply be > > translated to "ln -s /dev/ttyU0 /dev/pilot" which would simply > > create the link and it would work as soon as a ttyU0 device (my > > PDA) is there. But instead it checks weather the device exists > > (of course it doesn't since I didn't press the hotsync button > > during boot) and omits the creation of the link. > > Note that while for you it might be sufficient to have a hard coded > link from /dev/pilot to /dev/ttyU0, that is not necessarily the > case if you have multiple USB serial gadgets. > The way I handled it is by using an entry in /etc/usbd.conf: > > # > # Fixup permissions for Palm Handheld ucom devices > # (set here and not in devfs.rules since we only want to apply > # the change to Palm com ports, not all USB com ports) > device "PalmHandheld" > devname "ucom[0-9]+" > vendor 0x0830 > attach "/bin/chmod 0666 /dev/${DEVNAME} ; /bin/ln -s > /dev/${DEVNAME} /dev/pilot" > detach "rm -f /dev/pilot > Roland already mentioned this point, but usbd and usbd.conf have been=20 depreciated since 5.x. They WILL be going away in CURRENT (usbd.conf=20 no longer has any entries) once Ian gets a chance to review and=20 commit the patches. If you are in need of the release field for usb=20 devices on 5.x or 6.x check out: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D73799 =2D-=20 Anish Mistry --nextPart4031399.fXJWB8Hav3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDn23TxqA5ziudZT0RAsGvAJ9wVDJUvJmjZgND/ciCqXo+A8xVcgCgvSDt iZheel+/dZY14bnryetWI1s= =U2+f -----END PGP SIGNATURE----- --nextPart4031399.fXJWB8Hav3-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 05:55:38 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CC9816A41F for ; Wed, 14 Dec 2005 05:55:38 +0000 (GMT) (envelope-from bozden@ttnet.net.tr) Received: from fep04.ttnet.net.tr (mail.ttnet.net.tr [212.175.13.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70FB643D66 for ; Wed, 14 Dec 2005 05:55:37 +0000 (GMT) (envelope-from bozden@ttnet.net.tr) Received: from ttnet.net.tr ([85.102.188.68]) by fep04.ttnet.net.tr with ESMTP id <20051214055302.EUWB1378.fep04.ttnet.net.tr@ttnet.net.tr> for ; Wed, 14 Dec 2005 07:53:02 +0200 Message-ID: <197360-220051231455527389@ttnet.net.tr> From: bozden@ttnet.net.tr To: "q" Date: Wed, 14 Dec 2005 07:55:27 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-NAI-Spam-Rules: 0 Rules triggered Subject: q X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 05:55:38 -0000 q From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 07:15:43 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C10716A41F for ; Wed, 14 Dec 2005 07:15:43 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail20.syd.optusnet.com.au (mail20.syd.optusnet.com.au [211.29.132.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A57F43D5A for ; Wed, 14 Dec 2005 07:15:42 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail20.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBE7Fdbj017011 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 14 Dec 2005 18:15:40 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBDIRhHh078781; Wed, 14 Dec 2005 05:27:43 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBDIRgFo078780; Wed, 14 Dec 2005 05:27:42 +1100 (EST) (envelope-from pjeremy) Date: Wed, 14 Dec 2005 05:27:42 +1100 From: Peter Jeremy To: fredthetree Message-ID: <20051213182742.GG77268@cirb503493.alcatel.com.au> References: <439DE88B.1090407@asd.aplus.net> <439E0B23.3060304@asd.aplus.net> <20051213025028.GC77268@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 07:15:43 -0000 On Tue, 2005-Dec-13 13:43:13 -0400, fredthetree wrote: >[/var/crash/vmcore.1] >---------------------------------- >Unread portion of the kernel message buffer: > > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x10 That's a NULL pointer de-reference - it Shouldn't Happen(TM). Can you get a backtrace from kgdb ("where")? >[vmcore.0] >---------------------------------- >Unread portion of the kernel message buffer: >ĂwÄ0żÁ0ÂÁ"ŔíÁŔJđÂÄüÂ3ÄÓÂŔíÁŔóÂDţÁŔóÂđCÂŔíÁ1Ä >ĂđÚĂŔíÁ´ÂÄBđ°ÄÁŔíÁ"ÁDHđÂŔÄÁŔíÁŔÄÄšÂĐÄÁŔíÁ@ţÁj.Ă@ >---------------------------------- The most likely problem is that your vmcore file doesn't match your kernel. Are you running kgdb with the same kernel as was running when the system crashed? (If you don't have that kernel handy, you might as well delete vmcore.0). -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 08:32:11 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F013C16A41F for ; Wed, 14 Dec 2005 08:32:11 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0871943D55 for ; Wed, 14 Dec 2005 08:32:10 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ozohwn@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBE8W8vN061842 for ; Wed, 14 Dec 2005 09:32:09 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBE8W8sZ061841; Wed, 14 Dec 2005 09:32:08 +0100 (CET) (envelope-from olli) Date: Wed, 14 Dec 2005 09:32:08 +0100 (CET) Message-Id: <200512140832.jBE8W8sZ061841@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: mountd fails intermittently X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 08:32:12 -0000 Michael Sperber wrote: > I'm running 5.4-STABLE (about two weeks old), and have just set up an > NFS server for the first time. Remote mounts sometimes work fine, and > sometimes fail. > > The symptoms are that "showmount -e" sez > > showmount: can't do exports rpc > > and that "rpcinfo -u mountd" often works fine n times in a row, > and then stops working, like so: > > ... > Michael-Sperbers-Computer[105] rpcinfo -u matt mountd > program 100005 version 1 ready and waiting > rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 > program 100005 version 2 is not available > program 100005 version 3 ready and waiting > Michael-Sperbers-Computer[106] rpcinfo -u matt mountd > program 100005 version 1 ready and waiting > rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 > program 100005 version 2 is not available > program 100005 version 3 ready and waiting > Michael-Sperbers-Computer[107] rpcinfo -u matt mountd > program 100005 version 1 ready and waiting > rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 > program 100005 version 2 is not available > program 100005 version 3 ready and waiting > Michael-Sperbers-Computer[108] rpcinfo -u matt mountd > program 100005 version 1 ready and waiting > rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 > program 100005 version 2 is not available > program 100005 version 3 ready and waiting > Michael-Sperbers-Computer[109] rpcinfo -u matt mountd > rpcinfo: RPC: Timed out > program 100005 version 0 is not available > > From then on, it'll keep failing. That looks like your rpcbind(8) process died. Can you check that with ps? Also, are there any warnings or errors reported in /var/log/messages? Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Python is an experiment in how much freedom programmers need. Too much freedom and nobody can read another's code; too little and expressiveness is endangered." -- Guido van Rossum From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 09:11:49 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C47B16A41F for ; Wed, 14 Dec 2005 09:11:49 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 0836F43D67 for ; Wed, 14 Dec 2005 09:11:46 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 14 Dec 2005 09:11:44 -0000 Received: from p54A7DBAF.dip.t-dialin.net (EHLO [192.168.0.211]) [84.167.219.175] by mail.gmx.net (mp034) with SMTP; 14 Dec 2005 10:11:44 +0100 X-Authenticated: #5465401 Message-ID: <439FE1C0.3050807@gmx.de> Date: Wed, 14 Dec 2005 10:11:28 +0100 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: how to reach a developer X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 09:11:49 -0000 Because of the devfs discussion I had a look into sys/fs/devfs/devfs_rules.c . Somewhere in the sourcecode he/she's asking a question and I would like to answer it. There just is no email address provided. The question is as follows: /* * XXX: Does it matter whether we do * * foreach(dk in ds) * foreach(de in dm) * apply(dk to de) * * as opposed to * * foreach(de in dm) * foreach(dk in ds) * apply(dk to de) * * The end result is obviously the same, but does the order * matter? */ Supposing that there is only read access to dk and only de is manipulated by the operation apply(dk to de); I have to say that the second example is a lot more efficient, because the first one causes lots of unnecessary cache to memory writebacks. Which would be gracefuly avoided by the second one. - Dominic From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 10:29:29 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB05616A41F for ; Wed, 14 Dec 2005 10:29:29 +0000 (GMT) (envelope-from pherman@frenchfries.net) Received: from alcatraz.frenchfries.net (216-73-106-93.ocdc-01.net [216.73.106.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6DB243D45 for ; Wed, 14 Dec 2005 10:29:29 +0000 (GMT) (envelope-from pherman@frenchfries.net) Received: from localhost (alcatraz [216.73.106.93]) by alcatraz.frenchfries.net (Postfix) with ESMTP id CD875C6420 for ; Wed, 14 Dec 2005 02:29:28 -0800 (PST) Date: Wed, 14 Dec 2005 11:29:27 +0100 (CET) From: Paul Herman X-X-Sender: pherman@tahoe.cgn.cleverbridge.com To: FreeBSD Stable In-Reply-To: <20051212110259.6D0B3C6481@alcatraz.frenchfries.net> References: <20051212110259.6D0B3C6481@alcatraz.frenchfries.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Message-Id: <20051214102928.CD875C6420@alcatraz.frenchfries.net> Subject: Re: 6.0-STABLE setkey panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 10:29:30 -0000 On Mon, 12 Dec 2005, Paul Herman wrote: > Just installed 6.0-STABLE/amd64 (cvsup from within the last day) onto a K8 > Sempron with IPSEC compiled in and I get a kernel panic when I try to run > racoon. Anyone else seen this? (Replying to myself...) Just saw this is PR 89261. Sorry for the redundancy. -Paul. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 11:03:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D75116A41F for ; Wed, 14 Dec 2005 11:03:22 +0000 (GMT) (envelope-from ob@gruft.de) Received: from obh.snafu.de (obh.snafu.de [213.73.92.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A47743D45 for ; Wed, 14 Dec 2005 11:03:21 +0000 (GMT) (envelope-from ob@gruft.de) Received: from ob by obh.snafu.de with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EmUPp-0000om-3Q for freebsd-stable@freebsd.org; Wed, 14 Dec 2005 12:03:21 +0100 Date: Wed, 14 Dec 2005 12:03:21 +0100 From: Oliver Brandmueller To: freebsd-stable@freebsd.org Message-ID: <20051214110321.GC34429@e-Gitt.NET> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Sender: Oliver Brandmueller Subject: NFS locking problem with RELENG_6 client on RELENG_5 server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 11:03:22 -0000 Hi, I have a setup with an 5.4-STABLE (July, 10th 2005) NFS server and about 10 FreeBSD clients. Most of the clients are still running on RELENG_5, but I recently started updating to RELENG_6. Shortly after updating the first client I ran into a problem with a spinning rpc.lockd on the NFS servers. While rpc.lockd in normal circumstances runs at about 0.1% to 0.7% CPU it the starts using more and more CPU (about 1% more CPU per minute in my setup, when it's using about 20 to 25 percent I get problems with locking). If I restart rpc.lockd on the server it starts spinning again immediately. If I restart rpc.lockd on the RELENG_6 client everything is fine again for some time. I cannot reproduce the behaviour by certain actions, it seems to be related to load. We have to weekdays, where workload is high and filesystem load on the NFS server is also high due to long running backup processes. I only saw the lockd problem on these days ("load" means about 60 MBit/s Traffic from the NFS clients to the server, about 30 MBit/s for the backup [which is writing with dump to a NFS mounted partition]). I looked through the sources and updated my RELENG_6 clients with downgraded versions of: src/sys/nfsclient/nfs_lock.c (1.40 now instead of 1.40.2.1) src/sys/nfsclient/nlminfo.h (1.2 now instead of 1.2.14.1) src/sys/sys/lockf.h (1.18 now instead of 1.18.2.1) since these seem to be the changes from RELENG_5 on the NFS clients that make a difference for the locking. We had the problem about once or twice a week. Now everything is fine for about one week (the second "high load" day is today). I'm not a programmer and especially I can only do very limited debugging on the prod systems (and I did not manage to produce the load in NFS and locking on our test systems). This means: I cannot be sure 100% that this commit is the root of the problem, but I have enough evidence to believe so. If someones willing and interested in debugging, I have (from the NFS server) a few minutes of debugging output after a restart from rpc.lockd - since it is long and I don't know for what to look exactly it's not attached, but I can grep (or even make it available) if it's of any help. I don't have debugging output of the NFS client rpc.lockd, though, because I cannot let it run with debugging on all the time and restarting the client fixed the problem :-/ Thanx, Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 11:15:12 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E56A816A41F for ; Wed, 14 Dec 2005 11:15:12 +0000 (GMT) (envelope-from barner@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 87F4D43D64 for ; Wed, 14 Dec 2005 11:15:08 +0000 (GMT) (envelope-from barner@gmx.de) Received: (qmail invoked by alias); 14 Dec 2005 11:15:04 -0000 Received: from unknown (EHLO zi025.glh.mhn.de) [129.187.43.241] by mail.gmx.net (mp002) with SMTP; 14 Dec 2005 12:15:04 +0100 X-Authenticated: #147403 Received: by zi025.glh.mhn.de (Postfix, from userid 1000) id 203C9C182; Wed, 14 Dec 2005 12:15:06 +0100 (CET) Date: Wed, 14 Dec 2005 12:15:06 +0100 From: Simon Barner To: "[LoN]Kamikaze" Message-ID: <20051214111505.GC20777@zi025.glh.mhn.de> References: <439FE1C0.3050807@gmx.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LwW0XdcUbUexiWVK" Content-Disposition: inline In-Reply-To: <439FE1C0.3050807@gmx.de> User-Agent: Mutt/1.5.11 X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org Subject: Re: how to reach a developer X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 11:15:13 -0000 --LwW0XdcUbUexiWVK Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [LoN]Kamikaze wrote: > Because of the devfs discussion I had a look into > sys/fs/devfs/devfs_rules.c . ^ without 's' >=20 > Somewhere in the sourcecode he/she's asking a question and I would like > to answer it. There just is no email address provided. [...] You can use the annotate/blame function of CVS: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/fs/devfs/devfs_rule.c?annotat= e=3D1.14.2.2 shows, that this part of the file has been committed by dd@ back in July 2002. --=20 Best regards / Viele Gr=FC=DFe, barner@FreeBSD.= org Simon Barner barner@gmx.de --LwW0XdcUbUexiWVK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDn/65Ckn+/eutqCoRAkZJAKDb4xrQAZhitmxUUAImZkCb88tOmQCfd3nw PLYTR+iABNBE6bUCd8oo3t8= =CI58 -----END PGP SIGNATURE----- --LwW0XdcUbUexiWVK-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 12:12:16 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4856616A41F for ; Wed, 14 Dec 2005 12:12:16 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8712743D5D for ; Wed, 14 Dec 2005 12:12:15 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002118766.msg for ; Wed, 14 Dec 2005 12:12:07 +0000 Message-ID: <00e001c600a7$99ec81b0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: Date: Wed, 14 Dec 2005 12:12:02 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Processed: multiplay.co.uk, Wed, 14 Dec 2005 12:12:07 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: multiplay.co.uk, Wed, 14 Dec 2005 12:12:08 +0000 Subject: Problems with ata RAID? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 12:12:16 -0000 Just spotted the following in the logs of one of our machines There seems to errors across too many disks for it to be disk issues. Any one seen this before / got any advice? ad4: timeout waiting to issue command ad4: error issueing WRITE_DMA command ar0: WARNING - mirror protection lost. RAID0+1 array in DEGRADED mode ad4: timeout waiting to issue command ad4: error issueing WRITE_DMA command ad4: write metadata failed ad6: req=0xc49b0578 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2325663 ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2325695 ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2325695 ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2325727 ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2325632 ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=393344 ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=393344 ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=393344 ad5: FAILURE - WRITE_DMA status=51 error=84 LBA=393344 ad4: req=0xc8585258 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! ad4: req=0xc8585258 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! ad4: req=0xc8585258 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! ad4: req=0xc8585258 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! ad5: FAILURE - SETFEATURES SET TRANSFER MODE status=51 error=4 ad5: FAILURE - SETFEATURES SET TRANSFER MODE status=51 error=4 ad5: FAILURE - SETFEATURES ENABLE RCACHE status=51 error=4 ad5: FAILURE - SETFEATURES ENABLE WCACHE status=51 error=4 ad5: FAILURE - SET_MULTI status=51 error=4 ad4: FAILURE - WRITE_DMA timed out LBA=234441585 ad4: write metadata failed ad5: FAILURE - WRITE_DMA status=59 error=4 dma=0x06 LBA=234441585 ad5: write metadata failed ad6: req=0xc853c190 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! [dmesg] atapci0: port 0xa400-0xa407,0xa800-0xa803,0xac00-0xac07,0xb000-0xb003,0xb400-0xb43f mem 0xf8120000-0xf813ffff irq 18 at device 12.0 on pci0 ata2: on atapci0 ata3: on atapci0 ad4: 114473MB at ata2-master UDMA100 ad5: 114473MB at ata2-slave UDMA100 ad6: 114473MB at ata3-master UDMA100 ad7: 114473MB at ata3-slave UDMA100 ar0: 228946MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (master) using ad5 at ata2-slave ar0: disk2 READY (mirror) using ad6 at ata3-master ar0: disk3 READY (mirror) using ad7 at ata3-slave [/dmesg] ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 12:26:52 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C848116A41F for ; Wed, 14 Dec 2005 12:26:52 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30EDC43D4C for ; Wed, 14 Dec 2005 12:26:51 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002118795.msg for ; Wed, 14 Dec 2005 12:26:45 +0000 Message-ID: <00ef01c600a9$a6c79ad0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: References: <00e001c600a7$99ec81b0$b3db87d4@multiplay.co.uk> Date: Wed, 14 Dec 2005 12:26:42 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Processed: multiplay.co.uk, Wed, 14 Dec 2005 12:26:45 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: multiplay.co.uk, Wed, 14 Dec 2005 12:26:46 +0000 Subject: Re: Problems with ata RAID? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 12:26:52 -0000 Opps forgot to say running 6.0-RELEASE. Steve ----- Original Message ----- From: "Steven Hartland" > Just spotted the following in the logs of one of our machines > There seems to errors across too many disks for it to be disk issues. > Any one seen this before / got any advice? > > ad4: timeout waiting to issue command > ad4: error issueing WRITE_DMA command > ar0: WARNING - mirror protection lost. RAID0+1 array in DEGRADED mode ... ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 12:28:24 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAEF816A41F for ; Wed, 14 Dec 2005 12:28:23 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 088A343D4C for ; Wed, 14 Dec 2005 12:28:22 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 18163 invoked from network); 14 Dec 2005 12:28:20 -0000 Received: from unknown (HELO TP51.local) ([pbs]775067@[217.187.177.99]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 14 Dec 2005 12:28:20 -0000 Date: Wed, 14 Dec 2005 13:25:30 +0100 From: Fabian Keil To: freebsd-stable@freebsd.org Message-ID: <20051214132530.3b6daecd@TP51.local> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.6; i386-portbld-freebsd5.4) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_d+Z+FPTJW7+CfAB5byqEFfU; protocol="application/pgp-signature"; micalg=PGP-SHA1 Subject: FreeBSD 6.0 panic: kmem_malloc(16384): kmem_map too small: 172728320 total allocated X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 12:28:24 -0000 --Sig_d+Z+FPTJW7+CfAB5byqEFfU Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I triggered a few reproducible panics on FreeBSD 6.0-STABLE. I created a ramdisk with: =20 /sbin/mdconfig -a -t malloc -s 256M -u 10 /sbin/newfs -U /dev/md10 /sbin/mount /dev/md10 /mnt/ramdisk The system has "avail memory =3D 515932160 (492 MB)" and 1GB swap space. While copying to /mnt/ramdisk trough ftp localhost it got: root@africanqueen ~/crashdump #kgdb kernel-GENERIC.debug vmcore.3 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:= Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] [...] Unread portion of the kernel message buffer: panic: kmem_malloc(16384): kmem_map too small: 172728320 total allocated Uptime: 2m57s Dumping 511 MB (2 chunks) chunk 0: 1MB (158 pages) ... ok chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335= 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) where #0 doadump () at pcpu.h:165 #1 0xc063a4ee in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:3= 99 #2 0xc063a784 in panic (fmt=3D0xc0880846 "kmem_malloc(%ld): kmem_map too s= mall: %ld total allocated") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc07a44bd in kmem_malloc (map=3D0xc10430c0, size=3D16384, flags=3D1026= ) at /usr/src/sys/vm/vm_kern.c:299 #4 0xc079c0c6 in page_alloc (zone=3D0x0, bytes=3D16384, pflag=3D0x0, wait= =3D1026) at /usr/src/sys/vm/uma_core.c:958 #5 0xc079e41f in uma_large_malloc (size=3D16384, wait=3D1026) at /usr/src/= sys/vm/uma_core.c:2702 #6 0xc0630085 in malloc (size=3D16384, mtp=3D0xc08ffe40, flags=3D1026) at = /usr/src/sys/kern/kern_malloc.c:329 #7 0xc078365e in softdep_disk_io_initiation (bp=3D0xcd899658) at /usr/src/= sys/ufs/ffs/ffs_softdep.c:3630 #8 0xc078b1fe in ffs_geom_strategy (bo=3D0xc3593e90, bp=3D0xcd899658) at b= uf.h:422 #9 0xc0796869 in ufs_strategy (ap=3D0x0) at /usr/src/sys/ufs/ufs/ufs_vnops= .c:1926 #10 0xc081c645 in VOP_STRATEGY_APV (vop=3D0xc09012a0, a=3D0xdd93ec0c) at vn= ode_if.c:1796 #11 0xc06841d0 in bufstrategy (bo=3D0xc35f7720, bp=3D0x0) at vnode_if.h:928 #12 0xc067eda8 in bufwrite (bp=3D0xcd899658) at buf.h:415 #13 0xc067f397 in bawrite (bp=3D0x0) at buf.h:399 #14 0xc078b53d in ffs_syncvnode (vp=3D0xc35f7660, waitfor=3D1) at /usr/src/= sys/ufs/ffs/ffs_vnops.c:256 #15 0xc078b28e in ffs_fsync (ap=3D0xdd93ecc0) at /usr/src/sys/ufs/ffs/ffs_v= nops.c:179 #16 0xc081c05c in VOP_FSYNC_APV (vop=3D0x0, a=3D0x0) at vnode_if.c:1020 #17 0xc0698278 in fsync (td=3D0xc3460d80, uap=3D0x0) at vnode_if.h:537 #18 0xc080b6eb in syscall (frame=3D {tf_fs =3D 59, tf_es =3D 59, tf_ds =3D 59, tf_edi =3D 64, tf_esi =3D = 134572032, tf_ebp =3D -1077940680, tf_isp =3D -5775079=20 96, tf_ebx =3D 134561920, tf_edx =3D 1, tf_ecx =3D 6, tf_eax =3D 95, tf_tra= pno =3D 0, tf_err =3D 2, tf_eip =3D 672366947, tf_cs =3D=20 51, tf_eflags =3D 662, tf_esp =3D -1077945572, tf_ss =3D 59}) at /usr/src/= sys/i386/i386/trap.c:981 #19 0xc07fa57f in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s= :200 #20 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) By simply copying to /mnt/ramdisk with cp I got: root@africanqueen ~/crashdump #kgdb kernel-GENERIC.debug vmcore.4 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:= Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] [...] Unread portion of the kernel message buffer: g_vfs_done():md10[WRITE(offset=3D206372864, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D206503936, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D206635008, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D206766080, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D206897152, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D207028224, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D207159296, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D207290368, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D207421440, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D207552512, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D207683584, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D207814656, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D207945728, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D208076800, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D208207872, length=3D131072)]error =3D 28 g_vfs_done():md10[WRITE(offset=3D208338944, length=3D131072)]error =3D 28 panic: kmem_malloc(4096): kmem_map too small: 172728320 total allocated Uptime: 11m23s Dumping 511 MB (2 chunks) chunk 0: 1MB (158 pages) ... ok chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335= 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h #0 doadump () at pcpu.h:165 #1 0xc063a4ee in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:3= 99 #2 0xc063a784 in panic (fmt=3D0xc0880846 "kmem_malloc(%ld): kmem_map too s= mall: %ld total allocated") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc07a44bd in kmem_malloc (map=3D0xc10430c0, size=3D4096, flags=3D1026)= at /usr/src/sys/vm/vm_kern.c:299 #4 0xc079c0c6 in page_alloc (zone=3D0xc104d800, bytes=3D4096, pflag=3D0x0,= wait=3D1026) at /usr/src/sys/vm/uma_core.c:958 #5 0xc079bbfd in slab_zalloc (zone=3D0xc104d800, wait=3D1026) at /usr/src/= sys/vm/uma_core.c:823 #6 0xc079d39c in uma_zone_slab (zone=3D0xc104d800, flags=3D1282) at /usr/s= rc/sys/vm/uma_core.c:2025 #7 0xc079d5b8 in uma_zalloc_bucket (zone=3D0xc104d800, flags=3D1282) at /u= sr/src/sys/vm/uma_core.c:2134 #8 0xc079d22d in uma_zalloc_arg (zone=3D0xc104d800, udata=3D0x0, flags=3D1= 282) at /usr/src/sys/vm/uma_core.c:1942 #9 0xc0630042 in malloc (size=3D64, mtp=3D0xc08ffec0, flags=3D1282) at uma= .h:275 #10 0xc077fff5 in newallocindir (ip=3D0xc924a6b4, ptrno=3D0, newblkno=3DUnh= andled dwarf expression opcode 0x93 ) at /usr/src/sys/ufs/ffs/ffs_softdep.c:1818 #11 0xc0780060 in softdep_setup_allocindir_page (ip=3D0xc924a6b4, lbn=3D441= 0, bp=3D0xcd82e550, ptrno=3D302,=20 newblkno=3D101840, oldblkno=3D0, nbp=3D0xcd7c4118) at /usr/src/sys/ufs/= ffs/ffs_softdep.c:1847 #12 0xc0776562 in ffs_balloc_ufs2 (vp=3D0xc37a7220, startoffset=3DUnhandled= dwarf expression opcode 0x93 ) at /usr/src/sys/ufs/ffs/ffs_balloc.c:822 #13 0xc078be30 in ffs_write (ap=3D0xdeb8fbec) at /usr/src/sys/ufs/ffs/ffs_v= nops.c:662 #14 0xc081bdbe in VOP_WRITE_APV (vop=3D0xc0900d60, a=3D0xdeb8fbec) at vnode= _if.c:698 #15 0xc069c336 in vn_write (fp=3D0xc3573a68, uio=3D0xdeb8fcbc, active_cred= =3D0xc35f7c80, flags=3D0, td=3D0xc374dc00) at vnode_if.h:372 #16 0xc065bb1b in dofilewrite (td=3D0xc374dc00, fd=3D4, fp=3D0xc3573a68, au= io=3D0xdeb8fcbc, offset=3DUnhandled dwarf expression opcode 0x93 ) at file.h:246 #17 0xc065b9bf in kern_writev (td=3D0xc374dc00, fd=3D4, auio=3D0xdeb8fcbc) = at /usr/src/sys/kern/sys_generic.c:402 #18 0xc065b8e5 in write (td=3D0xc374dc00, uap=3D0x0) at /usr/src/sys/kern/s= ys_generic.c:326 #19 0xc080b6eb in syscall (frame=3D {tf_fs =3D 59, tf_es =3D 59, tf_ds =3D 59, tf_edi =3D 134526528, tf_e= si =3D 65536, tf_ebp =3D -1077941656, tf_isp =3D -558301852, tf_ebx =3D 655= 36, tf_edx =3D 0, tf_ecx =3D 134607176, tf_eax =3D 4, tf_trapno =3D 32, tf_= err =3D 2, tf_eip =3D 672311759, tf_cs =3D 51, tf_eflags =3D 518, tf_esp = =3D -1077941732, tf_ss =3D 59}) at /usr/src/sys/i386/i386/trap.c:981 #20 0xc07fa57f in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s= :200 #21 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) For the last two panics I used GENERIC, sources are from yesterday. Fabian --=20 http://www.fabiankeil.de/ --Sig_d+Z+FPTJW7+CfAB5byqEFfU Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoA8/jV8GA4rMKUQRAshnAJ9CINROSxs/e7S44sJsx/ARr+a+2ACfZTm5 t8ChCwSxNPuYmE+EMKn6+jA= =dwnD -----END PGP SIGNATURE----- --Sig_d+Z+FPTJW7+CfAB5byqEFfU-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 12:28:28 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CD4416A41F for ; Wed, 14 Dec 2005 12:28:28 +0000 (GMT) (envelope-from fredthetree@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F54A43D62 for ; Wed, 14 Dec 2005 12:28:26 +0000 (GMT) (envelope-from fredthetree@gmail.com) Received: by wproxy.gmail.com with SMTP id i5so384718wra for ; Wed, 14 Dec 2005 04:28:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=fwKb/Hc+v7IT3ydk1GxxuEL6R5mDxzQsJ9QjEslVxomPofJ+7wXRSYeaaTaCCeiZjfwWL9O5eOjqjZtDPN7j0LRyHRGkeLLM1rfxN/hnmF3twn/R8QcnG83ujmIm2M/j5sEh8tw+/gcvykYkq81pXMeUV4acAe6DGokkAlJr/To= Received: by 10.54.151.9 with SMTP id y9mr612045wrd; Wed, 14 Dec 2005 04:28:26 -0800 (PST) Received: by 10.54.146.19 with HTTP; Wed, 14 Dec 2005 04:28:26 -0800 (PST) Message-ID: Date: Wed, 14 Dec 2005 08:28:26 -0400 From: fredthetree To: Peter Jeremy , freebsd-stable@freebsd.org In-Reply-To: <20051213182742.GG77268@cirb503493.alcatel.com.au> MIME-Version: 1.0 References: <439DE88B.1090407@asd.aplus.net> <439E0B23.3060304@asd.aplus.net> <20051213025028.GC77268@cirb503493.alcatel.com.au> <20051213182742.GG77268@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 12:28:28 -0000 i've only used the generic 6.0 kernel # kgdb kernel.debug /var/crash/vmcore.1 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you ar= e welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x10 fault code =3D supervisor read, page not present instruction pointer =3D 0x20:0xc0a7cf08 stack pointer =3D 0x28:0xd56a694c frame pointer =3D 0x28:0x0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 29 (swi1: net) trap number =3D 12 panic: page fault Uptime: 1d23h40m51s Dumping 511 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) where #0 doadump () at pcpu.h:165 #1 0xc0638202 in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:3= 99 #2 0xc0638498 in panic (fmt=3D0xc084e5a2 "%s") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc0807c30 in trap_fatal (frame=3D0xd56a690c, eva=3D16) at /usr/src/sys/i386/i386/trap.c:831 #4 0xc080799b in trap_pfault (frame=3D0xd56a690c, usermode=3D0, eva=3D16) at /usr/src/sys/i386/i386/trap.c:742 #5 0xc08075d9 in trap (frame=3D {tf_fs =3D -1038680056, tf_es =3D 40, tf_ds =3D 40, tf_edi =3D 0, tf_= esi =3D -646886620, tf_ebp =3D 0, tf_isp =3D -714446536, tf_ebx =3D -646862464, tf_= edx =3D 791735, tf_ecx =3D -1073475471, tf_eax =3D 1, tf_trapno =3D 12, tf_err =3D = 0, tf_eip =3D -1062744312, tf_cs =3D 32, tf_eflags =3D 66050, tf_esp =3D 16798208, tf= _ss =3D 0}) at /usr/src/sys/i386/i386/trap.c:432 #6 0xc07f6dca in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc0a7cf08 in ?? () On 12/13/05, Peter Jeremy wrote: > > On Tue, 2005-Dec-13 13:43:13 -0400, fredthetree wrote: > >[/var/crash/vmcore.1] > >---------------------------------- > >Unread portion of the kernel message buffer: > > > > > >Fatal trap 12: page fault while in kernel mode > >fault virtual address =3D 0x10 > > That's a NULL pointer de-reference - it Shouldn't Happen(TM). Can you > get a backtrace from kgdb ("where")? > > >[vmcore.0] > >---------------------------------- > >Unread portion of the kernel message buffer: > >=C3w=C40=BF=C10=C2=C1"=C0=ED=C1=C0J=F0=C2=C4=FC=C23=C4=D3=C2=C0=ED=C1=C0= =F3=C2D=FE=C1=C0=F3=C2=F0C=C2=C0=ED=C11=C4 > >=C3=F0=DA=C3=C0=ED=C1=B4=C2=C4B=F0=C2=B0=C4=C1=C0=ED=C1"=C1DH=F0=C2=C0= =C4=C1=C0=ED=C1=C0=C4=C4=B9=C2=D0=C4=C1=C0=ED=C1@=FE=C1j.=C3@ > >---------------------------------- > > The most likely problem is that your vmcore file doesn't match your > kernel. > Are you running kgdb with the same kernel as was running when the system > crashed? (If you don't have that kernel handy, you might as well delete > vmcore.0). > > -- > Peter Jeremy > From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 13:13:53 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2E7D16A41F for ; Wed, 14 Dec 2005 13:13:53 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from anduin.net (mail.anduin.net [213.225.74.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BB6F43D55 for ; Wed, 14 Dec 2005 13:13:53 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from [10.1.3.26] (helo=[10.1.3.26]) by anduin.net with esmtpa (Exim 4.54 (FreeBSD)) id 1El0yp-0006fE-So; Sat, 10 Dec 2005 10:25:23 +0100 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: =?ISO-8859-1?Q?Eirik_=D8verby?= Date: Sat, 10 Dec 2005 10:25:23 +0100 To: Joshua Coombs X-Mailer: Apple Mail (2.746.2) Cc: freebsd-stable@freebsd.org Subject: Re: ZERO_COPY_SOCKETS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 13:13:53 -0000 On Dec 6, 2005, at 03:20 , Joshua Coombs wrote: > #options ZERO_COPY_SOCKETS > > What's the status of this in 6.0-R and 6-stable? The idea of > avoiding memory copies when possible seems really appealing for my > 386, on which any little boost is significant. : ) Hoi, let me know how you got 6.0 running on i386 .. It sounds like the perfect way to spend some of the holidays ;) I've heard it won't run on a plain i386 out-of-the-box, what did you do to convince it to run? /Eirik > > Joshua Coombs > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscribe@freebsd.org" > > > From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 13:19:01 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E33C916A41F for ; Wed, 14 Dec 2005 13:19:01 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 297C843D46 for ; Wed, 14 Dec 2005 13:19:00 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jBEDItKq076391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Dec 2005 16:18:55 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jBEDItso076390; Wed, 14 Dec 2005 16:18:55 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 14 Dec 2005 16:18:55 +0300 From: Gleb Smirnoff To: Fabian Keil Message-ID: <20051214131855.GH59644@FreeBSD.org> References: <20051214132530.3b6daecd@TP51.local> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20051214132530.3b6daecd@TP51.local> User-Agent: Mutt/1.5.6i Cc: freebsd-stable@FreeBSD.org Subject: Re: FreeBSD 6.0 panic: kmem_malloc(16384): kmem_map too small: 172728320 total allocated X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 13:19:02 -0000 On Wed, Dec 14, 2005 at 01:25:30PM +0100, Fabian Keil wrote: F> I triggered a few reproducible panics on FreeBSD 6.0-STABLE. F> F> I created a ramdisk with: F> F> /sbin/mdconfig -a -t malloc -s 256M -u 10 F> /sbin/newfs -U /dev/md10 F> /sbin/mount /dev/md10 /mnt/ramdisk F> F> The system has "avail memory = 515932160 (492 MB)" F> and 1GB swap space. F> F> While copying to /mnt/ramdisk trough ftp localhost F> it got: This usually exposes some memory leak in kernel. Can you please do the following - copy some amount of data to /mnt/ramdisk trough ftp localhost, and cancel the operation before it panics. Then run vmstat -m and vmstat -z, to determine what kind of memory allocation is leaking. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 14:23:11 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D01BD16A41F for ; Wed, 14 Dec 2005 14:23:11 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CE1443D62 for ; Wed, 14 Dec 2005 14:23:09 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 5755 invoked from network); 14 Dec 2005 14:23:07 -0000 Received: from unknown (HELO TP51.local) ([pbs]775067@[217.187.177.99]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 14 Dec 2005 14:23:07 -0000 Date: Wed, 14 Dec 2005 15:22:42 +0100 From: Fabian Keil To: Gleb Smirnoff Message-ID: <20051214152242.430b2d94@TP51.local> In-Reply-To: <20051214131855.GH59644@FreeBSD.org> References: <20051214132530.3b6daecd@TP51.local> <20051214131855.GH59644@FreeBSD.org> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.6; i386-portbld-freebsd5.4) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_ewVYPuwn69neDc7MBZnMEla; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-stable@FreeBSD.org Subject: Re: FreeBSD 6.0 panic: kmem_malloc(16384): kmem_map too small: 172728320 total allocated X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 14:23:12 -0000 --Sig_ewVYPuwn69neDc7MBZnMEla Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Gleb Smirnoff wrote: > On Wed, Dec 14, 2005 at 01:25:30PM +0100, Fabian Keil wrote: > F> I triggered a few reproducible panics on FreeBSD 6.0-STABLE. > F>=20 > F> I created a ramdisk with: > F> =20 > F> /sbin/mdconfig -a -t malloc -s 256M -u 10 > F> /sbin/newfs -U /dev/md10 > F> /sbin/mount /dev/md10 /mnt/ramdisk > F>=20 > F> The system has "avail memory =3D 515932160 (492 MB)" > F> and 1GB swap space. > F>=20 > F> While copying to /mnt/ramdisk trough ftp localhost > F> it got: >=20 > This usually exposes some memory leak in kernel. Can you please do the > following - copy some amount of data to /mnt/ramdisk trough ftp > localhost, and cancel the operation before it panics. >=20 > Then run vmstat -m and vmstat -z, to determine what kind of memory > allocation is leaking. I had loops with vmstat -m and vmstat -z in the background while copying to /mnt/ramdisk. The last output before the panic was: Type InUse MemUse HighUse Requests Size(s) DEVFS 22 1K - 23 16,128 pfs_nodes 20 3K - 20 128 GEOM 189 26K - 858 16,32,64,128,256,512,1024,2048,4096 isadev 17 2K - 17 64 ATA DMA 4 1K - 4 128 cdev 27 4K - 27 128 AR driver 0 0K - 11 512,2048 ACD driver 3 6K - 3 2048 file desc 120 46K - 1611 16,32,256,512,2048 sigio 2 1K - 3 32 kenv 96 7K - 97 16,32,64,4096 kqueue 0 0K - 62 256,1024 proc-args 43 2K - 797 16,32,64,128 zombie 0 0K - 907 128 ithread 48 5K - 49 64,128 KTRACE 100 13K - 100 128 CAM SIM 1 1K - 1 64 linker 68 3K - 99 16,32,256 CAM XPT 10 1K - 17 16,64,512 lockf 3 1K - 3 64 devbuf 1346 3177K - 1816 16,32,64,128,256,512,1024,2048,4096 temp 16 171K - 6266 16,32,64,128,256,512,1024,2048,4096 ip6opt 1 1K - 1 128 ip6ndp 6 1K - 7 64,128 module 371 24K - 371 64,128 mtx_pool 1 8K - 1 =20 pgrp 36 3K - 623 64 session 29 4K - 47 128 proc 2 4K - 2 2048 subproc 209 413K - 1116 256,4096 cred 35 5K - 4132 128 plimit 18 5K - 400 256 uidinfo 4 1K - 20 32,512 sysctl 0 0K - 619 16,32,64 sysctloid 2567 77K - 2567 16,32,64 sysctltmp 0 0K - 280 16,32,128 umtx 120 8K - 120 64 SWAP 2 141K - 2 64 bus 959 38K - 3599 16,32,64,128,1024 bus-sc 57 27K - 1537 16,32,64,128,256,512,1024,2048,4096 devstat 18 37K - 18 16,4096 eventhandler 37 3K - 37 32,128 kobj 248 496K - 299 2048 MD disk 294 7K - 294 16,2048 MD sectors 293 1172K - 293 4096 rman 149 10K - 570 16,64 sbuf 0 0K - 440 16,32,64,128,256,512,1024,2048,4096 sleep queues 121 4K - 121 32 taskqueue 6 1K - 6 128 turnstiles 121 8K - 121 64 Unitno 7 1K - 9 16,64 ioctlops 0 0K - 2757 16,32,64,256,512,1024,4096 iov 0 0K - 487 16,64,128 msg 4 25K - 4 1024,4096 sem 4 7K - 4 512,1024,4096 shm 1 12K - 1 =20 ttys 1228 174K - 3223 128,1024 ptys 3 1K - 3 128 mbuf_tag 0 0K - 6 32,64 soname 6 1K - 735 16,32,128 pcb 29 5K - 81 16,32,64,2048 BIO buffer 0 0K - 99 2048 vfscache 1 256K - 1 =20 cluster_save buffer 0 0K - 19 32,64 Export Host 1 1K - 2 256 VFS hash 1 128K - 1 =20 vnodes 1 1K - 1 128 mount 130 12K - 641 16,32,64,128,512,1024,2048 CAM periph 1 1K - 1 128 BPF 4 1K - 4 64 ifnet 5 5K - 5 256,1024 ifaddr 40 10K - 40 16,32,64,256,512,2048 ether_multi 40 2K - 46 16,32,64 clone 4 16K - 4 4096 arpcom 2 1K - 2 16 lo 1 1K - 1 16 ATA generic 5 5K - 22 16,512,1024 CAM queue 3 1K - 3 16 CAM dev queue 1 1K - 1 64 routetbl 30 3K - 62 16,32,64,128,256 in_multi 2 1K - 2 32 hostcache 1 24K - 1 =20 syncache 1 8K - 1 =20 in6_multi 12 1K - 12 16,64 ip6_moptions 1 1K - 1 16 NFS srvsock 2 1K - 2 128 NFS daemon 5 3K - 5 256,512 agp 2 257K - 2 16 p1003.1b 1 1K - 1 16 pagedep 2 17K - 32 64 inodedep 11 130K - 116 128 newblk 1 1K - 15816 64,256 bmsafemap 3 1K - 76 32 allocdirect 14 2K - 573 128 indirdep 3 1K - 311 32 allocindir 3333 209K - 15242 64 freefrag 0 0K - 91 32 freeblks 2 1K - 32 256 freefile 1 1K - 36 32 diradd 1 1K - 78 32 mkdir 0 0K - 12 32 dirrem 0 0K - 68 32 savedino 0 0K - 34 256 UFS dirhash 48 9K - 48 16,32,512 UFS mount 18 38K - 30 64,256,512,1024,2048,4096 UMAHash 2 257K - 13 256,512,1024,2048,4096 AD driver 2 1K - 2 32 ppbusdev 3 1K - 3 128 entropy 1024 64K - 1024 64 VM pgdata 2 33K - 2 64 atkbddev 2 1K - 2 32 USB 31 3K - 31 16,32,64,128,256 USBdev 2 1K - 8 128,512 DEVFS2 105 2K - 105 16 memdesc 1 4K - 1 4096 nexusdev 3 1K - 3 16 DEVFS3 237 30K - 238 128 DEVFS1 112 28K - 112 256 DEVFS_RULE 34 8K - 34 32,256 linux 10 1K - 10 32 acpica 1507 84K - 19881 16,32,64,128,256,512,1024,2048 acpitask 0 0K - 2 32 acpidev 41 2K - 41 32 acpisem 18 2K - 18 64 PCI Link 8 1K - 8 64,128 ITEM SIZE LIMIT USED FREE REQUESTS UMA Kegs: 140, 0, 63, 9, 63 UMA Zones: 120, 0, 63, 27, 63 UMA Slabs: 64, 0, 37254, 34, 38294 UMA RCntSlabs: 104, 0, 67, 7, 67 UMA Hash: 128, 0, 2, 28, 4 16 Bucket: 76, 0, 24, 26, 28 32 Bucket: 140, 0, 20, 8, 25 64 Bucket: 268, 0, 22, 6, 29 128 Bucket: 524, 0, 67, 3, 70 VM OBJECT: 132, 0, 1518, 135, 20178 MAP: 192, 0, 7, 33, 7 KMAP ENTRY: 68, 31976, 15, 153, 41589 MAP ENTRY: 68, 0, 1265, 191, 59199 PV ENTRY: 24, 933800, 12742, 2193, 513804 DP fakepg: 72, 0, 0, 0, 0 mt_zone: 64, 0, 195, 100, 195 16: 16, 0, 2869, 176, 24798 32: 32, 0, 1998, 149, 4847 64: 64, 0, 3973, 3461, 38988 128: 128, 0, 1994, 106, 12191 256: 256, 0, 425, 25, 2784 512: 512, 0, 51, 5, 301 1024: 1024, 0, 61, 71, 1511 2048: 2048, 0, 283, 57, 862 4096: 4096, 0, 442, 13, 5057 Files: 72, 0, 114, 98, 5926 PROC: 524, 0, 95, 17, 1004 THREAD: 372, 0, 112, 8, 112 KSEGRP: 88, 0, 112, 48, 112 UPCALL: 44, 0, 0, 0, 0 VMSPACE: 300, 0, 43, 22, 952 mbuf_packet: 256, 0, 21, 107, 118780 mbuf: 256, 0, 1, 141, 160524 mbuf_cluster: 2048, 17088, 128, 6, 128 ACL UMA zone: 388, 0, 0, 0, 0 g_bio: 132, 0, 0, 348, 162122 ata_request: 200, 0, 0, 95, 40954 ata_composite: 192, 0, 0, 0, 0 VNODE: 272, 0, 792, 20, 830 VNODEPOLL: 76, 0, 0, 0, 0 S VFS Cache: 68, 0, 758, 82, 1542 L VFS Cache: 291, 0, 0, 0, 0 NAMEI: 1024, 0, 3, 9, 17240 DIRHASH: 1024, 0, 47, 9, 47 NFSMOUNT: 480, 0, 0, 0, 0 NFSNODE: 460, 0, 0, 0, 0 PIPE: 408, 0, 4, 14, 216 KNOTE: 68, 0, 0, 112, 62 socket: 356, 17094, 48, 7, 294 unpcb: 140, 17108, 14, 42, 135 udpcb: 180, 17094, 14, 30, 95 inpcb: 180, 17094, 23, 43, 63 tcpcb: 460, 17088, 20, 12, 63 tcptw: 48, 3432, 3, 153, 10 syncache: 100, 15366, 0, 78, 18 hostcache: 76, 15400, 2, 98, 2 tcpreass: 20, 1183, 0, 0, 0 sackhole: 20, 0, 0, 0, 0 ripcb: 180, 17094, 0, 0, 0 rtentry: 132, 0, 14, 44, 15 SWAPMETA: 276, 63266, 0, 0, 0 FFS inode: 132, 0, 740, 43, 777 FFS1 dinode: 128, 0, 0, 0, 0 FFS2 dinode: 256, 0, 740, 10, 777 md10: 512, 0, 292351, 41, 292418 Fabian --=20 http://www.fabiankeil.de/ --Sig_ewVYPuwn69neDc7MBZnMEla Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoCq9jV8GA4rMKUQRArMAAJsHFQS0a3ApFPI4JYUKiUo2RQ8NVgCgk7LQ /ngcHEvTTuQIKfex98evzl4= =wNd7 -----END PGP SIGNATURE----- --Sig_ewVYPuwn69neDc7MBZnMEla-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 15:20:45 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CE6D16A41F for ; Wed, 14 Dec 2005 15:20:45 +0000 (GMT) (envelope-from Colin.Farley@ecarecenters.com) Received: from ranger.electric.net (ranger.electric.net [216.129.90.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EAF443D5F for ; Wed, 14 Dec 2005 15:20:44 +0000 (GMT) (envelope-from Colin.Farley@ecarecenters.com) Received: from root by ranger.electric.net with emc1-ok (Exim 4.24) id 1EmYQt-0001b2-TH for freebsd-stable@freebsd.org; Wed, 14 Dec 2005 07:20:43 -0800 Received: by emcmailer; Wed, Dec 14 2005 07:20:43 -0800 Received: from [64.4.68.42] (helo=wpg1-notesmail.ecarecenters.net) by ranger.electric.net with esmtp (Exim 4.24) id 1EmYQs-0001aj-VR for freebsd-stable@freebsd.org; Wed, 14 Dec 2005 07:20:42 -0800 To: freebsd-stable@freebsd.org X-Mailer: Lotus Notes Release 7.0 August 18, 2005 Message-ID: From: Colin Farley Date: Wed, 14 Dec 2005 09:19:52 -0600 X-MIMETrack: Serialize by Router on PRLUSA-NOTESMAIL/COMPUBank(Release 6.5.4FP1|June 19, 2005) at 12/14/2005 09:19:40 AM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Virus-Status: Scanned by VirusSMART (s) Subject: free space reported incorrectly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 15:20:45 -0000 I'm running FreeBSD 4.10-RELEASE-p16 on a couple of production mail relays/web servers. Today I noticed that one had a lot more space in /var used. I figured that a log was growing and started to investigate. After running du -h /var and seeing it come up with a total usage much less than what df -h reports I decided to run fsck /var. This is the output I get: ** /dev/da1s1f (NO WRITE) ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=538020 OWNER=vscan MODE=100640 SIZE=251844 MTIME=Dec 5 14:27 2005 CLEAR? no UNREF FILE I=806417 OWNER=clamav MODE=100640 SIZE=281460 MTIME=Dec 14 15:49 2005 CLEAR? no UNREF FILE I=806441 OWNER=www MODE=100644 SIZE=183241 MTIME=Dec 14 04:34 2005 CLEAR? no UNREF FILE I=806446 OWNER=clamav MODE=100640 SIZE=352331 MTIME=Dec 14 15:25 2005 CLEAR? no UNREF FILE I=806465 OWNER=www MODE=100644 SIZE=39865 MTIME=Dec 14 01:29 2005 CLEAR? no UNREF FILE I=806467 OWNER=www MODE=100644 SIZE=132 MTIME=Oct 26 00:01 2005 CLEAR? no UNREF FILE I=806484 OWNER=www MODE=100644 SIZE=10908 MTIME=Dec 14 01:29 2005 CLEAR? no UNREF FILE I=806487 OWNER=www MODE=100644 SIZE=223963235 MTIME=Dec 14 16:01 2005 CLEAR? no UNREF FILE I=806501 OWNER=www MODE=100644 SIZE=132 MTIME=Oct 26 00:01 2005 CLEAR? no UNREF FILE I=806509 OWNER=root MODE=100644 SIZE=663256384 MTIME=Dec 14 16:01 2005 CLEAR? no UNREF FILE I=806516 OWNER=www MODE=100644 SIZE=132 MTIME=Oct 26 00:01 2005 CLEAR? no UNREF FILE I=806523 OWNER=www MODE=100644 SIZE=132 MTIME=Oct 26 00:01 2005 CLEAR? no ** Phase 5 - Check Cyl groups SUMMARY INFORMATION BAD SALVAGE? no BLK(S) MISSING IN BIT MAPS SALVAGE? no 3954 files, 479350 used, 4701227 free (2355 frags, 587359 blocks, 0.0% fragmentation) I see there are a couple of large files there that seem to have some problems. Can anyone explain what is going on and maybe point me in the direction of a good document on fsck and common problems? Thanks, Colin From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 15:40:58 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AA5616A41F; Wed, 14 Dec 2005 15:40:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92CB543D7F; Wed, 14 Dec 2005 15:40:52 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jBEFeiGH004672; Wed, 14 Dec 2005 08:40:45 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43A03CFC.6070406@samsco.org> Date: Wed, 14 Dec 2005 08:40:44 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gleb Smirnoff References: <20051214132530.3b6daecd@TP51.local> <20051214131855.GH59644@FreeBSD.org> In-Reply-To: <20051214131855.GH59644@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.0 panic: kmem_malloc(16384): kmem_map too small: 172728320 total allocated X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 15:40:58 -0000 Gleb Smirnoff wrote: > On Wed, Dec 14, 2005 at 01:25:30PM +0100, Fabian Keil wrote: > F> I triggered a few reproducible panics on FreeBSD 6.0-STABLE. > F> > F> I created a ramdisk with: > F> > F> /sbin/mdconfig -a -t malloc -s 256M -u 10 > F> /sbin/newfs -U /dev/md10 > F> /sbin/mount /dev/md10 /mnt/ramdisk > F> > F> The system has "avail memory = 515932160 (492 MB)" > F> and 1GB swap space. > F> > F> While copying to /mnt/ramdisk trough ftp localhost > F> it got: > > This usually exposes some memory leak in kernel. Can you please do the > following - copy some amount of data to /mnt/ramdisk trough ftp localhost, > and cancel the operation before it panics. > > Then run vmstat -m and vmstat -z, to determine what kind of memory allocation > is leaking. > > While it can mean a memory leak in the kernel, I don't think that's the case here. On i386, only 320MB can be allocated to kernel malloc memory. Much of this space can get consumed with vnodes and other filesystem structures, so trying to allocate 256MB to a ramdisk is likely putting you over the max. I'd suggest instead to use a swap-back disk. It doesn't necessarily mean that the ramdisk pages will live in swap, it just means that they will get managed directly in the bufcache, eliminating the 320MB restriction. Scott From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 16:33:18 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48F3E16A41F for ; Wed, 14 Dec 2005 16:33:18 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A22043D58 for ; Wed, 14 Dec 2005 16:33:15 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 20968 invoked from network); 14 Dec 2005 16:33:13 -0000 Received: from unknown (HELO TP51.local) ([pbs]775067@[217.187.177.99]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 14 Dec 2005 16:33:13 -0000 Date: Wed, 14 Dec 2005 17:32:34 +0100 From: Fabian Keil To: Scott Long Message-ID: <20051214173234.4bb5ffb9@TP51.local> In-Reply-To: <43A03CFC.6070406@samsco.org> References: <20051214132530.3b6daecd@TP51.local> <20051214131855.GH59644@FreeBSD.org> <43A03CFC.6070406@samsco.org> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.6; i386-portbld-freebsd5.4) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_DozOW9gfpdiMI6_.CT6ET5G; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Gleb Smirnoff , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.0 panic: kmem_malloc(16384): kmem_map too small: 172728320 total allocated [solved] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 16:33:18 -0000 --Sig_DozOW9gfpdiMI6_.CT6ET5G Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Scott Long wrote: > Gleb Smirnoff wrote: >=20 > > On Wed, Dec 14, 2005 at 01:25:30PM +0100, Fabian Keil wrote: > > F> I triggered a few reproducible panics on FreeBSD 6.0-STABLE. > > F>=20 > > F> I created a ramdisk with: > > F> =20 > > F> /sbin/mdconfig -a -t malloc -s 256M -u 10 > > F> /sbin/newfs -U /dev/md10 > > F> /sbin/mount /dev/md10 /mnt/ramdisk > > F>=20 > > F> The system has "avail memory =3D 515932160 (492 MB)" > > F> and 1GB swap space. > > F>=20 > > F> While copying to /mnt/ramdisk trough ftp localhost > > F> it got: > >=20 > > This usually exposes some memory leak in kernel. Can you please do > > the following - copy some amount of data to /mnt/ramdisk trough ftp > > localhost, and cancel the operation before it panics. > >=20 > > Then run vmstat -m and vmstat -z, to determine what kind of memory > > allocation is leaking. > >=20 > >=20 >=20 > While it can mean a memory leak in the kernel, I don't think that's > the case here. > On i386, only 320MB can be allocated to kernel malloc memory. Much > of this space > can get consumed with vnodes and other filesystem structures, so > trying to allocate > 256MB to a ramdisk is likely putting you over the max. I'd suggest=20 > instead to use > a swap-back disk. It doesn't necessarily mean that the ramdisk pages=20 > will live in > swap, it just means that they will get managed directly in the > bufcache, eliminating > the 320MB restriction. I guess you're right. I can fill a 256MB swap-backed disk without panic=20 and without swapping. Before ftp localhost: last pid: 652; load averages: 0.02, 0.09, 0.07 up 0+00:07:16 17:12:05 37 processes: 1 running, 36 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.4% interrupt, 99.6% idle Mem: 11M Active, 12M Inact, 18M Wired, 11M Buf, 453M Free Swap: 999M Total, 999M Free After ftp localhost: last pid: 666; load averages: 0.20, 0.12, 0.08 up 0+00:09:05 17:13:54 36 processes: 1 running, 35 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.4% interrupt, 99.6% idle Mem: 244M Active, 150M Inact, 73M Wired, 27M Cache, 60M Buf, 984= K Free Swap: 999M Total, 999M Free After removal of the swap-backed disk: last pid: 690; load averages: 0.00, 0.01, 0.03 up 0+00:17:53 17:22:42 34 processes: 1 running, 33 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 15M Active, 76M Inact, 43M Wired, 13M Cache, 60M Buf, 347M F= ree Swap: 999M Total, 999M Free Thanks for your time Gleb and Scott. Fabian --=20 http://www.fabiankeil.de/ --Sig_DozOW9gfpdiMI6_.CT6ET5G Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoEk7jV8GA4rMKUQRAiU9AKCxxVRrnuGW1/RBE94c5a6klL5N6QCgutnB GOB5wVzdwaFJC+Z5imlLQ8E= =xqEn -----END PGP SIGNATURE----- --Sig_DozOW9gfpdiMI6_.CT6ET5G-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 16:35:08 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9733A16A41F for ; Wed, 14 Dec 2005 16:35:08 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 265EB43D46 for ; Wed, 14 Dec 2005 16:35:07 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id jBEGZ0S7045577; Wed, 14 Dec 2005 10:35:00 -0600 (CST) (envelope-from dan) Date: Wed, 14 Dec 2005 10:35:00 -0600 From: Dan Nelson To: Colin Farley Message-ID: <20051214163500.GA18296@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: free space reported incorrectly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 16:35:08 -0000 In the last episode (Dec 14), Colin Farley said: > I'm running FreeBSD 4.10-RELEASE-p16 on a couple of production mail > relays/web servers. Today I noticed that one had a lot more space in > /var used. I figured that a log was growing and started to > investigate. After running du -h /var and seeing it come up with a > total usage much less than what df -h reports I decided to run fsck > /var. This is the output I get: > > ** /dev/da1s1f (NO WRITE) Don't trust any fsck output on a mounted filessytem. You probably have some logfiles that got manually rotated or deleted (i.e. not via newsyslog), and syslogd was never told to close&reopen the logfile. Run "lsof +L1" (lsof is in ports) to find the offending processes and restart them. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 18:01:59 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6887416A41F for ; Wed, 14 Dec 2005 18:01:59 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9997C43D5A for ; Wed, 14 Dec 2005 18:01:58 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail09.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBEI1tZZ001086 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 15 Dec 2005 05:01:56 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBEI1tHh080256; Thu, 15 Dec 2005 05:01:55 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBEI1tAS080255; Thu, 15 Dec 2005 05:01:55 +1100 (EST) (envelope-from pjeremy) Date: Thu, 15 Dec 2005 05:01:55 +1100 From: Peter Jeremy To: fredthetree Message-ID: <20051214180155.GH77268@cirb503493.alcatel.com.au> References: <439DE88B.1090407@asd.aplus.net> <439E0B23.3060304@asd.aplus.net> <20051213025028.GC77268@cirb503493.alcatel.com.au> <20051213182742.GG77268@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 18:01:59 -0000 On Wed, 2005-Dec-14 08:28:26 -0400, fredthetree wrote: >i've only used the generic 6.0 kernel > ># kgdb kernel.debug /var/crash/vmcore.1 ... >#6 0xc07f6dca in calltrap () at /usr/src/sys/i386/i386/exception.s:139 >#7 0xc0a7cf08 in ?? () Unfortunately, it's frame 7 and below that is crucial. Was #7 the last line or did you cut the backtrace off? The top frames are the kernel handling the trap. It looks like the trap occurred in a KLD - in this case, try running: # cd /usr/obj/usr/src/sys/GENERIC (or name of kernel config) # make gdbinit [this just copies a few config files for kgdb] # gdb kernel.debug /var/crash/vmcore.1 (kgdb) kldsyms (kgdb) where Hopefully this will decode #7 and you can provide a few more frames. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 18:14:12 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B428C16A41F for ; Wed, 14 Dec 2005 18:14:12 +0000 (GMT) (envelope-from nealie@kobudo.homeunix.net) Received: from neal.nelson.name (neal.nelson.name [82.139.192.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id A932443D76 for ; Wed, 14 Dec 2005 18:14:11 +0000 (GMT) (envelope-from nealie@kobudo.homeunix.net) Received: from [10.0.0.8] (wtibook.home [10.0.0.8]) by neal.nelson.name with esmtp; Wed, 14 Dec 2005 19:14:09 +0100 id 000CF017.43A060F1.0000771B Mime-Version: 1.0 (Apple Message framework v623) Content-Transfer-Encoding: 7bit Message-Id: <70a5d94afc7213b73c0b44c881c49c76@kobudo.homeunix.net> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-stable@freebsd.org From: Neal Nelson Date: Wed, 14 Dec 2005 19:14:07 +0100 X-Mailer: Apple Mail (2.623) Subject: WPA Access Point X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 18:14:12 -0000 Has anyone got FreeBSD 6.0 to work as a wireless access point using WPA? I'm running a Prism 2.5 based wireless card and have been using it as an access point for years. It stills works OK but I installed the hostapd port in order to add WPA authentication. Unfortunately this doesn't seem to work as it complains when I run it as follows: bsd_configure_wpa: group key cipher=AES-CCM (3) ioctl[SIOCS80211]: Invalid argument I'm not sure whether hostapd is configured right as there seems to be no documentation for it. Can anyone shed some light on this or am I barking up the wrong tree as far as WPA is concerned? From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 19:00:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB35016A420 for ; Wed, 14 Dec 2005 19:00:03 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B69943D60 for ; Wed, 14 Dec 2005 18:59:52 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.200] ([10.0.0.200]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id jBEIxoA8000275 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Dec 2005 10:59:50 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43A06BDA.5030602@errno.com> Date: Wed, 14 Dec 2005 11:00:42 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Neal Nelson References: <70a5d94afc7213b73c0b44c881c49c76@kobudo.homeunix.net> In-Reply-To: <70a5d94afc7213b73c0b44c881c49c76@kobudo.homeunix.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: WPA Access Point X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 19:00:03 -0000 Neal Nelson wrote: > Has anyone got FreeBSD 6.0 to work as a wireless access point using WPA? > > I'm running a Prism 2.5 based wireless card and have been using it as an > access point for years. It stills works OK but I installed the hostapd > port in order to add WPA authentication. Unfortunately this doesn't seem > to work as it complains when I run it as follows: > > bsd_configure_wpa: group key cipher=AES-CCM (3) > ioctl[SIOCS80211]: Invalid argument > > I'm not sure whether hostapd is configured right as there seems to be no > documentation for it. > > Can anyone shed some light on this or am I barking up the wrong tree as > far as WPA is concerned? The above error is likely because you don't have wlan_ccmp loaded/configured. However ifconfig wi0 list caps should indicate the driver lacks support for WPA1/WPA2. Guess it would be good for hostpad to check that. Sam From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 19:00:48 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C59D516A41F for ; Wed, 14 Dec 2005 19:00:48 +0000 (GMT) (envelope-from ptroot@iaces.com) Received: from iaces.com (horton.iaces.com [204.147.87.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D62443D7C for ; Wed, 14 Dec 2005 19:00:44 +0000 (GMT) (envelope-from ptroot@iaces.com) Received: from [204.147.87.125] (borg.iaces.com [204.147.87.125]) (authenticated bits=0) by iaces.com (8.13.4/8.13.3) with ESMTP id jBEJ0apP044259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 14 Dec 2005 13:00:37 -0600 (CST) (envelope-from ptroot@iaces.com) Message-ID: <43A06BE2.7080703@iaces.com> Date: Wed, 14 Dec 2005 13:00:50 -0600 From: "Paul T. Root" User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: nfs server timeout X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 19:00:48 -0000 I have a HP Vectra running FreeBSD acesfbsd 6.0-STABLE FreeBSD 6.0-STABLE #0: Fri Dec 9 14:44:30 CST 2005 that has trouble with nfs mounts (amd home directory) from a Solaris 8 box. It started life as 4.x went through a lot of 5.x all with no problems. However, since upgrading to 6.0, occasionally, it will get the dreaded "nfs server not responding" message. That will last for a few minutes and then come back. The server is fine, all the Solaris clients have no trouble at the time. The ethernet interface is clean. 100Meg full. Any thoughts? Thanks, Paul. -- ______ Paul T. Root / _ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \______/ From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 20:43:59 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AF3516A41F; Wed, 14 Dec 2005 20:43:59 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21EE043D45; Wed, 14 Dec 2005 20:43:55 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E54161A3C1F; Wed, 14 Dec 2005 12:43:50 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2F9C051592; Wed, 14 Dec 2005 15:43:50 -0500 (EST) Date: Wed, 14 Dec 2005 15:43:50 -0500 From: Kris Kennaway To: Fabian Keil Message-ID: <20051214204349.GA86018@xor.obsecurity.org> References: <20051214132530.3b6daecd@TP51.local> <20051214131855.GH59644@FreeBSD.org> <43A03CFC.6070406@samsco.org> <20051214173234.4bb5ffb9@TP51.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: <20051214173234.4bb5ffb9@TP51.local> User-Agent: Mutt/1.4.2.1i Cc: Gleb Smirnoff , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.0 panic: kmem_malloc(16384): kmem_map too small: 172728320 total allocated [solved] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 20:43:59 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 14, 2005 at 05:32:34PM +0100, Fabian Keil wrote: > I guess you're right. I can fill a 256MB swap-backed disk without panic= =20 > and without swapping. FYI, this is documented in the manpage. Kris --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoIQFWry0BWjoQKURAqXcAJ922akbacwUqaZjsw5vEPHe6lPgmACgn9Jb QyfnpHhgvnWm+FNFt7kcicM= =ypaG -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 20:47:04 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5710A16A41F for ; Wed, 14 Dec 2005 20:47:04 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 016EB43D8D for ; Wed, 14 Dec 2005 20:47:01 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from 35st-server.simplicato.com (static-71-249-233-130.nycmny.east.verizon.net [71.249.233.130]) by zoraida.natserv.net (Postfix) with ESMTP id E81A97E4D for ; Wed, 14 Dec 2005 15:46:46 -0500 (EST) Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: FreeBSD Stable List Date: Wed, 14 Dec 2005 15:48:39 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Subject: 6 Stable freezes upon bootup, but Release 6.0 works X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 20:47:04 -0000 Have a machine that once we upgraded to 6 Stable the machine would freeze at the bootup menu. We tried disabling ACPI and AIPC and it did not help. Usually the freezing occurs after 2 or 3 seconds out of the 10 second countdown. To make it more interesting... if we press enter right after the menu comes up the machine boots perfectly fine and the machine works without any problems. Motherboard Tyan S515G3NR, 3WARE 2 port controller, 2GB RAM. Tried stable from 12-6-05 (initial stable cvsup we did).. and after we discovered the problem we also tried stable as of 12-12-05. Strangely enough we have a second machine with the same motherboard, same amount of memory, same 3Ware controller, but with different drives. the machine that is Freezing has 10K RPM SATA raptors and the other has some 7200RPM western digitals (same brand as the raptors). That second machine works fine with 12-6 stable. We looked at the bios levels and as far as we can tell they have the same bios level. On the trouble machine I did do a custom kernel, but I don't believe the kernel is even loading yet at the point it freezes. :-( Is there a verbose mode or log for the boot menu and/or the boot process? Given some recent bug fixes on 6 stable that correct a problem with Raid controllers I really would like to get both machines to 6 Stable. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 20:56:01 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16F7C16A41F for ; Wed, 14 Dec 2005 20:56:01 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2769A43D6A for ; Wed, 14 Dec 2005 20:55:49 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by zproxy.gmail.com with SMTP id 4so240121nzn for ; Wed, 14 Dec 2005 12:55:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Vkh5iltXkYzuz+2/EGnoHRGl6Dxn/X2GAWFSvXjUfE0xAy8np9jUBkGq7WjdWX3mDWq7ZwZHD0zZ0b4z/fKNbXClZnCP80EE/00PpiqMEDxp2lKRr4clYmWIUefrjejfvmzUwcbOcauY1sN5Gd7NUV4pgWSB4t2+L2JNxi+vYWg= Received: by 10.65.186.7 with SMTP id n7mr767094qbp; Wed, 14 Dec 2005 12:55:48 -0800 (PST) Received: by 10.65.192.14 with HTTP; Wed, 14 Dec 2005 12:55:48 -0800 (PST) Message-ID: Date: Wed, 14 Dec 2005 21:55:48 +0100 From: Claus Guttesen To: Francisco Reyes In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Cc: FreeBSD Stable List Subject: Re: 6 Stable freezes upon bootup, but Release 6.0 works X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 20:56:01 -0000 > Have a machine that once we upgraded to 6 Stable the machine would freeze= at > the bootup menu. > > Strangely enough we have a second machine with the same motherboard, same > amount of memory, same 3Ware controller, but with different drives. the > machine that is Freezing has 10K RPM SATA raptors and the other has some > 7200RPM western digitals (same brand as the raptors). That second machine > works fine with 12-6 stable. Have you tried to swap the disks? And tried to run memtest (www.memtest.org= )? regards Claus From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 21:53:21 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E91716A41F for ; Wed, 14 Dec 2005 21:53:21 +0000 (GMT) (envelope-from Colin.Farley@ecarecenters.com) Received: from ranger.electric.net (ranger.electric.net [216.129.90.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD4FB43D58 for ; Wed, 14 Dec 2005 21:53:20 +0000 (GMT) (envelope-from Colin.Farley@ecarecenters.com) Received: from root by ranger.electric.net with emc1-ok (Exim 4.24) id 1EmeYp-0001KF-W9; Wed, 14 Dec 2005 13:53:19 -0800 Received: by emcmailer; Wed, Dec 14 2005 13:53:19 -0800 Received: from [64.4.68.42] (helo=wpg1-notesmail.ecarecenters.net) by ranger.electric.net with esmtp (Exim 4.24) id 1EmeYp-0001Ju-TG; Wed, 14 Dec 2005 13:53:19 -0800 In-Reply-To: <20051214163500.GA18296@dan.emsphone.com> To: Dan Nelson X-Mailer: Lotus Notes Release 7.0 August 18, 2005 Message-ID: From: Colin Farley Date: Wed, 14 Dec 2005 15:51:12 -0600 X-MIMETrack: Serialize by Router on PRLUSA-NOTESMAIL/COMPUBank(Release 6.5.4FP1|June 19, 2005) at 12/14/2005 03:52:16 PM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Virus-Status: Scanned by VirusSMART (s) Cc: freebsd-stable@freebsd.org Subject: Re: free space reported incorrectly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 21:53:21 -0000 Thanks for the reply. I have found as suspected that apache is responsible. Since these servers are redundant using UCARP I am planning to shut down the services, unmount /var and run fsck, one at a time. I'm just not sure why I cannot see these files but hopefully fsck will make them visable or just remove them for me. I think at the same time I will make a change to my apache log rotation strategy as it appears to be causing the problems. Thanks again, Colin Dan Nelson To Colin Farley 12/14/2005 10:35 AM cc freebsd-stable@freebsd.org Subject Re: free space reported incorrectly In the last episode (Dec 14), Colin Farley said: > I'm running FreeBSD 4.10-RELEASE-p16 on a couple of production mail > relays/web servers. Today I noticed that one had a lot more space in > /var used. I figured that a log was growing and started to > investigate. After running du -h /var and seeing it come up with a > total usage much less than what df -h reports I decided to run fsck > /var. This is the output I get: > > ** /dev/da1s1f (NO WRITE) Don't trust any fsck output on a mounted filessytem. You probably have some logfiles that got manually rotated or deleted (i.e. not via newsyslog), and syslogd was never told to close&reopen the logfile. Run "lsof +L1" (lsof is in ports) to find the offending processes and restart them. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 22:01:21 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49BC416A41F for ; Wed, 14 Dec 2005 22:01:21 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2375E43D62 for ; Wed, 14 Dec 2005 22:01:19 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id jBEM17VH015367; Wed, 14 Dec 2005 16:01:07 -0600 (CST) (envelope-from dan) Date: Wed, 14 Dec 2005 16:01:07 -0600 From: Dan Nelson To: Colin Farley Message-ID: <20051214220107.GB18296@dan.emsphone.com> References: <20051214163500.GA18296@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: free space reported incorrectly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 22:01:21 -0000 In the last episode (Dec 14), Colin Farley said: > Thanks for the reply. I have found as suspected that apache is > responsible. Since these servers are redundant using UCARP I am > planning to shut down the services, unmount /var and run fsck, one at > a time. I'm just not sure why I cannot see these files but hopefully > fsck will make them visable or just remove them for me. I think at > the same time I will make a change to my apache log rotation strategy > as it appears to be causing the problems. You can't see the files because they have been deleted. As long as a process holds a filehandle open on the file, however, the file still exists and consumes space in the filessytem. Killing the apache processes (or sending this the appropriate "reopen your logfiles" signal) will suffice to free the space up. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 22:20:42 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D416116A41F for ; Wed, 14 Dec 2005 22:20:42 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D40643D55 for ; Wed, 14 Dec 2005 22:20:42 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465 for ; Wed, 14 Dec 2005 14:20:37 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 94FEF5D07 for ; Wed, 14 Dec 2005 14:20:37 -0800 (PST) To: stable@freebsd.org Date: Wed, 14 Dec 2005 14:20:37 -0800 From: "Kevin Oberman" Message-Id: <20051214222037.94FEF5D07@ptavv.es.net> Cc: Subject: Odd performance problems after upgrade from 4.11 to 6.0-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 22:20:43 -0000 I recently upgraded my last desktop system from 4.11-Stable to 6.0-Stable. I did an update to 5.3 then to RELENG_5, RELENG_6_0_0_RELEASE and on to RELENG6_0. This system has been updated regularly from the days of at least 4.1. The hardware is a 1GHz PIII with an ICH2 chipset. 256 MB of memory. After the upgrade, the system performs poorly. Specifically, it seems to be blocking on I/O. If I have a dump or bsdtar running, a CPU intensive job produced minimal CPU utilization and little progress. The system is 70% or more idle all of the time. X is particularly sluggish. Many times the system will simply appear to be locked up for seconds at a time like all of the I/O is synchronous and the entire system is blocking on GIANT until the disk write finishes. A level 0 dump of the system drive piped through gzip and over the network took about 10 hours. Now it is 17 hours. My network link only ran at 3.4 Mbps (yes, that's bits, not Bytes) over a 100 Mbps connection to the storage server. The rate was much higher under 4.11. My attempts to track down the source of the problem simply failed. I have examined my kernel configuration and found nothing out of the ordinary. In fact, the the configuration varies from GENERIC only in devices (both added and deleted), dropping 486 and 586 CPU code and a larger SC_HISTORY. I have nothing in sysctl.conf and only enable DMA on my ATAPI devices in loader.conf. I have confirmed that the disks are running ATA100. Any suggestions on where to look? At this point I am baffled. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 14 23:17:49 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7911116A41F for ; Wed, 14 Dec 2005 23:17:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B314143D55 for ; Wed, 14 Dec 2005 23:17:46 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jBENHdwY006972; Wed, 14 Dec 2005 16:17:39 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43A0A812.1060104@samsco.org> Date: Wed, 14 Dec 2005 16:17:38 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20051214222037.94FEF5D07@ptavv.es.net> In-Reply-To: <20051214222037.94FEF5D07@ptavv.es.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: stable@freebsd.org Subject: Re: Odd performance problems after upgrade from 4.11 to 6.0-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 23:17:49 -0000 Kevin Oberman wrote: > I recently upgraded my last desktop system from 4.11-Stable to > 6.0-Stable. I did an update to 5.3 then to RELENG_5, > RELENG_6_0_0_RELEASE and on to RELENG6_0. > > This system has been updated regularly from the days of at least 4.1. > The hardware is a 1GHz PIII with an ICH2 chipset. 256 MB of memory. > > After the upgrade, the system performs poorly. Specifically, it seems to > be blocking on I/O. If I have a dump or bsdtar running, a CPU intensive > job produced minimal CPU utilization and little progress. The system is > 70% or more idle all of the time. X is particularly sluggish. Many times > the system will simply appear to be locked up for seconds at a time like > all of the I/O is synchronous and the entire system is blocking on GIANT > until the disk write finishes. A level 0 dump of the system drive piped > through gzip and over the network took about 10 hours. Now it is 17 > hours. My network link only ran at 3.4 Mbps (yes, that's bits, not > Bytes) over a 100 Mbps connection to the storage server. The rate was > much higher under 4.11. > > My attempts to track down the source of the problem simply failed. I > have examined my kernel configuration and found nothing out of the > ordinary. In fact, the the configuration varies from GENERIC only in > devices (both added and deleted), dropping 486 and 586 CPU code and a > larger SC_HISTORY. I have nothing in sysctl.conf and only enable DMA on > my ATAPI devices in loader.conf. I have confirmed that the disks are > running ATA100. > > Any suggestions on where to look? At this point I am baffled. The bufdaemon is probably causing some of the Giant contention. However, what it is contending with is the real question. Is your network driver and stack running MPSAFE? At least a 'dmesg' dump is needed here. Also, taking out CPU_I586 is usually a bad idea. It offers no performance penalties (unlike CPU_I386 and maybe CPU_I486), but enables things like optimized bcopy. Scott From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 00:26:26 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6AE916A41F for ; Thu, 15 Dec 2005 00:26:26 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal4.es.net (postal4.es.net [198.124.252.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5194E43D68 for ; Thu, 15 Dec 2005 00:26:25 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id IBA74465; Wed, 14 Dec 2005 16:26:24 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id B4D3B5D07; Wed, 14 Dec 2005 16:26:18 -0800 (PST) X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Scott Long In-reply-to: Your message of "Wed, 14 Dec 2005 16:17:38 MST." <43A0A812.1060104@samsco.org> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_1134606298_362810" Date: Wed, 14 Dec 2005 16:26:18 -0800 From: "Kevin Oberman" Message-Id: <20051215002618.B4D3B5D07@ptavv.es.net> Cc: stable@freebsd.org Subject: Re: Odd performance problems after upgrade from 4.11 to 6.0-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 00:26:26 -0000 This is a multipart MIME message. --==_Exmh_1134606298_362810 Content-Type: text/plain; charset=us-ascii > Date: Wed, 14 Dec 2005 16:17:38 -0700 > From: Scott Long > > Kevin Oberman wrote: > > > I recently upgraded my last desktop system from 4.11-Stable to > > 6.0-Stable. I did an update to 5.3 then to RELENG_5, > > RELENG_6_0_0_RELEASE and on to RELENG6_0. > > > > This system has been updated regularly from the days of at least 4.1. > > The hardware is a 1GHz PIII with an ICH2 chipset. 256 MB of memory. > > > > After the upgrade, the system performs poorly. Specifically, it seems to > > be blocking on I/O. If I have a dump or bsdtar running, a CPU intensive > > job produced minimal CPU utilization and little progress. The system is > > 70% or more idle all of the time. X is particularly sluggish. Many times > > the system will simply appear to be locked up for seconds at a time like > > all of the I/O is synchronous and the entire system is blocking on GIANT > > until the disk write finishes. A level 0 dump of the system drive piped > > through gzip and over the network took about 10 hours. Now it is 17 > > hours. My network link only ran at 3.4 Mbps (yes, that's bits, not > > Bytes) over a 100 Mbps connection to the storage server. The rate was > > much higher under 4.11. > > > > My attempts to track down the source of the problem simply failed. I > > have examined my kernel configuration and found nothing out of the > > ordinary. In fact, the the configuration varies from GENERIC only in > > devices (both added and deleted), dropping 486 and 586 CPU code and a > > larger SC_HISTORY. I have nothing in sysctl.conf and only enable DMA on > > my ATAPI devices in loader.conf. I have confirmed that the disks are > > running ATA100. > > > > Any suggestions on where to look? At this point I am baffled. > > The bufdaemon is probably causing some of the Giant contention. > However, what it is contending with is the real question. Is > your network driver and stack running MPSAFE? At least a 'dmesg' > dump is needed here. > > Also, taking out CPU_I586 is usually a bad idea. It offers no > performance penalties (unlike CPU_I386 and maybe CPU_I486), but > enables things like optimized bcopy. Ahh, This is the sort of thing I never realized. Is there anything in the handbook that covers this? I had always been under the impression that CPU_I686 enabled all things that the 686 was capable of. I will build a new kernel to add that back in. I am attaching a dmesg. I do have a few of drivers (uhci, pcm, psm, atkbd0 and ichsmb) that are still marked as GIANT-LOCKED, but I'm not using the USB very often. And I'm not using pcm or ichsmb during the dump, either. I think everyone has the mouse and keyboard under GIANT, but I can't really see those as a problem, either. I will attach both my kernel configuration and my dmesg in hopes that I'm missing something obvious. Thanks! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 --==_Exmh_1134606298_362810 Content-Type: text/plain ; name="PTAVV"; charset=us-ascii Content-Description: PTAVV Content-Disposition: attachment; filename="PTAVV" # # PTAVV -- Modified ESnet kernel configuration file for FreeBSD/i386 # running on TWC Dell PIII system. # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.4 2005/10/28 19:21:27 jhb Exp $ machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident PTAVV # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols #options SCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. #options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. #device apic # I/O APIC # Bus support. #device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives #device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives device atapicam # emulate ATAPI devices as SCSI ditto via CAM # needs CAM to be present (scbus & pass) options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) #device ch # SCSI media changers device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc options SC_HISTORY_SIZE=2000 # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor device agp # support several AGP chipsets # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port #device ppc #device ppbus # Parallel port bus (required) #device lpt # Printer #device plip # TCP/IP over parallel #device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to the sio and/or ppc drivers): #device puc # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support #device sl # Kernel SLIP #device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse #device ural # Ralink Technology RT2500USB wireless NICs #device urio # Diamond Rio 500 MP3 player device uscanner # Scanners # USB Ethernet, requires miibus #device aue # ADMtek USB Ethernet #device axe # ASIX Electronics USB Ethernet #device cdce # Generic USB over Ethernet #device cue # CATC USB Ethernet #device kue # Kawasaki LSI USB Ethernet #device rue # RealTek RTL8150 USB Ethernet # FireWire support #device firewire # FireWire bus code #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) # Sound card device smbus device ichsmb device smb device sound device snd_ich # Video capture card device iicbus device iicbb device bktr options BROOKTREE_SYSTEM_DEFAULT=BROOKTREE_NTSC --==_Exmh_1134606298_362810 Content-Type: text/plain ; name="dmesg.boot"; charset=us-ascii Content-Description: dmesg.boot Content-Disposition: attachment; filename="dmesg.boot" Copyright (c) 1992-2005 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 6.0-STABLE #0: Sun Dec 11 23:18:16 PST 2005 oberman@ptavv.es.net:/usr/obj/usr/src/sys/PTAVV Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (996.77-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383fbff real memory = 267350016 (254 MB) avail memory = 256102400 (244 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf4000000-0xf7ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xec80-0xecff mem 0xfbfffc00-0xfbfffc7f irq 11 at device 12.0 on pci2 miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:06:5b:80:b1:fc isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0xff80-0xff9f irq 11 at device 31.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ichsmb0: port 0xdcd0-0xdcdf irq 10 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: on ichsmb0 smb0: on smbus0 uhci1: port 0xff60-0xff7f irq 9 at device 31.4 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcm0: port 0xd800-0xd8ff,0xdc40-0xdc7f irq 10 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc87ff,0xc8800-0xcbfff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 996769408 Hz quality 800 Timecounters tick every 1.000 msec ad0: 38166MB at ata0-master UDMA100 ad1: 19092MB at ata0-slave UDMA100 acd0: CDRW at ata1-master UDMA33 acd1: DMA limited to UDMA33, controller found non-ATA66 cable acd1: DVDR at ata1-slave UDMA33 pcm0: measured ac97 link rate at 55947 Hz Trying to mount root from ufs:/dev/ad0s1a cd0 at ata1 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed cd1 at ata1 bus 0 target 0 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled --==_Exmh_1134606298_362810-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 00:34:08 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D1EF16A41F for ; Thu, 15 Dec 2005 00:34:08 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D78643D5C for ; Thu, 15 Dec 2005 00:34:08 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6A4AB1A3C2C; Wed, 14 Dec 2005 16:34:06 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 266FD54A41; Wed, 14 Dec 2005 19:34:05 -0500 (EST) Date: Wed, 14 Dec 2005 19:34:04 -0500 From: Kris Kennaway To: Kevin Oberman Message-ID: <20051215003403.GA89393@xor.obsecurity.org> References: <43A0A812.1060104@samsco.org> <20051215002618.B4D3B5D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: <20051215002618.B4D3B5D07@ptavv.es.net> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: Odd performance problems after upgrade from 4.11 to 6.0-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 00:34:08 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Dec 14, 2005 at 04:26:18PM -0800, Kevin Oberman wrote: > I am attaching a dmesg. I do have a few of drivers (uhci, pcm, psm, > atkbd0 and ichsmb) that are still marked as GIANT-LOCKED, but I'm not > using the USB very often. And I'm not using pcm or ichsmb during the > dump, either. I think everyone has the mouse and keyboard under GIANT, > but I can't really see those as a problem, either. A bunch of things are sharing interrupts with USB..disable it and see if that helps. Also check vmstat -i to see if some device is storming. If not, turn on MUTEX_PROFILING(9) in your kernel and run the dump (or something faster that also exhibits the problem), then look for what is contending with Giant. Kris --UugvWAfsgieZRqgk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoLn6Wry0BWjoQKURAhTOAJ4rE/clAQL1Fh4bbbxI64onRE6A/ACgtyg9 RGwE2WCaU+DE3I3NjwdN9n0= =FpU+ -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 00:45:50 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F4816A41F for ; Thu, 15 Dec 2005 00:45:50 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal4.es.net (postal4.es.net [198.124.252.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AD4C43D5D for ; Thu, 15 Dec 2005 00:45:50 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id IBA74465; Wed, 14 Dec 2005 16:45:49 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id EAE465D07; Wed, 14 Dec 2005 16:45:47 -0800 (PST) To: Kris Kennaway In-reply-to: Your message of "Wed, 14 Dec 2005 19:34:04 EST." <20051215003403.GA89393@xor.obsecurity.org> Date: Wed, 14 Dec 2005 16:45:47 -0800 From: "Kevin Oberman" Message-Id: <20051215004547.EAE465D07@ptavv.es.net> Cc: stable@freebsd.org Subject: Re: Odd performance problems after upgrade from 4.11 to 6.0-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 00:45:50 -0000 > Date: Wed, 14 Dec 2005 19:34:04 -0500 > From: Kris Kennaway > > On Wed, Dec 14, 2005 at 04:26:18PM -0800, Kevin Oberman wrote: > > > I am attaching a dmesg. I do have a few of drivers (uhci, pcm, psm, > > atkbd0 and ichsmb) that are still marked as GIANT-LOCKED, but I'm not > > using the USB very often. And I'm not using pcm or ichsmb during the > > dump, either. I think everyone has the mouse and keyboard under GIANT, > > but I can't really see those as a problem, either. > > A bunch of things are sharing interrupts with USB..disable it and see > if that helps. Also check vmstat -i to see if some device is > storming. If not, turn on MUTEX_PROFILING(9) in your kernel and run > the dump (or something faster that also exhibits the problem), then > look for what is contending with Giant. Yes, it may be time for MUTEX_PROFILING. I had already looked at interrupts. My kernel is sans APIC so I didn't really think that interrupts were a problems and I see: interrupt total rate irq0: clk 207037779 1000 irq1: atkbd0 50208 0 irq6: fdc0 9 0 irq8: rtc 26498038 128 irq10: pcm0 ichsmb0 2 0 irq11: xl0 uhci0 18076067 87 irq12: psm0 869500 4 irq13: npx0 1 0 irq14: ata0 10423468 50 irq15: ata1 112 0 Total 262955184 1270 Clearly no storms and nothing looks obviously broken. USB and the network card share an IRQ, but the USB is not connected to anything and I would not think that it is generating many interrupts. The network IS being used and I'm not seeing all that many interrupts on IRQ11. Thanks for the suggestions! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 00:52:23 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7EAF16A41F for ; Thu, 15 Dec 2005 00:52:23 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7E6943D7F for ; Thu, 15 Dec 2005 00:52:11 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8059D1A3C2A; Wed, 14 Dec 2005 16:52:04 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 60F4351588; Wed, 14 Dec 2005 19:52:03 -0500 (EST) Date: Wed, 14 Dec 2005 19:52:03 -0500 From: Kris Kennaway To: Kevin Oberman Message-ID: <20051215005203.GA89670@xor.obsecurity.org> References: <20051215003403.GA89393@xor.obsecurity.org> <20051215004547.EAE465D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline In-Reply-To: <20051215004547.EAE465D07@ptavv.es.net> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org, Kris Kennaway Subject: Re: Odd performance problems after upgrade from 4.11 to 6.0-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 00:52:24 -0000 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 14, 2005 at 04:45:47PM -0800, Kevin Oberman wrote: > > Date: Wed, 14 Dec 2005 19:34:04 -0500 > > From: Kris Kennaway > >=20 > > On Wed, Dec 14, 2005 at 04:26:18PM -0800, Kevin Oberman wrote: > >=20 > > > I am attaching a dmesg. I do have a few of drivers (uhci, pcm, psm, > > > atkbd0 and ichsmb) that are still marked as GIANT-LOCKED, but I'm not > > > using the USB very often. And I'm not using pcm or ichsmb during the > > > dump, either. I think everyone has the mouse and keyboard under GIANT, > > > but I can't really see those as a problem, either. > >=20 > > A bunch of things are sharing interrupts with USB..disable it and see > > if that helps. Also check vmstat -i to see if some device is > > storming. If not, turn on MUTEX_PROFILING(9) in your kernel and run > > the dump (or something faster that also exhibits the problem), then > > look for what is contending with Giant. >=20 > Yes, it may be time for MUTEX_PROFILING. I had already looked at > interrupts. My kernel is sans APIC so I didn't really think that > interrupts were a problems and I see: > interrupt total rate > irq0: clk 207037779 1000 > irq1: atkbd0 50208 0 > irq6: fdc0 9 0 > irq8: rtc 26498038 128 > irq10: pcm0 ichsmb0 2 0 > irq11: xl0 uhci0 18076067 87 > irq12: psm0 869500 4 > irq13: npx0 1 0 > irq14: ata0 10423468 50 > irq15: ata1 112 0 > Total 262955184 1270 >=20 > Clearly no storms and nothing looks obviously broken. USB and the > network card share an IRQ, but the USB is not connected to anything and > I would not think that it is generating many interrupts. The network > IS being used and I'm not seeing all that many interrupts on IRQ11. Whenever there is an interrupt on irq11 from the NIC, *both* drivers will wake up to process it. uhci0 will need to acquire Giant. If something else is also trying to acquire Giant (bufdaemon), then they will serialize, degrading performance. This may not be the cause since there are only a few interrupts, but MUTEX_PROFILING will tell you. Kris --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoL4yWry0BWjoQKURAuZFAKDUwuAu9BElsCzvxjV08ew9/a2flACff3eW WOdlC7m365q8eabbq1xSMnU= =ph/3 -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 02:01:58 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEBDA16A428 for ; Thu, 15 Dec 2005 02:01:58 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D24043D45 for ; Thu, 15 Dec 2005 02:01:58 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.41] (asd0.aplus.net [216.55.129.41]) (authenticated bits=0) by pro20.abac.com (8.13.4/8.13.4) with ESMTP id jBF21ukh029029; Wed, 14 Dec 2005 18:01:56 -0800 (PST) (envelope-from atanas@asd.aplus.net) Message-ID: <43A0D070.7020103@asd.aplus.net> Date: Wed, 14 Dec 2005 18:09:52 -0800 From: Atanas User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Jeremy References: <439DE88B.1090407@asd.aplus.net> <20051212214003.GA77268@cirb503493.alcatel.com.au> <439E3894.6060901@asd.aplus.net> <20051213100034.GE77268@cirb503493.alcatel.com.au> In-Reply-To: <20051213100034.GE77268@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 02:01:59 -0000 Peter Jeremy said the following on 12/13/05 02:00: > > Note that PS/2 keyboards aren't hot-pluggable and attempts to do so > can have deleterious effects on your keyboard and/or motherboard. In > any case, the probe/attach sequence relies on the kernel being in a > reasonably sane state (and I'm not sure if it will detect the keyboard > as a console device except at boot time). > I agree, but the keyboard is a passive device (with no power source, i.e. mostly harmless), and it's a standard practice to have only few movable consoles for several racks and plug them in only where it's necessary. It always has been working for us and I don't remember having any hot-plugging accidents for years. > If the keyboard has been plugged in since the system booted, do you > still get the same "no response"? If so, the kernel has wedged at > a fairly low level and I'm not quite sure how to proceed other than > by enabling the sanity checks that other people have mentioned > (eg WITNESS, INVARIANTS) and hoping they catch something. > I cannot say for sure. When the thing happens I'm usually away, and until I go there, the console could have been used by someone. I'm in process of getting a serial console, so if there's no response as well, I will enable the sanity checks. > I only mentioned serial consoles on the off-chance that you had one. > Whilst it may not help here, serial consoles have a number of > advantages when managing remote equipment > Thanks for pointing this. As I said I'm in process of getting one for now, and possibly equipping some dozens of servers with that later. >>After the downgrade we could eventually set a test bed and start >>hammering it with requests. The problem would be how to trigger the >>crash and whether we would be able to reproduce it at all. > I already went to the 5.4 downgrade way. Actually I was forced to do so during the other night, when one of the machines started hanging up in every half an hour or so. Looks like the background fsck on the slower SATA based RAID5 array helped a lot with that. Now I have the test bed online. This is the very same server (SCSI based, with the OS drive intact and production data drives moved elsewhere) that was crashing once a day or so. Hopefully tomorrow I will have a serial console attached to it, so we can start pounding it. I hope this machine won't need to go in production during the next month or so and we'll have enough time for tests. > Depending on your application and the interfaces to it, it might be > feasible to either tee live traffic into both systems and just junk > the responses from your test bed, or "record" live traffic and > replay it into your test bed. > It runs a fairly complex set of services. It's a shared web hosting server handling some hundreds of websites, and also email SMTP/POP3/IMAP, databases MySQL, FTP, DNS, etc. I don't know how easy would be implement such traffic gathering and replaying that on the test bed. It seems kind of complicated at first sight (though I realize it might be the only way to reproduce the crash). We might need some NAT (via ipfw?), some services might not like their responses being junked, etc. I was thinking about trying the kernel stress suite first. Or just have something rsync-ing lots files back and forth (possibly over the network), run apache bench in a loop and point it to some database intensive page, etc. Regards, Atanas From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 02:02:04 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D307516A41F for ; Thu, 15 Dec 2005 02:02:04 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from smtp103.biz.mail.re2.yahoo.com (smtp103.biz.mail.re2.yahoo.com [68.142.229.217]) by mx1.FreeBSD.org (Postfix) with SMTP id A449943D60 for ; Thu, 15 Dec 2005 02:02:03 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: (qmail 50068 invoked from network); 15 Dec 2005 00:06:13 -0000 Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@24.99.22.177 with login) by smtp103.biz.mail.re2.yahoo.com with SMTP; 15 Dec 2005 00:06:13 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 40A1361A4; Wed, 14 Dec 2005 19:06:11 -0500 (EST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 53950-17; Wed, 14 Dec 2005 19:06:10 -0500 (EST) Received: from [127.0.0.1] (optimator [192.168.1.11]) by optimator.noacks.org (Postfix) with ESMTP id C02EA60D5; Wed, 14 Dec 2005 19:06:09 -0500 (EST) Message-ID: <43A0B36D.6090906@alumni.rice.edu> Date: Wed, 14 Dec 2005 19:06:05 -0500 From: Jonathan Noack User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: Scott Long References: <20051214222037.94FEF5D07@ptavv.es.net> <43A0A812.1060104@samsco.org> In-Reply-To: <43A0A812.1060104@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at noacks.org Cc: stable@freebsd.org Subject: Re: Odd performance problems after upgrade from 4.11 to 6.0-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 02:02:05 -0000 Scott Long wrote: > Also, taking out CPU_I586 is usually a bad idea. It offers no > performance penalties (unlike CPU_I386 and maybe CPU_I486), but > enables things like optimized bcopy. Is that documented? In /sys/i386/conf/NOTES I see: # You must specify at least one CPU (the one you intend to run on); # deleting the specification for CPUs you don't need to use may make # parts of the system run faster. # cpu I486_CPU cpu I586_CPU # aka Pentium(tm) cpu I686_CPU # aka Pentium Pro(tm) I've always commented out I486_CPU and I586_CPU. Shouldn't leaving in I686_CPU enable all the features it can use? Do you mean I've spent all these years using un-optimized bcopy?!? -Jonathan From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 03:42:00 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7C3F16A41F for ; Thu, 15 Dec 2005 03:42:00 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from smtp102.biz.mail.re2.yahoo.com (smtp102.biz.mail.re2.yahoo.com [68.142.229.216]) by mx1.FreeBSD.org (Postfix) with SMTP id 11E6043D58 for ; Thu, 15 Dec 2005 03:41:59 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: (qmail 61490 invoked from network); 15 Dec 2005 03:41:58 -0000 Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@24.99.22.177 with login) by smtp102.biz.mail.re2.yahoo.com with SMTP; 15 Dec 2005 03:41:58 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 489E361A4; Wed, 14 Dec 2005 22:41:56 -0500 (EST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 54946-18; Wed, 14 Dec 2005 22:41:55 -0500 (EST) Received: from [192.168.1.9] (bastion.noacks.org [192.168.1.9]) by optimator.noacks.org (Postfix) with ESMTP id 03FBA60D5; Wed, 14 Dec 2005 22:41:54 -0500 (EST) Message-ID: <43A0E607.2030101@alumni.rice.edu> Date: Wed, 14 Dec 2005 22:41:59 -0500 From: Jonathan Noack User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: Kevin Oberman References: <20051215002618.B4D3B5D07@ptavv.es.net> In-Reply-To: <20051215002618.B4D3B5D07@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at noacks.org Cc: stable@freebsd.org Subject: kernel cpu entries (was: Odd performance problems after upgrade from 4.11 to 6.0-Stable) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 03:42:01 -0000 Kevin Oberman wrote: > Scott Long wrote: >> Also, taking out CPU_I586 is usually a bad idea. It offers no >> performance penalties (unlike CPU_I386 and maybe CPU_I486), but >> enables things like optimized bcopy. > > Ahh, This is the sort of thing I never realized. Is there anything in > the handbook that covers this? I had always been under the impression > that CPU_I686 enabled all things that the 686 was capable of. I will > build a new kernel to add that back in. From tuning(7): ************************************************** There are a number of *_CPU options that can be commented out. If you only want the kernel to run on a Pentium class CPU, you can easily remove I486_CPU, but only remove I586_CPU if you are sure your CPU is being recognized as a Pentium II or better. Some clones may be recognized as a Pentium or even a 486 and not be able to boot without those options. If it works, great! The operating system will be able to better use higher-end CPU features for MMU, task switching, timebase, and even device operations... ************************************************** From /sys/i386/conf/NOTES: ************************************************** # You must specify at least one CPU (the one you intend to run on); # deleting the specification for CPUs you don't need to use may make # parts of the system run faster. ************************************************** From npx(4) (also see /sys/i386/i386/support.s): ************************************************** The NPX registers are normally used to optimize copying and zeroing when all of the following conditions are satisfied: 1. cpu I586_CPU is an option ... Then copying and zeroing using the NPX registers is normally 30-100% faster. ************************************************** All is rosy until you see that I586_CPU looks like a loss for blowfish (if you have an i686 CPU): /sys/crypto/blowfish/arch/i386/bf_enc.S As I use AES, I guess I586_CPU is a win for me. Despite this, I think it makes the most sense for I686_CPU to enable the optimized bcopy if it really is a win for i686 CPUs. -Jonathan From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 03:55:16 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 254E416A41F for ; Thu, 15 Dec 2005 03:55:16 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A718A43D5E for ; Thu, 15 Dec 2005 03:55:13 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jBF3t1Ao008333; Wed, 14 Dec 2005 20:55:01 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43A0E916.7070204@samsco.org> Date: Wed, 14 Dec 2005 20:55:02 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: noackjr@alumni.rice.edu References: <20051215002618.B4D3B5D07@ptavv.es.net> <43A0E607.2030101@alumni.rice.edu> In-Reply-To: <43A0E607.2030101@alumni.rice.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: stable@freebsd.org Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 03:55:16 -0000 Jonathan Noack wrote: > Kevin Oberman wrote: > >> Scott Long wrote: >> >>> Also, taking out CPU_I586 is usually a bad idea. It offers no >>> performance penalties (unlike CPU_I386 and maybe CPU_I486), but >>> enables things like optimized bcopy. >> >> >> Ahh, This is the sort of thing I never realized. Is there anything in >> the handbook that covers this? I had always been under the impression >> that CPU_I686 enabled all things that the 686 was capable of. I will >> build a new kernel to add that back in. > > > From tuning(7): > ************************************************** > There are a number of *_CPU options that can be commented out. If you > only want the kernel to run on a Pentium class CPU, you can easily > remove I486_CPU, but only remove I586_CPU if you are sure your CPU is > being recognized as a Pentium II or better. Some clones may be > recognized as a Pentium or even a 486 and not be able to boot without > those options. If it works, great! The operating system will be able > to better use higher-end CPU features for MMU, task switching, timebase, > and even device operations... > ************************************************** > > From /sys/i386/conf/NOTES: > ************************************************** > # You must specify at least one CPU (the one you intend to run on); > # deleting the specification for CPUs you don't need to use may make > # parts of the system run faster. > ************************************************** > > From npx(4) (also see /sys/i386/i386/support.s): > ************************************************** > The NPX registers are normally used to optimize copying and zeroing when > all of the following conditions are satisfied: > 1. cpu I586_CPU is an option > ... > Then copying and zeroing using the NPX registers is normally 30-100% > faster. > ************************************************** > > All is rosy until you see that I586_CPU looks like a loss for blowfish > (if you have an i686 CPU): > /sys/crypto/blowfish/arch/i386/bf_enc.S > > As I use AES, I guess I586_CPU is a win for me. Despite this, I think > it makes the most sense for I686_CPU to enable the optimized bcopy if it > really is a win for i686 CPUs. > > -Jonathan I agree, but frankly I've been loath to touch it out of pure fear of the correctness geeks. I know that if I go near it, someone will point out that it's not 100% correct in all cases of some buggy i686 derivative that hasn't been sold since 1998, and therefore it's better to just leave it alone and satify that .00001% of the problem. Or, the alternate scenario is that people will moan that we should be using SSE instead, and that any change that doesn't involve SSE is wrong and a waste of time. Then a meta-argument will break out over SSE vs SSE2 vs 3DNow, and how again some buggy derivative chip can't use it and can't be detected or worked around. I make my peace by just remembering to leave CPU_I586 enabled on all of my local systems =-) Scott From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 04:05:05 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF88316A41F for ; Thu, 15 Dec 2005 04:05:05 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from smtp101.biz.mail.mud.yahoo.com (smtp101.biz.mail.mud.yahoo.com [68.142.200.236]) by mx1.FreeBSD.org (Postfix) with SMTP id 25D1B43D53 for ; Thu, 15 Dec 2005 04:05:05 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: (qmail 82817 invoked from network); 15 Dec 2005 04:05:04 -0000 Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@24.99.22.177 with login) by smtp101.biz.mail.mud.yahoo.com with SMTP; 15 Dec 2005 04:05:04 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 6AAB861A4; Wed, 14 Dec 2005 23:05:03 -0500 (EST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 55448-15; Wed, 14 Dec 2005 23:05:02 -0500 (EST) Received: from [192.168.1.9] (bastion.noacks.org [192.168.1.9]) by optimator.noacks.org (Postfix) with ESMTP id 2775060D5; Wed, 14 Dec 2005 23:05:02 -0500 (EST) Message-ID: <43A0EB72.8060908@alumni.rice.edu> Date: Wed, 14 Dec 2005 23:05:06 -0500 From: Jonathan Noack User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: Scott Long References: <20051215002618.B4D3B5D07@ptavv.es.net> <43A0E607.2030101@alumni.rice.edu> <43A0E916.7070204@samsco.org> In-Reply-To: <43A0E916.7070204@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at noacks.org Cc: stable@freebsd.org Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 04:05:05 -0000 Scott Long wrote: > Jonathan Noack wrote: >> Kevin Oberman wrote: >>> Scott Long wrote: >>>> Also, taking out CPU_I586 is usually a bad idea. It offers no >>>> performance penalties (unlike CPU_I386 and maybe CPU_I486), but >>>> enables things like optimized bcopy. >>> >>> >>> Ahh, This is the sort of thing I never realized. Is there anything in >>> the handbook that covers this? I had always been under the impression >>> that CPU_I686 enabled all things that the 686 was capable of. I will >>> build a new kernel to add that back in. >> >> >> From tuning(7): >> ************************************************** >> There are a number of *_CPU options that can be commented out. If you >> only want the kernel to run on a Pentium class CPU, you can easily >> remove I486_CPU, but only remove I586_CPU if you are sure your CPU is >> being recognized as a Pentium II or better. Some clones may be >> recognized as a Pentium or even a 486 and not be able to boot without >> those options. If it works, great! The operating system will be able >> to better use higher-end CPU features for MMU, task switching, >> timebase, and even device operations... >> ************************************************** >> >> From /sys/i386/conf/NOTES: >> ************************************************** >> # You must specify at least one CPU (the one you intend to run on); >> # deleting the specification for CPUs you don't need to use may make >> # parts of the system run faster. >> ************************************************** >> >> From npx(4) (also see /sys/i386/i386/support.s): >> ************************************************** >> The NPX registers are normally used to optimize copying and zeroing >> when all of the following conditions are satisfied: >> 1. cpu I586_CPU is an option >> ... >> Then copying and zeroing using the NPX registers is normally 30-100% >> faster. >> ************************************************** >> >> All is rosy until you see that I586_CPU looks like a loss for blowfish >> (if you have an i686 CPU): >> /sys/crypto/blowfish/arch/i386/bf_enc.S >> >> As I use AES, I guess I586_CPU is a win for me. Despite this, I think >> it makes the most sense for I686_CPU to enable the optimized bcopy if >> it really is a win for i686 CPUs. > > I agree, but frankly I've been loath to touch it out of pure fear of the > correctness geeks. I know that if I go near it, someone will point out > that it's not 100% correct in all cases of some buggy i686 derivative > that hasn't been sold since 1998, and therefore it's better to just > leave it alone and satify that .00001% of the problem. Or, the > alternate scenario is that people will moan that we should be using > SSE instead, and that any change that doesn't involve SSE is wrong and > a waste of time. Then a meta-argument will break out over SSE vs SSE2 > vs 3DNow, and how again some buggy derivative chip can't use it and > can't be detected or worked around. I make my peace by just remembering > to leave CPU_I586 enabled on all of my local systems =-) It's even a project idea: http://www.freebsd.org/projects/ideas/#p-memcpy -Jonathan From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 04:10:17 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EABD016A41F for ; Thu, 15 Dec 2005 04:10:16 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [203.96.152.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EE9D43D53 for ; Thu, 15 Dec 2005 04:10:15 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-3.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-1.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IRI00A7CU91A0@linda-1.paradise.net.nz> for stable@freebsd.org; Thu, 15 Dec 2005 17:10:14 +1300 (NZDT) Received: from [192.168.1.11] (218-101-28-129.dsl.clear.net.nz [218.101.28.129]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id 040DB16C6415; Thu, 15 Dec 2005 17:10:09 +1300 (NZDT) Date: Thu, 15 Dec 2005 17:10:07 +1300 From: Mark Kirkwood In-reply-to: <43A0E916.7070204@samsco.org> To: Scott Long Message-id: <43A0EC9F.9080800@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106) References: <20051215002618.B4D3B5D07@ptavv.es.net> <43A0E607.2030101@alumni.rice.edu> <43A0E916.7070204@samsco.org> Cc: stable@freebsd.org Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 04:10:17 -0000 Scott Long wrote: > Jonathan Noack wrote: > >> Kevin Oberman wrote: >> >>> Scott Long wrote: >>> >>>> Also, taking out CPU_I586 is usually a bad idea. It offers no >>>> performance penalties (unlike CPU_I386 and maybe CPU_I486), but >>>> enables things like optimized bcopy. >>> >>> >>> >>> Ahh, This is the sort of thing I never realized. Is there anything in >>> the handbook that covers this? I had always been under the impression >>> that CPU_I686 enabled all things that the 686 was capable of. I will >>> build a new kernel to add that back in. >> >> >> >> From tuning(7): >> ************************************************** >> There are a number of *_CPU options that can be commented out. If you >> only want the kernel to run on a Pentium class CPU, you can easily >> remove I486_CPU, but only remove I586_CPU if you are sure your CPU is >> being recognized as a Pentium II or better. Some clones may be >> recognized as a Pentium or even a 486 and not be able to boot without >> those options. If it works, great! The operating system will be able >> to better use higher-end CPU features for MMU, task switching, >> timebase, and even device operations... >> ************************************************** >> >> From /sys/i386/conf/NOTES: >> ************************************************** >> # You must specify at least one CPU (the one you intend to run on); >> # deleting the specification for CPUs you don't need to use may make >> # parts of the system run faster. >> ************************************************** >> >> From npx(4) (also see /sys/i386/i386/support.s): >> ************************************************** >> The NPX registers are normally used to optimize copying and zeroing >> when all of the following conditions are satisfied: >> 1. cpu I586_CPU is an option >> ... >> Then copying and zeroing using the NPX registers is normally 30-100% >> faster. >> ************************************************** >> >> All is rosy until you see that I586_CPU looks like a loss for blowfish >> (if you have an i686 CPU): >> /sys/crypto/blowfish/arch/i386/bf_enc.S >> >> As I use AES, I guess I586_CPU is a win for me. Despite this, I think >> it makes the most sense for I686_CPU to enable the optimized bcopy if >> it really is a win for i686 CPUs. >> >> -Jonathan > > > I agree, but frankly I've been loath to touch it out of pure fear of the > correctness geeks. I know that if I go near it, someone will point out > that it's not 100% correct in all cases of some buggy i686 derivative > that hasn't been sold since 1998, and therefore it's better to just > leave it alone and satify that .00001% of the problem. Or, the > alternate scenario is that people will moan that we should be using > SSE instead, and that any change that doesn't involve SSE is wrong and > a waste of time. Then a meta-argument will break out over SSE vs SSE2 > vs 3DNow, and how again some buggy derivative chip can't use it and > can't be detected or worked around. I make my peace by just remembering > to leave CPU_I586 enabled on all of my local systems =-) Is a minor update to the handbook needed in order avoid confusion then? e.g. I have been commenting out CPU_I586 on all my PIII systems in the (mistaken it would seem) belief that having CPU_I686 only was better. cheers Mark From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 05:17:23 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 963AB16A41F for ; Thu, 15 Dec 2005 05:17:23 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from smtp102.rog.mail.re2.yahoo.com (smtp102.rog.mail.re2.yahoo.com [206.190.36.80]) by mx1.FreeBSD.org (Postfix) with SMTP id D596F43D49 for ; Thu, 15 Dec 2005 05:17:22 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 16700 invoked from network); 15 Dec 2005 05:17:22 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=KW+X4tZBKAf27gAbiNFWrZQmZQuHNLjUpwkIXoO0ylJwlM5Y/vpjx07DmD79SMYSrklEcNSAv+eRv3xGiTEIWs7oK4JevIZHmBl/rNu7BxVjzlN2lSY9/6fHXG0qoD2HKMF6mVpUjCBSwPzIYsO+i8V6zUoBDDIXAm9z5xOcbTM= ; Received: from unknown (HELO ?172.16.0.199?) (mikej@rogers.com@66.96.18.43 with plain) by smtp102.rog.mail.re2.yahoo.com with SMTP; 15 Dec 2005 05:17:22 -0000 Message-ID: <43A0FC61.3060704@rogers.com> Date: Thu, 15 Dec 2005 00:17:21 -0500 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: Mark Kirkwood References: <20051215002618.B4D3B5D07@ptavv.es.net> <43A0E607.2030101@alumni.rice.edu> <43A0E916.7070204@samsco.org> <43A0EC9F.9080800@paradise.net.nz> In-Reply-To: <43A0EC9F.9080800@paradise.net.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 05:17:23 -0000 Mark Kirkwood wrote: > Is a minor update to the handbook needed in order avoid confusion > then? e.g. I have been commenting out CPU_I586 on all my PIII systems > in the (mistaken it would seem) belief that having CPU_I686 only was > better. Agreed, i have always just used I686, assuming it inherited the features of I586. I think most people will assume this. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 05:31:04 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B73D216A41F for ; Thu, 15 Dec 2005 05:31:04 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from smtp103.biz.mail.re2.yahoo.com (smtp103.biz.mail.re2.yahoo.com [68.142.229.217]) by mx1.FreeBSD.org (Postfix) with SMTP id 1852F43D49 for ; Thu, 15 Dec 2005 05:31:03 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: (qmail 87067 invoked from network); 15 Dec 2005 05:31:03 -0000 Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@24.99.22.177 with login) by smtp103.biz.mail.re2.yahoo.com with SMTP; 15 Dec 2005 05:31:03 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 6103360D9; Thu, 15 Dec 2005 00:31:02 -0500 (EST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00645-01; Thu, 15 Dec 2005 00:31:01 -0500 (EST) Received: from [192.168.1.9] (bastion.noacks.org [192.168.1.9]) by optimator.noacks.org (Postfix) with ESMTP id 1DA3260D4; Thu, 15 Dec 2005 00:31:01 -0500 (EST) Message-ID: <43A0FF9A.6040505@alumni.rice.edu> Date: Thu, 15 Dec 2005 00:31:06 -0500 From: Jonathan Noack User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: Mike Jakubik References: <20051215002618.B4D3B5D07@ptavv.es.net> <43A0E607.2030101@alumni.rice.edu> <43A0E916.7070204@samsco.org> <43A0EC9F.9080800@paradise.net.nz> <43A0FC61.3060704@rogers.com> In-Reply-To: <43A0FC61.3060704@rogers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at noacks.org Cc: stable@freebsd.org, Mark Kirkwood Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 05:31:04 -0000 Mike Jakubik wrote: > Mark Kirkwood wrote: >> Is a minor update to the handbook needed in order avoid confusion >> then? e.g. I have been commenting out CPU_I586 on all my PIII systems >> in the (mistaken it would seem) belief that having CPU_I686 only was >> better. > > Agreed, i have always just used I686, assuming it inherited the features > of I586. I think most people will assume this. A quick benchmark (average of five 'dd' runs sending a large file to /dev/null using a blocksize of 32k) similar to that suggested by Matt Dillon (http://www.freebsd.org/projects/ideas/#p-memcpy) shows ~3% increase with I586_CPU on a dual Pentium III. This was on a lightly loaded live system, but I think it shows that using I586_CPU on an i686 CPU does show a performance improvement (at least in certain tests). I have done no testing with blowfish to see how I586_CPU might affect it as I use AES, but it seems it should be recommended for i686 CPUs as well. -Jonathan From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 05:53:31 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BE5716A445 for ; Thu, 15 Dec 2005 05:53:31 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id E59C043D5A for ; Thu, 15 Dec 2005 05:53:30 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.4) with ESMTP id jBF5uM7Y034289 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 15 Dec 2005 00:56:28 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-stable@freebsd.org Date: Thu, 15 Dec 2005 00:55:32 -0500 User-Agent: KMail/1.8.3 References: <20051215002618.B4D3B5D07@ptavv.es.net> <43A0E607.2030101@alumni.rice.edu> <43A0E916.7070204@samsco.org> In-Reply-To: <43A0E916.7070204@samsco.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart9687671.stBZ66knZu"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512150055.39521.mistry.7@osu.edu> X-Spam-Status: No, score=-4.8 required=5.0 tests=ALL_TRUSTED,BAYES_50, MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.87/1209/Mon Dec 12 10:48:01 2005 on mail.united-ware.com X-Virus-Status: Clean Cc: Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 05:53:31 -0000 --nextPart9687671.stBZ66knZu Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 14 December 2005 10:55 pm, Scott Long wrote: > Jonathan Noack wrote: > > Kevin Oberman wrote: > >> Scott Long wrote: > >>> Also, taking out CPU_I586 is usually a bad idea. It offers no > >>> performance penalties (unlike CPU_I386 and maybe CPU_I486), but > >>> enables things like optimized bcopy. > >> > >> Ahh, This is the sort of thing I never realized. Is there > >> anything in the handbook that covers this? I had always been > >> under the impression that CPU_I686 enabled all things that the > >> 686 was capable of. I will build a new kernel to add that back > >> in. > > > > From tuning(7): > > ************************************************** > > There are a number of *_CPU options that can be commented out.=20 > > If you only want the kernel to run on a Pentium class CPU, you > > can easily remove I486_CPU, but only remove I586_CPU if you are > > sure your CPU is being recognized as a Pentium II or better.=20 > > Some clones may be recognized as a Pentium or even a 486 and not > > be able to boot without those options. If it works, great! The > > operating system will be able to better use higher-end CPU > > features for MMU, task switching, timebase, and even device > > operations... > > ************************************************** > > > > From /sys/i386/conf/NOTES: > > ************************************************** > > # You must specify at least one CPU (the one you intend to run > > on); # deleting the specification for CPUs you don't need to use > > may make # parts of the system run faster. > > ************************************************** > > > > From npx(4) (also see /sys/i386/i386/support.s): > > ************************************************** > > The NPX registers are normally used to optimize copying and > > zeroing when all of the following conditions are satisfied: > > 1. cpu I586_CPU is an option > > ... > > Then copying and zeroing using the NPX registers is normally > > 30-100% faster. > > ************************************************** > > > > All is rosy until you see that I586_CPU looks like a loss for > > blowfish (if you have an i686 CPU): > > /sys/crypto/blowfish/arch/i386/bf_enc.S > > > > As I use AES, I guess I586_CPU is a win for me. Despite this, I > > think it makes the most sense for I686_CPU to enable the > > optimized bcopy if it really is a win for i686 CPUs. > > > > -Jonathan > > I agree, but frankly I've been loath to touch it out of pure fear > of the correctness geeks. I know that if I go near it, someone > will point out that it's not 100% correct in all cases of some > buggy i686 derivative that hasn't been sold since 1998, and > therefore it's better to just leave it alone and satify that > .00001% of the problem. Or, the alternate scenario is that people > will moan that we should be using SSE instead, and that any change > that doesn't involve SSE is wrong and a waste of time. Then a > meta-argument will break out over SSE vs SSE2 vs 3DNow, and how > again some buggy derivative chip can't use it and can't be detected > or worked around. I make my peace by just remembering to leave > CPU_I586 enabled on all of my local systems =3D-) > > Scott I too fall into the "I had no idea!" camp. This seems a bit silly=20 just to satisfy a very small and unknown group of broken chips. =20 Couldn't the optimized bcopy be enabled with I686_CPU, and also an=20 option like NO_OPTIMIZED_BCOPY and an UPDATING entry that would tell=20 those .00001% to make that change so their system doesn't break? =20 Would this be an acceptable solution? =2D-=20 Anish Mistry --nextPart9687671.stBZ66knZu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDoQVbxqA5ziudZT0RAqaxAJ9ngOxxt8M9xhcwj6HIKPtCnw6JQgCfUFBk z4rbAN3ywa5EoxcpG0QTikk= =K6Ov -----END PGP SIGNATURE----- --nextPart9687671.stBZ66knZu-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 06:58:39 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4094B16A41F for ; Thu, 15 Dec 2005 06:58:39 +0000 (GMT) (envelope-from stijn@pcwin002.win.tue.nl) Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.3.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 667E943D5E for ; Thu, 15 Dec 2005 06:58:30 +0000 (GMT) (envelope-from stijn@pcwin002.win.tue.nl) Received: from localhost (localhost [127.0.0.1]) by kweetal.tue.nl (Postfix) with ESMTP id 2BEC013BAB3; Thu, 15 Dec 2005 07:58:27 +0100 (CET) Received: from kweetal.tue.nl ([127.0.0.1]) by localhost (kweetal.tue.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36227-03; Thu, 15 Dec 2005 07:58:26 +0100 (CET) Received: from umta.win.tue.nl (umta.win.tue.nl [131.155.71.100]) by kweetal.tue.nl (Postfix) with ESMTP id A425313BAA0; Thu, 15 Dec 2005 07:58:26 +0100 (CET) Received: from pcwin002.win.tue.nl (pcwin002 [131.155.71.72]) by umta.win.tue.nl (Postfix) with ESMTP id A169131401C; Thu, 15 Dec 2005 07:58:26 +0100 (CET) Received: by pcwin002.win.tue.nl (Postfix, from userid 1001) id 9999340BA; Thu, 15 Dec 2005 07:58:26 +0100 (CET) Date: Thu, 15 Dec 2005 07:58:26 +0100 From: Stijn Hoop To: Mike Jakubik Message-ID: <20051215065826.GY912@pcwin002.win.tue.nl> References: <20051215002618.B4D3B5D07@ptavv.es.net> <43A0E607.2030101@alumni.rice.edu> <43A0E916.7070204@samsco.org> <43A0EC9F.9080800@paradise.net.nz> <43A0FC61.3060704@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43A0FC61.3060704@rogers.com> User-Agent: Mutt/1.4.2.1i X-Bright-Idea: Let's abolish HTML mail! X-Virus-Scanned: amavisd-new at tue.nl Cc: stable@freebsd.org, Mark Kirkwood Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 06:58:39 -0000 On Thu, Dec 15, 2005 at 12:17:21AM -0500, Mike Jakubik wrote: > Mark Kirkwood wrote: > >Is a minor update to the handbook needed in order avoid confusion > >then? e.g. I have been commenting out CPU_I586 on all my PIII systems > >in the (mistaken it would seem) belief that having CPU_I686 only was > >better. > > Agreed, i have always just used I686, assuming it inherited the features > of I586. I think most people will assume this. I did. (just another datapoint) --Stijn -- "I used to think I was indecisive, but now I'm not so sure." From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 07:05:49 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B504F16A41F for ; Thu, 15 Dec 2005 07:05:49 +0000 (GMT) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.FreeBSD.org (Postfix) with SMTP id 9BA9743D5A for ; Thu, 15 Dec 2005 07:05:47 +0000 (GMT) (envelope-from sthaug@nethelp.no) Received: (qmail 30876 invoked from network); 15 Dec 2005 07:05:45 -0000 Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 15 Dec 2005 07:05:45 -0000 Date: Thu, 15 Dec 2005 08:05:45 +0100 (CET) Message-Id: <20051215.080545.74719904.sthaug@nethelp.no> To: markir@paradise.net.nz From: sthaug@nethelp.no In-Reply-To: <43A0EC9F.9080800@paradise.net.nz> References: <43A0E607.2030101@alumni.rice.edu> <43A0E916.7070204@samsco.org> <43A0EC9F.9080800@paradise.net.nz> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 07:05:49 -0000 > Is a minor update to the handbook needed in order avoid confusion then? > e.g. I have been commenting out CPU_I586 on all my PIII systems in the > (mistaken it would seem) belief that having CPU_I686 only was better. I've been doing the same thing myself - removing the CPU_I586 on PIII and newer systems. An update would be good. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 07:25:14 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 782B216A498 for ; Thu, 15 Dec 2005 07:25:14 +0000 (GMT) (envelope-from sperber@deinprogramm.de) Received: from h615406.serverkompetenz.net (h615406.serverkompetenz.net [81.169.143.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id C532C43D5D for ; Thu, 15 Dec 2005 07:25:13 +0000 (GMT) (envelope-from sperber@deinprogramm.de) Received: from h615406.serverkompetenz.net (localhost [127.0.0.1]) by h615406.serverkompetenz.net (Postfix) with ESMTP id 21B7017108 for ; Thu, 15 Dec 2005 08:22:35 +0100 (MET) Received: from Michael-Sperbers-Computer.deinprogramm.de (p54A093A1.dip0.t-ipconnect.de [84.160.147.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by h615406.serverkompetenz.net (Postfix) with ESMTP id C675A17107 for ; Thu, 15 Dec 2005 08:22:34 +0100 (MET) Received: by Michael-Sperbers-Computer.deinprogramm.de (Postfix, from userid 2246) id D908B37E9DC; Thu, 15 Dec 2005 08:25:08 +0100 (CET) Resent-To: freebsd-stable@freebsd.org Resent-From: Michael Sperber Resent-Date: Thu, 15 Dec 2005 08:25:07 +0100 Resent-Message-ID: X-From-Line: nobody Thu Dec 15 08:14:35 2005 From: Michael Sperber Newsgroups: gmane.os.freebsd.stable To: Oliver Fromme References: <200512140832.jBE8W8sZ061841@lurza.secnetix.de> Date: Thu, 15 Dec 2005 08:14:30 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) XEmacs/21.5-b21 (darwin) Cancel-Lock: sha1:57jS3r791vuqNkvIcDS365BH/2o= In-Reply-To: <200512140832.jBE8W8sZ061841@lurza.secnetix.de> (Oliver Fromme's message of "Wed, 14 Dec 2005 09:32:08 +0100 (CET)") MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Lines: 22 Posted-To: gmane.os.freebsd.stable X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: Re: mountd fails intermittently X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 07:25:14 -0000 Oliver Fromme writes: > That looks like your rpcbind(8) process died. Can you > check that with ps? Also, are there any warnings or > errors reported in /var/log/messages? No, it's still running. It shows up in rpcinfo (as does nfsd), and rpcbind itself also replies to pings. In fact, I can usually temporarily fix the problem by killing and restarting mountd. (Not long enough to bring up my clients, though.) (kill -HUP doesn't help, btw.) Moreover, the one client I have that's managed to mount, works. Looking on the 'net, I can see quite a few other people had very similar problems, but nobody's ever posted a reliable fix. (Or anything other than "kill and restart.") Notably: http://www.freebsddiary.org/nfs.php -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 07:42:20 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD5DE16A41F for ; Thu, 15 Dec 2005 07:42:20 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4092F43D5E for ; Thu, 15 Dec 2005 07:42:19 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [195.159.6.24] (ws24.ns5.powertech.no [195.159.6.24]) by smtp1.powertech.no (Postfix) with ESMTP id 07A19867C for ; Thu, 15 Dec 2005 08:40:09 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <22B23729-6168-431E-BC15-CF53E26CCCC3@nordahl.net> References: <22B23729-6168-431E-BC15-CF53E26CCCC3@nordahl.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <92ADBB6B-73F8-4CDB-BE76-7B793EDD0831@nordahl.net> Content-Transfer-Encoding: 7bit From: Frode Nordahl Date: Thu, 15 Dec 2005 08:40:08 +0100 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.746.2) Subject: Re: panic: pmap_enter: invalid page directory pdir=0xc1e063, va=0xffc00000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 07:42:20 -0000 On 4. des. 2005, at 23.44, Frode Nordahl wrote: > Hello, > > After almost 6 months of problem-free operation one of my NFS > servers has suddenly started to panic and do a automatic reboot > regularly, about every 24 hours. > > This is a dual Xeon (with UP kernel for the time being) SE7501HG2 > with 4 GB RAM and a Intel SRCU42X RAID controller (AMI MegaRAID). > > I ran 5.4-RELEASE-p2 on it, but had no kernel.debug for that, so I > installed 5.4-RELEASE-p8 on it to get some information from the > crashes. (See below). I have also installed a UP kernel to rule out > any SMP related problems. > > I found no PRs referencing this exact problem, and no mailinglist > postings addressing this exact problem (well, found one thread > where someone provoked this to happen by tweaking the wrong numbers). > > > My gut feeling tells me that this is a tuning problem, but I really > don't know where to start, so any pointers would be great! > > By habit I have this in my loader.conf: vm.kmem_size_max=419430400 [snip] It turns out this was caused by a erratic backup script. It runs full and incremental backups on two FireWire disks, automatically mounting the second one when the first is full. For some reason the second got full as well and the script ended up remounting the device over 340 times (!) trying to squeze some more bits out of the unwilling device :-) I will set up a test case on a crashbox, rule out that 6.0 has this problem or file a complete pr with test scripts etc. Frode Nordahl frode@nordahl.net From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 08:10:25 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24AC316A41F for ; Thu, 15 Dec 2005 08:10:25 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D37943D55 for ; Thu, 15 Dec 2005 08:10:24 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail07.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBF8AGvt004722 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 15 Dec 2005 19:10:22 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBF8AGHh081019; Thu, 15 Dec 2005 19:10:16 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBF8ABVg081018; Thu, 15 Dec 2005 19:10:11 +1100 (EST) (envelope-from pjeremy) Date: Thu, 15 Dec 2005 19:10:11 +1100 From: Peter Jeremy To: Scott Long Message-ID: <20051215081011.GK77268@cirb503493.alcatel.com.au> References: <20051214222037.94FEF5D07@ptavv.es.net> <43A0A812.1060104@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43A0A812.1060104@samsco.org> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: stable@freebsd.org Subject: Re: Odd performance problems after upgrade from 4.11 to 6.0-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 08:10:25 -0000 On Wed, 2005-Dec-14 16:17:38 -0700, Scott Long wrote: >Also, taking out CPU_I586 is usually a bad idea. It offers no >performance penalties (unlike CPU_I386 and maybe CPU_I486), but >enables things like optimized bcopy. This doesn't quite mesh with my reading of -current and -stable. The following refers only to x86 kernels. Kernel references to {bcopy,bzero,copyin,copyout}() indirect through {bcopy,bzero,copyin,copyout}_vector. This is initialised to generic_{bcopy,bzero,copyin,copyout} in i386/i386/support.s. *_vector is over-ridden with optimised routines as follows: bcopy_vector: - (effectively) never bzero_vector: - i486_bzero if (cpu_class == CPUCLASS_486) in sys/i386/i386/identcpu.c copyin_vector: - (effectively) never copyout_vector: - (effectively) never The i586 optimised routines are defined in sys/i386/i386/support.s but (effectively) never used since v1.101 of sys/i386/isa/npx.c changed '#ifdef I586_CPU' to '#ifdef I586_CPU_XXX' (in 2001/05/22 21:20:49). Even then, they are inside if (cpu_class == CPUCLASS_586) which is not true for P-II and later CPUs. That said, it might be worthwhile revisiting the issue of cpu-specific optimisations. If there is better code then generic_*() for Athlon or P4 CPUs, we should implement it. If there isn't, we can get a (slight) performance improvement by removing the indirection through *_vector - I suspect that CPUs can't predict/pipeline an indirect branch as well as a direct branch. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 09:43:40 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7ABDB16A41F for ; Thu, 15 Dec 2005 09:43:40 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 832F243D4C for ; Thu, 15 Dec 2005 09:43:39 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (jqdovs@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBF9hbok049586 for ; Thu, 15 Dec 2005 10:43:37 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBF9habb049585; Thu, 15 Dec 2005 10:43:36 +0100 (CET) (envelope-from olli) Date: Thu, 15 Dec 2005 10:43:36 +0100 (CET) Message-Id: <200512150943.jBF9habb049585@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: mountd fails intermittently X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 09:43:40 -0000 Michael Sperber wrote: > Oliver Fromme writes: > > That looks like your rpcbind(8) process died. Can you > > check that with ps? Also, are there any warnings or > > errors reported in /var/log/messages? > > No, it's still running. It shows up in rpcinfo (as does nfsd), But mountd does not show up there? > and rpcbind itself also replies to pings. In fact, I can usually > temporarily fix the problem by killing and restarting mountd. (Not > long enough to bring up my clients, though.) (kill -HUP doesn't help, > btw.) Moreover, the one client I have that's managed to mount, works. So it's a failure in mountd. Personally I've never seen such a problem before, even though I'm also running NFS servers under FreeBSD 6 (-release and -stable). Now the one question is: What are the circumstances under which the problem can be reproduced? :-) Of course I'm aware that that's probably a tough question. There are a few possibilities to try to track the problem down. 1. First of all, it might be helpful to see the contents of your /etc/exports. To be honest, I don't think that it is causing the problem, but you never know. 2. Does your mountd log anything to /var/log/messages? 3. What flags are you using with rpcbind and mountd, if any? What flags are you using with the mount command line (i.e. anything unusual)? 4. Please post the output from these commands (preferably before failure and after failure, if possible): # rpcinfo # sockstat | egrep "mountd|rpc" 5. If all else fails, maybe tracing the mountd process during a failing mount attempt might be helpful. Personally I prefer strace (from the ports collection) for the more useful output, but you can also use ktrace which is in the base system. Best regards Oliver PS: If you're sure it's a bug (and not PEBKAC), it might be a good idea to submit a PR containing the information collected so far. -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one?" -- Tom Cargil, C++ Journal From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 09:44:25 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE93316A41F; Thu, 15 Dec 2005 09:44:25 +0000 (GMT) (envelope-from wsk@gddsn.org.cn) Received: from gddsn.org.cn (gddsn.org.cn [218.19.164.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEC3843D53; Thu, 15 Dec 2005 09:44:24 +0000 (GMT) (envelope-from wsk@gddsn.org.cn) Received: from [192.168.168.138] (unknown [192.168.168.138]) by gddsn.org.cn (Postfix) with ESMTP id 66B1A38CB41; Thu, 15 Dec 2005 17:44:22 +0800 (CST) Message-ID: <43A13AF6.90003@gddsn.org.cn> Date: Thu, 15 Dec 2005 17:44:22 +0800 From: wsk User-Agent: Thunderbird 1.5 (X11/20051128) MIME-Version: 1.0 To: current@freebsd.org, hardware@freebsd.org, stable@freebsd.org Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 7bit Cc: Subject: Can support Intel's E8500 chipset on freebsd??? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 09:44:25 -0000 lists: with DELL PE6850, It seems 6.0 Can't support the Intel's E8500 XMB chipset pciconf -lv: none0@pci0:9:0: class=0x050000 card=0x01701028 chip=0x26208086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'E8500 XMB A/B/C/D Identification Registers' class = memory subclass = RAM none1@pci0:9:1: class=0x050000 card=0x01701028 chip=0x26218086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'E8500 XMB A/B/C/D Miscellaneous Registers' class = memory subclass = RAM none2@pci0:9:2: class=0x050000 card=0x01701028 chip=0x26228086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'E8500 XMB A/B/C/D Memory Interleaving Registers' class = memory subclass = RAM dmesg: %dmesg Copyright (c) 1992-2005 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 6.0-RELEASE #0: Fri Dec 16 00:54:34 CST 2005 wsk@wfdb2.gddsn.org.cn:/usr/obj/usr/src/sys/WFDB2 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) MP CPU 3.00GHz (2995.52-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x659d> AMD Features=0x20100800 real memory = 9395240960 (8960 MB) avail memory = 8288649216 (7904 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 cpu2 (AP): APIC ID: 8 cpu3 (AP): APIC ID: 14 ioapic1: Changing APIC ID to 1 ioapic1: WARNING: intbase 32 != expected base 24 ioapic2: Changing APIC ID to 2 ioapic2: WARNING: intbase 64 != expected base 56 ioapic3: Changing APIC ID to 3 ioapic3: WARNING: intbase 96 != expected base 88 ioapic4: Changing APIC ID to 4 ioapic4: WARNING: intbase 128 != expected base 120 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard ioapic2 irqs 64-87 on motherboard ioapic3 irqs 96-119 on motherboard ioapic4 irqs 128-151 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 5 on acpi0 pci_link3: irq 10 on acpi0 pci_link4: on acpi0 pci_link5: on acpi0 pci_link6: on acpi0 pci_link7: irq 3 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 2.0 on pci0 pci4: on pcib2 pcib3: at device 3.0 on pci0 pci7: on pcib3 pcib4: at device 4.0 on pci0 pci8: on pcib4 pcib5: at device 5.0 on pci0 pci11: on pcib5 pcib6: at device 6.0 on pci0 pci14: on pcib6 pcib7: mem 0xdf6ff000-0xdf6fffff at device 0.0 on pci14 pci15: on pcib7 pcib8: at device 0.2 on pci14 pci18: on pcib8 bge0: mem 0xdf8f0000-0xdf8fffff irq 64 at device 2.0 on pci18 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:12:3f:ff:81:47 bge1: mem 0xdf8e0000-0xdf8effff irq 65 at device 2.1 on pci18 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:12:3f:ff:81:48 pcib9: at device 7.0 on pci0 pci19: on pcib9 pcib10: at device 0.0 on pci19 pci20: on pcib10 amr0: mem 0xdd0f0000-0xdd0fffff,0xdf4c0000-0xdf4fffff irq 110 at device 14.0 on pci20 amr0: Firmware 521S, BIOS H430, 256MB RAM pcib11: at device 0.2 on pci19 pci21: on pcib11 pci0: at device 9.0 (no driver attached) pci0: at device 9.1 (no driver attached) pci0: at device 9.2 (no driver attached) pci0: at device 9.3 (no driver attached) pci0: at device 9.4 (no driver attached) pci0: at device 9.5 (no driver attached) pci0: at device 9.6 (no driver attached) pci0: at device 9.7 (no driver attached) pci0: at device 11.0 (no driver attached) pci0: at device 11.1 (no driver attached) pci0: at device 11.2 (no driver attached) pci0: at device 11.3 (no driver attached) pci0: at device 11.4 (no driver attached) pci0: at device 11.5 (no driver attached) pci0: at device 11.6 (no driver attached) pci0: at device 11.7 (no driver attached) pci0: at device 13.0 (no driver attached) pci0: at device 13.1 (no driver attached) pci0: at device 13.2 (no driver attached) pci0: at device 13.3 (no driver attached) pci0: at device 13.4 (no driver attached) pci0: at device 13.5 (no driver attached) pci0: at device 13.6 (no driver attached) pci0: at device 13.7 (no driver attached) pci0: at device 15.0 (no driver attached) pci0: at device 15.1 (no driver attached) pci0: at device 15.2 (no driver attached) pci0: at device 15.3 (no driver attached) pci0: at device 15.4 (no driver attached) pci0: at device 15.5 (no driver attached) pci0: at device 15.6 (no driver attached) pci0: at device 15.7 (no driver attached) uhci0: port 0x6ce0-0x6cff irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x6cc0-0x6cdf irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x6ca0-0x6cbf irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xdff00000-0xdff003ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered uhub4: vendor 0x413c product 0xa001, class 9/0, rev 2.00/0.00, addr 2 uhub4: multiple transaction translators uhub4: 2 ports with 2 removable, self powered pcib12: at device 30.0 on pci0 pci22: on pcib12 pci22: at device 0.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: at iomem 0xc0000-0xc9fff,0xca000-0xcafff,0xcb000-0xcc7ff,0xec000-0xeffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: vendor 0x413c product 0x3010, rev 2.00/2.20, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. ukbd0: Dell Dell USB Keyboard, rev 1.10/2.00, addr 3, iclass 3/1 kbd0 at ukbd0 Timecounters tick every 1.000 msec acd0: DVDROM at ata0-master UDMA33 amrd0: on amr0 amrd0: 1144320MB (2343567360 sectors) RAID 5 (optimal) ses0 at amr0 bus 0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: SAF-TE Compliant Device SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Trying to mount root from ufs:/dev/amrd0s1a bge0: link state changed to UP any ideas?? TIA From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 10:52:04 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8198916A41F for ; Thu, 15 Dec 2005 10:52:04 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BF0A43D5C for ; Thu, 15 Dec 2005 10:52:00 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 1B91F2C90B for ; Thu, 15 Dec 2005 11:51:56 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id 54D9E2C90A for ; Thu, 15 Dec 2005 11:51:55 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 1380B2C906 for ; Thu, 15 Dec 2005 11:51:55 +0100 (CET) From: Massimo Lusetti To: freebsd-stable@freebsd.org Content-Type: text/plain Organization: CEDOC - Modena Date: Thu, 15 Dec 2005 11:51:54 +0100 Message-Id: <1134643915.4304.11.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: tracking multiple machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 10:52:04 -0000 I'm tryng to accomplish this http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/small-lan.html to have four boxes updated toghether. I've done almost everything in the docs and have the main machine, the one who builds world and kernels, do its own work successfully, now with buildworld and buildkernel (all my 4 kernels plus GENERIC) completed i NFS exported /usr/obj and /usr/src to the others. I even finished the procedure (and rebooted) to update to -STABLE the main box without any problem but from a slave machine when i try to : make installkernel KERNCONF=MYNAME I got: ERROR: No kernel "MYNAME" to install. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. But the kernel is present in /usr/obj/usr/src/sys/MYNAME. What so simple I'm missing here? Thanks -- Massimo.run(); From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 11:05:30 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D88B16A41F for ; Thu, 15 Dec 2005 11:05:30 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1A2943D46 for ; Thu, 15 Dec 2005 11:05:29 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so314087wra for ; Thu, 15 Dec 2005 03:05:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=O6MHS49IGSC3VviewE9XTz2yN3aEKS5sUWqqSLXV6cERxEAQx11utz6KDpmMQS7aE75tdJJqutyK/wE1/ZfZ5tbUOUTGiClRC2pNEeV2VN/KRwc2y0kCTd6MlzD6nIhPcmCWFKFa9PhUAbobUOflR1vIUpSxUOD+DAwRB/UfT+w= Received: by 10.65.186.7 with SMTP id n7mr982794qbp; Thu, 15 Dec 2005 02:58:39 -0800 (PST) Received: by 10.65.192.14 with HTTP; Thu, 15 Dec 2005 02:58:39 -0800 (PST) Message-ID: Date: Thu, 15 Dec 2005 11:58:39 +0100 From: Claus Guttesen To: Massimo Lusetti In-Reply-To: <1134643915.4304.11.camel@massimo.datacode.it> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1134643915.4304.11.camel@massimo.datacode.it> Cc: freebsd-stable@freebsd.org Subject: Re: tracking multiple machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 11:05:30 -0000 > I'm tryng to accomplish this > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/small-lan.html > to have four boxes updated toghether. > > I've done almost everything in the docs and have the main machine, the > one who builds world and kernels, do its own work successfully, now with > buildworld and buildkernel (all my 4 kernels plus GENERIC) completed i > NFS exported /usr/obj and /usr/src to the others. > > I even finished the procedure (and rebooted) to update to -STABLE the > main box without any problem but from a slave machine when i try to : > make installkernel KERNCONF=3DMYNAME > > I got: > ERROR: No kernel "MYNAME" to install. > *** Error code 1 > > What so simple I'm missing here? Did you mount /usr/src from the client? regards Claus From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 11:11:50 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2BAF16A41F for ; Thu, 15 Dec 2005 11:11:50 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3192F43D49 for ; Thu, 15 Dec 2005 11:11:49 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 61C1E2C90B for ; Thu, 15 Dec 2005 12:11:48 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id B9FE12C90A; Thu, 15 Dec 2005 12:11:47 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 7EFA02C906; Thu, 15 Dec 2005 12:11:47 +0100 (CET) From: Massimo Lusetti To: Claus Guttesen In-Reply-To: References: <1134643915.4304.11.camel@massimo.datacode.it> Content-Type: text/plain Organization: CEDOC - Modena Date: Thu, 15 Dec 2005 12:11:47 +0100 Message-Id: <1134645107.4304.14.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: tracking multiple machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 11:11:51 -0000 On Thu, 2005-12-15 at 11:58 +0100, Claus Guttesen wrote: > Did you mount /usr/src from the client? Sure, i've mounted both /usr/src and /usr/obj with the same name with maproot options (from exports) -- Massimo.run(); From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 11:21:08 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA4BD16A41F for ; Thu, 15 Dec 2005 11:21:08 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C6DD43D53 for ; Thu, 15 Dec 2005 11:21:07 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (gripyj@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBFBL6Et052749 for ; Thu, 15 Dec 2005 12:21:06 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBFBL6J9052748; Thu, 15 Dec 2005 12:21:06 +0100 (CET) (envelope-from olli) Date: Thu, 15 Dec 2005 12:21:06 +0100 (CET) Message-Id: <200512151121.jBFBL6J9052748@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <1134643915.4304.11.camel@massimo.datacode.it> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: tracking multiple machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 11:21:09 -0000 Massimo Lusetti wrote: > I'm tryng to accomplish this > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/small-lan.html > to have four boxes updated toghether. > [...] > make installkernel KERNCONF=MYNAME > > ERROR: No kernel "MYNAME" to install. > [...] > But the kernel is present in /usr/obj/usr/src/sys/MYNAME. Are the /etc/make.conf files in sync on client and server? Did you mount /usr/src and /usr/obj with -maproot=0? Any other unusual exports or mount options (e.g. noexec)? Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." -- Robert Firth From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 11:28:53 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8151A16A41F for ; Thu, 15 Dec 2005 11:28:53 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C5FB43D5D for ; Thu, 15 Dec 2005 11:28:52 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by zproxy.gmail.com with SMTP id 12so372450nzp for ; Thu, 15 Dec 2005 03:28:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=O1IAryllKt/LysK+myNNuLY82l3NwsWYXv58+clG1CXoJUaO0+454/q/jU70rlG5GC0hptGkjX4WtmMuuvnF9yphxxW+W/ni9suq4gqKijotplGiTBGGx8HSsej6iAKo51R8TaXlSROepOV+HBS68XougawZXgkX2NykD644Ac4= Received: by 10.65.35.10 with SMTP id n10mr987174qbj; Thu, 15 Dec 2005 03:28:51 -0800 (PST) Received: by 10.65.192.14 with HTTP; Thu, 15 Dec 2005 03:28:51 -0800 (PST) Message-ID: Date: Thu, 15 Dec 2005 12:28:51 +0100 From: Claus Guttesen To: freebsd-stable@freebsd.org In-Reply-To: <200512151121.jBFBL6J9052748@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1134643915.4304.11.camel@massimo.datacode.it> <200512151121.jBFBL6J9052748@lurza.secnetix.de> Subject: Re: tracking multiple machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 11:28:53 -0000 > Are the /etc/make.conf files in sync on client and server? > Did you mount /usr/src and /usr/obj with -maproot=3D0? > Any other unusual exports or mount options (e.g. noexec)? It may be the maproot-option. I have the following in my /etc/exports: /usr/obj /usr/ports /usr/src -network=3Dxyz -mask=3Dmy-mask -maproo= t=3Droot I update FreeBSD and the ports-collection via nfs as well. regards Claus From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 12:43:36 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1891916A41F for ; Thu, 15 Dec 2005 12:43:36 +0000 (GMT) (envelope-from rerowe@rerowe.com) Received: from holmes.rerowe.com (holmes.rerowe.com [216.229.6.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7607843D5A for ; Thu, 15 Dec 2005 12:43:33 +0000 (GMT) (envelope-from rerowe@rerowe.com) Received: from [192.168.48.33] (work.rerowe.com [192.168.48.33]) by holmes.rerowe.com (8.13.1/8.13.1) with ESMTP id jBFChLdY031777; Thu, 15 Dec 2005 06:43:22 -0600 (CST) (envelope-from rerowe@rerowe.com) Message-ID: <43A164E8.7040700@rerowe.com> Date: Thu, 15 Dec 2005 06:43:20 -0600 From: Randy Rowe User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: noackjr@alumni.rice.edu References: <20051215002618.B4D3B5D07@ptavv.es.net> <43A0E607.2030101@alumni.rice.edu> In-Reply-To: <43A0E607.2030101@alumni.rice.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Cc: stable@freebsd.org Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 12:43:36 -0000 Jonathan Noack wrote: > Kevin Oberman wrote: > >> Scott Long wrote: >> >>> Also, taking out CPU_I586 is usually a bad idea. It offers no >>> performance penalties (unlike CPU_I386 and maybe CPU_I486), but >>> enables things like optimized bcopy. >> >> >> Ahh, This is the sort of thing I never realized. Is there anything in >> the handbook that covers this? I had always been under the impression >> that CPU_I686 enabled all things that the 686 was capable of. I will >> build a new kernel to add that back in. > > > From tuning(7): > ************************************************** > There are a number of *_CPU options that can be commented out. If you > only want the kernel to run on a Pentium class CPU, you can easily > remove I486_CPU, but only remove I586_CPU if you are sure your CPU is > being recognized as a Pentium II or better. Some clones may be > recognized as a Pentium or even a 486 and not be able to boot without > those options. If it works, great! The operating system will be able > to better use higher-end CPU features for MMU, task switching, > timebase, and even device operations... > ************************************************** > > From /sys/i386/conf/NOTES: > ************************************************** > # You must specify at least one CPU (the one you intend to run on); > # deleting the specification for CPUs you don't need to use may make > # parts of the system run faster. > ************************************************** > > From npx(4) (also see /sys/i386/i386/support.s): > ************************************************** > The NPX registers are normally used to optimize copying and zeroing > when all of the following conditions are satisfied: > 1. cpu I586_CPU is an option > ... > Then copying and zeroing using the NPX registers is normally 30-100% > faster. > ************************************************** > > All is rosy until you see that I586_CPU looks like a loss for blowfish > (if you have an i686 CPU): > /sys/crypto/blowfish/arch/i386/bf_enc.S > > As I use AES, I guess I586_CPU is a win for me. Despite this, I think > it makes the most sense for I686_CPU to enable the optimized bcopy if > it really is a win for i686 CPUs. > > -Jonathan > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" As another entry point here, this is from LINT on 4.x ##################################################################### # CPU OPTIONS # # You must specify at least one CPU (the one you intend to run on); # deleting the specification for CPUs you don't need to use may make # parts of the system run faster. This is especially true removing # I386_CPU. # cpu I386_CPU cpu I486_CPU cpu I586_CPU # aka Pentium(tm) cpu I686_CPU # aka Pentium Pro(tm) I have multiple dual and quad Pentium Pro machines running 4.x that have been remarkably stable using the I686_CPU setting (kudos to the developers!!). So I add myself to the list of those that have been removing the I586_CPU option. Randy From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 12:54:54 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87B1516A41F for ; Thu, 15 Dec 2005 12:54:54 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 810AF43D60 for ; Thu, 15 Dec 2005 12:54:53 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002121924.msg for ; Thu, 15 Dec 2005 12:54:07 +0000 Message-ID: <012101c60176$a0d3ed90$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Randy Rowe" , References: <20051215002618.B4D3B5D07@ptavv.es.net><43A0E607.2030101@alumni.rice.edu> <43A164E8.7040700@rerowe.com> Date: Thu, 15 Dec 2005 12:53:59 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Processed: multiplay.co.uk, Thu, 15 Dec 2005 12:54:07 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: stable@freebsd.org X-MDAV-Processed: multiplay.co.uk, Thu, 15 Dec 2005 12:54:08 +0000 Cc: stable@freebsd.org Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 12:54:54 -0000 Same here be nice to get a catagoric answer to this. Steve ----- Original Message ----- From: "Randy Rowe" > > I have multiple dual and quad Pentium Pro machines running 4.x that have > been > remarkably stable using the I686_CPU setting (kudos to the developers!!). > So I add myself to the list of those that have been removing the > I586_CPU option. ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 13:26:05 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E4DC16A452 for ; Thu, 15 Dec 2005 13:26:05 +0000 (GMT) (envelope-from morten@atreides.freenix.no) Received: from freenix.no (atreides.freenix.no [212.33.142.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E19643D53 for ; Thu, 15 Dec 2005 13:26:03 +0000 (GMT) (envelope-from morten@atreides.freenix.no) Received: from atreides.freenix.no (localhost [127.0.0.1]) by freenix.no (8.13.1/8.13.1) with ESMTP id jBFDQ1rb078240 for ; Thu, 15 Dec 2005 14:26:02 +0100 (CET) (envelope-from morten@atreides.freenix.no) Received: (from morten@localhost) by atreides.freenix.no (8.13.1/8.13.1/Submit) id jBFDPuO6078239 for freebsd-stable@freebsd.org; Thu, 15 Dec 2005 14:25:56 +0100 (CET) (envelope-from morten) Date: Thu, 15 Dec 2005 14:25:56 +0100 From: "Morten A. Middelthon" To: freebsd-stable@freebsd.org Message-ID: <20051215132556.GB74188@freenix.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eJnRUKwClWJh1Khz" Content-Disposition: inline X-PGP-Key: http://freenix.no/~morten/pgp.txt X-PGP-Key-FingerPrint: D48B 5C4E 1590 7DE6 08A0 6539 BECC F62E 829F DF6A X-Operating-System: FreeBSD 4.11-RELEASE-p2 X-Warning: So cunning you could brush your teeth with it. User-Agent: Mutt/1.5.11 Subject: shmget errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 13:26:05 -0000 --eJnRUKwClWJh1Khz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I've seen this problem discussed before on various mailinglists and forums, but never any real solutions.=20 It seems to happen right after a video player, such as totem or mplayer, has crashed. They might crash for different reasons, but the problem afterwards= is always the same.=20 Mplayer will f.ex give you the following error message: X11 error: BadAccess (attempt to access private resource denied) or if I try to start gvim: (gvim:86376): Gdk-WARNING **: shmget failed: error 12 (Cannot allocate memo= ry) or totem: The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadShmSeg (invalid shared segment parameter)'. (Details: serial 31 error_code 166 request_code 147 minor_code 2) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The only common thing with all these applications is gtk, though different versions: ldd `which mplayer`|grep tk libgtk12.so.2 =3D> /usr/X11R6/lib/libgtk12.so.2 (0x289f2000) ldd `which gvim` | grep tk libgtk-x11-2.0.so.0 =3D> /usr/X11R6/lib/libgtk-x11-2.0.so.0 (0x2819= 7000) ldd `which totem` | grep tk libgtk-x11-2.0.so.0 =3D> /usr/X11R6/lib/libgtk-x11-2.0.so.0 (0x2848= 6000) Seems to me that after a program such mplayer or totem crashes something is left behind which blocks future programs from accessing certain resources. = I'm not a programmer, so that is my very limited analysis so far. OS: FreeBSD 5.4-STABLE (built Nov 16 2005) Running XFree86 4.5.0 with Gnome 2.12.1 and nvidia-driver-1.0.7676_1 All gnome/gtk/glib-libs are up-to-date. --=20 Morten A. Middelthon "I have been Foolish and Deluded, and I am a Bear of No Brain at All."=20 -- Pooh --eJnRUKwClWJh1Khz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoW7jvsz2LoKf32oRAmYnAJ0eaSUuTut7rjbpJg66N5EHzCny/QCfYGbz dQkVgq4Q4u1Rd0lwcr4s2d0= =duu4 -----END PGP SIGNATURE----- --eJnRUKwClWJh1Khz-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 13:27:09 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D8FB16A41F for ; Thu, 15 Dec 2005 13:27:09 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66A4243D76 for ; Thu, 15 Dec 2005 13:26:58 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (zuvqlw@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBFDQnRQ056621 for ; Thu, 15 Dec 2005 14:26:50 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBFDQnad056620; Thu, 15 Dec 2005 14:26:49 +0100 (CET) (envelope-from olli) Date: Thu, 15 Dec 2005 14:26:49 +0100 (CET) Message-Id: <200512151326.jBFDQnad056620@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: tracking multiple machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 13:27:09 -0000 Claus Guttesen wrote: > > > Are the /etc/make.conf files in sync on client and server? > > Did you mount /usr/src and /usr/obj with -maproot=0? > > Any other unusual exports or mount options (e.g. noexec)? > > It may be the maproot-option. I have the following in my /etc/exports: > > /usr/obj /usr/ports /usr/src -network=xyz -mask=my-mask -maproot=root I'm not sure if the order is correct. According to the exports(5) manpage, the options (such as -maproot) must be placed before the set of hosts or networks to which the line applies. You might try fixing the order, but actually I think that mountd(8) should log a complaint to /var/log/messages (or whatever your syslog.conf says) if there's an error in your exports file. Best regards Oliver PS: Generic advice: Whenever you "kill -HUP" the mountd process, always check /var/log/messages afterwards. -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "A language that doesn't have everything is actually easier to program in than some that do." -- Dennis M. Ritchie From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 13:29:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22ED716A41F for ; Thu, 15 Dec 2005 13:29:22 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44F7643D5A for ; Thu, 15 Dec 2005 13:29:20 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 20711 invoked from network); 15 Dec 2005 13:29:18 -0000 Received: from unknown (HELO TP51.local) ([pbs]775067@[217.187.181.218]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 15 Dec 2005 13:29:18 -0000 Date: Thu, 15 Dec 2005 14:28:59 +0100 From: Fabian Keil To: Kris Kennaway Message-ID: <20051215142859.1a1bde7f@TP51.local> In-Reply-To: <20051214204349.GA86018@xor.obsecurity.org> References: <20051214132530.3b6daecd@TP51.local> <20051214131855.GH59644@FreeBSD.org> <43A03CFC.6070406@samsco.org> <20051214173234.4bb5ffb9@TP51.local> <20051214204349.GA86018@xor.obsecurity.org> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.6; i386-portbld-freebsd5.4) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_sIJ2313k_DzTQhgabhl=yjp"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.0 panic: kmem_malloc(16384): kmem_map too small: 172728320 total allocated [solved] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 13:29:22 -0000 --Sig_sIJ2313k_DzTQhgabhl=yjp Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Kris Kennaway wrote: > On Wed, Dec 14, 2005 at 05:32:34PM +0100, Fabian Keil wrote: >=20 > > I guess you're right. I can fill a 256MB swap-backed disk without > > panic and without swapping. >=20 > FYI, this is documented in the manpage. I think the panic potential should be mentioned in md(4) as well. I used a script not written by me, the commands used were working and after the panic I only read man md. Of course mdconfig(8) is mentioned twice, but I didn't think I needed more information about it. =20 Fabian --=20 http://www.fabiankeil.de/ --Sig_sIJ2313k_DzTQhgabhl=yjp Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoW+hjV8GA4rMKUQRAiprAKDHHUeISsB/IVpBGtB0haz61e9tOQCg1yGN J+cS3Gm+WY9WZzovsWxOcyU= =eMRo -----END PGP SIGNATURE----- --Sig_sIJ2313k_DzTQhgabhl=yjp-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 13:37:48 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C325416A41F for ; Thu, 15 Dec 2005 13:37:48 +0000 (GMT) (envelope-from morten@atreides.freenix.no) Received: from freenix.no (atreides.freenix.no [212.33.142.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id D300C43D7F for ; Thu, 15 Dec 2005 13:37:31 +0000 (GMT) (envelope-from morten@atreides.freenix.no) Received: from atreides.freenix.no (localhost [127.0.0.1]) by freenix.no (8.13.1/8.13.1) with ESMTP id jBFDbSS0078421 for ; Thu, 15 Dec 2005 14:37:29 +0100 (CET) (envelope-from morten@atreides.freenix.no) Received: (from morten@localhost) by atreides.freenix.no (8.13.1/8.13.1/Submit) id jBFDbNXH078420 for freebsd-stable@freebsd.org; Thu, 15 Dec 2005 14:37:23 +0100 (CET) (envelope-from morten) Date: Thu, 15 Dec 2005 14:37:23 +0100 From: "Morten A. Middelthon" To: freebsd-stable@freebsd.org Message-ID: <20051215133723.GC74188@freenix.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2JFBq9zoW8cOFH7v" Content-Disposition: inline X-PGP-Key: http://freenix.no/~morten/pgp.txt X-PGP-Key-FingerPrint: D48B 5C4E 1590 7DE6 08A0 6539 BECC F62E 829F DF6A X-Operating-System: FreeBSD 4.11-RELEASE-p2 X-Warning: So cunning you could brush your teeth with it. User-Agent: Mutt/1.5.11 Subject: Slightly OT, getting errors from members on this list X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 13:37:48 -0000 --2JFBq9zoW8cOFH7v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Just btw, I just got this message after posting to freebsd-stable@freebsd.org: Subject: Blogger post failed =46rom: postgateway@blogger.com To: morten@freenix.no Date: Thu, 15 Dec 2005 05:32:36 -0800 (PST) Blogger does not accept multipart/signed files. Error code: 7.774C07 Original message: =46rom: morten@freenix.no Date: Thu, 15 Dec 2005 14:25:56 +0100 Subject: shmget errors None Quite annoying. --=20 Morten A. Middelthon Elgureeethm (n: el-gure-a-it-m): Uny methud ooff celcooleshun perffurmed re= peetedly unteel a preeur desured resoolt is prudooced. This .sig has been encheferized - http://flipp.net/bork/ --2JFBq9zoW8cOFH7v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoXGTvsz2LoKf32oRAnHYAJ9IQttbMz8wI/fT5FXfx4q3WMDw0gCgg8bR WoTgzBM8m+FBzrJk1U3yHCw= =71D5 -----END PGP SIGNATURE----- --2JFBq9zoW8cOFH7v-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 14:22:08 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7F3F16A41F for ; Thu, 15 Dec 2005 14:22:08 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39D0F43D4C for ; Thu, 15 Dec 2005 14:22:05 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ojuzmj@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBFEM4vr058513 for ; Thu, 15 Dec 2005 15:22:04 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBFEM4Ei058512; Thu, 15 Dec 2005 15:22:04 +0100 (CET) (envelope-from olli) Date: Thu, 15 Dec 2005 15:22:04 +0100 (CET) Message-Id: <200512151422.jBFEM4Ei058512@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <20051215132556.GB74188@freenix.no> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: shmget errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 14:22:08 -0000 Morten A. Middelthon wrote: > I've seen this problem discussed before on various mailinglists and forums, > but never any real solutions. What you describe is an inherent problem with so-called System-V shared memory (SysV ShMem) which doesn't have a simple solution. But read on for some hints ... SysV IPC (inter-process communication) provides objects to communicate between arbitrary processes: shared memory segments, semaphores and message queues. Those objects are _not_ automatically freed when the process terminates, unlike other resources (such as open files or network sockets). That means: When a process crashes which has opened such SysV IPC object, then those objects will _not_ be freed, but stay around and consume memory. This is not a bug, it's a feature, because those IPV objects are intended to be used by unrelated processes, so a process may later pick up the existing IPC objects and continue working with them. The problem is that those resources are limited. You can put hard limits on the in your kernel configuration. Look for "SYSV IPC" in /sys/conf/NOTES. You can also see the values in ``sysctl kern.ipc'' and via ``ipcs -T''. Of course, you could increase the values, but that puts the limit only a bit further away, but it doesn't remove the problem. Apart from that, the "dead" reasources will take up more and more memory. You can see all IPC object currently existing the ``ipcs'' command. If you have programs that create SysV IPC objects and which are particularly prone to crash often, leaving the objects behind, it might be best to write a small wrapper script which calls the program and then cleans up afterwards. Also, the following shell snippet might be helpful: ipcs | awk '($1=="m"){print $2}' | xargs -n 1 -t ipcrm -m It removes _all_ shared memory segments. Be careful: Don't do that while any programs are still running which use SysV shared memory. You can check that by looking at the output of ``ipcs -p'': If the process IDs listed under the CPID and LPID columns don't exist, chances are that the memory segment isn't in use anymore. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "C is quirky, flawed, and an enormous success." -- Dennis M. Ritchie. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 14:24:07 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8118916A41F for ; Thu, 15 Dec 2005 14:24:07 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7611143D68 for ; Thu, 15 Dec 2005 14:24:01 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (mtuhkt@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBFENupQ058563 for ; Thu, 15 Dec 2005 15:23:56 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBFENucs058562; Thu, 15 Dec 2005 15:23:56 +0100 (CET) (envelope-from olli) Date: Thu, 15 Dec 2005 15:23:56 +0100 (CET) Message-Id: <200512151423.jBFENucs058562@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <43A13AF6.90003@gddsn.org.cn> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: Can support Intel's E8500 chipset on freebsd??? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 14:24:07 -0000 wsk wrote: > with DELL PE6850, It seems 6.0 Can't support the > Intel's E8500 XMB chipset What exactly is the problem? Actually, your dmesg output looks pretty good to me. What are you trying to do which doesn't work for you? Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "When your hammer is C++, everything begins to look like a thumb." -- Steve Haflich, in comp.lang.c++ From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 14:29:51 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75B8716A41F for ; Thu, 15 Dec 2005 14:29:51 +0000 (GMT) (envelope-from morten@atreides.freenix.no) Received: from freenix.no (atreides.freenix.no [212.33.142.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0B6243D6E for ; Thu, 15 Dec 2005 14:29:35 +0000 (GMT) (envelope-from morten@atreides.freenix.no) Received: from atreides.freenix.no (localhost [127.0.0.1]) by freenix.no (8.13.1/8.13.1) with ESMTP id jBFETXm3078999 for ; Thu, 15 Dec 2005 15:29:34 +0100 (CET) (envelope-from morten@atreides.freenix.no) Received: (from morten@localhost) by atreides.freenix.no (8.13.1/8.13.1/Submit) id jBFETSbm078998 for freebsd-stable@freebsd.org; Thu, 15 Dec 2005 15:29:28 +0100 (CET) (envelope-from morten) Date: Thu, 15 Dec 2005 15:29:28 +0100 From: "Morten A. Middelthon" To: freebsd-stable@freebsd.org Message-ID: <20051215142928.GA78879@freenix.no> References: <20051215132556.GB74188@freenix.no> <200512151422.jBFEM4Ei058512@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: <200512151422.jBFEM4Ei058512@lurza.secnetix.de> X-PGP-Key: http://freenix.no/~morten/pgp.txt X-PGP-Key-FingerPrint: D48B 5C4E 1590 7DE6 08A0 6539 BECC F62E 829F DF6A X-Operating-System: FreeBSD 4.11-RELEASE-p2 X-Warning: So cunning you could brush your teeth with it. User-Agent: Mutt/1.5.11 Subject: Re: shmget errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 14:29:51 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 15, 2005 at 03:22:04PM +0100, Oliver Fromme wrote: > Morten A. Middelthon wrote: > > I've seen this problem discussed before on various mailinglists and fo= rums, > > but never any real solutions. >=20 > What you describe is an inherent problem with so-called > System-V shared memory (SysV ShMem) which doesn't have a > simple solution. But read on for some hints ... Hi Olli, long time no see :) Thanks for the very useful information. I now have much more to work with. with regards, --=20 Morten A. Middelthon "There is no reason for any individual to have a computer in their home." -- Ken Olson, President of DEC, World Future Society Convention, 1977 --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoX3Gvsz2LoKf32oRAjiVAKCCbjCQ9r5gO0sg0Awux2cOGtIkAACeMdos BDBGR+CYRL39wIlQocGnEx0= =eQM+ -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 14:36:59 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62DAA16A41F for ; Thu, 15 Dec 2005 14:36:59 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8811A43D49 for ; Thu, 15 Dec 2005 14:36:58 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id C43412C90B for ; Thu, 15 Dec 2005 15:36:56 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id 098632C90A for ; Thu, 15 Dec 2005 15:36:56 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id B58352C906 for ; Thu, 15 Dec 2005 15:36:53 +0100 (CET) From: Massimo Lusetti To: freebsd-stable@freebsd.org In-Reply-To: <200512151121.jBFBL6J9052748@lurza.secnetix.de> References: <200512151121.jBFBL6J9052748@lurza.secnetix.de> Content-Type: text/plain Organization: CEDOC - Modena Date: Thu, 15 Dec 2005 15:36:52 +0100 Message-Id: <1134657412.4481.7.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: tracking multiple machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 14:36:59 -0000 On Thu, 2005-12-15 at 12:21 +0100, Oliver Fromme wrote: > Are the /etc/make.conf files in sync on client and server? Yep, they're empty except the KERNCONF definition > Did you mount /usr/src and /usr/obj with -maproot=0? No, i export them as /usr/src /usr/obj -maproot=root -network=10.0.0.0 -mask=255.255.255.0 > Any other unusual exports or mount options (e.g. noexec)? The options I use are: rw,noauto And no warning/error messages from syslog. I've commented out the KERNCONF definition and used the GENERIC kernel and all went fine... ?! The name of my kernel is spelled correctly. -- Massimo.run(); From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 14:51:58 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99EFA16A41F; Thu, 15 Dec 2005 14:51:58 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B32043D49; Thu, 15 Dec 2005 14:51:57 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3864196 for multiple; Thu, 15 Dec 2005 09:49:56 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jBFEpqRv069483; Thu, 15 Dec 2005 09:51:52 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Thu, 15 Dec 2005 09:52:20 -0500 User-Agent: KMail/1.8.2 References: <43A13AF6.90003@gddsn.org.cn> In-Reply-To: <43A13AF6.90003@gddsn.org.cn> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512150952.22302.jhb@freebsd.org> X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: stable@freebsd.org, current@freebsd.org, wsk , hardware@freebsd.org Subject: Re: Can support Intel's E8500 chipset on freebsd??? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 14:51:58 -0000 On Thursday 15 December 2005 04:44 am, wsk wrote: > lists: > with DELL PE6850, It seems 6.0 Can't support the > Intel's E8500 XMB chipset What doesn't work? > pciconf -lv: > none0@pci0:9:0: class=0x050000 card=0x01701028 chip=0x26208086 rev=0x00 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'E8500 XMB A/B/C/D Identification Registers' > class = memory > subclass = RAM These types of devices don't need a driver to work. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 14:57:45 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB3FD16A424 for ; Thu, 15 Dec 2005 14:57:45 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 939D943DA4 for ; Thu, 15 Dec 2005 14:56:53 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 27797 invoked from network); 15 Dec 2005 14:56:51 -0000 Received: from unknown (HELO TP51.local) ([pbs]775067@[217.187.181.218]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 15 Dec 2005 14:56:51 -0000 Date: Thu, 15 Dec 2005 15:56:27 +0100 From: Fabian Keil To: "Morten A. Middelthon" Message-ID: <20051215155627.563e69fc@TP51.local> In-Reply-To: <20051215133723.GC74188@freenix.no> References: <20051215133723.GC74188@freenix.no> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.6; i386-portbld-freebsd5.4) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_6KmbRORu5ewxf_GdEuWoJ9n; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-stable@freebsd.org Subject: Re: Slightly OT, getting errors from members on this list X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 14:57:46 -0000 --Sig_6KmbRORu5ewxf_GdEuWoJ9n Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "Morten A. Middelthon" wrote: > I just got this message after posting to freebsd-stable@freebsd.org: >=20 > Subject: Blogger post failed > From: postgateway@blogger.com > To: morten@freenix.no > Date: Thu, 15 Dec 2005 05:32:36 -0800 (PST) >=20 > Blogger does not accept multipart/signed files. >=20 > Error code: 7.774C07 You are not alone.=20 http://freebsd.rambler.ru/bsdmail/freebsd-stable_2005/msg08530.html > Quite annoying. And to be allowed to complain, you need a blogger account: http://www.blogger.com/problem.g Do no evil my ass. Fabian --=20 http://www.fabiankeil.de/ --Sig_6KmbRORu5ewxf_GdEuWoJ9n Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoYQnjV8GA4rMKUQRAkxKAKDbU5X7TZenImy1b/HIAJYBQPpxHwCfVIE7 q0eJ+Nz9hBz4Q+O/OeesyMc= =Ky/M -----END PGP SIGNATURE----- --Sig_6KmbRORu5ewxf_GdEuWoJ9n-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 14:59:19 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0ACD16A41F for ; Thu, 15 Dec 2005 14:59:19 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: from sarevok.lan.melvyn.homeunix.org (i153153.upc-i.chello.nl [62.195.153.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8253543D66 for ; Thu, 15 Dec 2005 14:59:16 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: by sarevok.lan.melvyn.homeunix.org (Postfix, from userid 100) id 44D7B11437; Thu, 15 Dec 2005 15:59:07 +0100 (CET) From: Melvyn Sopacua To: freebsd-stable@freebsd.org Date: Thu, 15 Dec 2005 15:59:06 +0100 User-Agent: KMail/1.8.3 References: <200512151121.jBFBL6J9052748@lurza.secnetix.de> <1134657412.4481.7.camel@massimo.datacode.it> In-Reply-To: <1134657412.4481.7.camel@massimo.datacode.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512151559.06253.freebsd.stable@melvyn.homeunix.org> Subject: Re: tracking multiple machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 14:59:20 -0000 On Thursday 15 December 2005 15:36, Massimo Lusetti wrote: > I've commented out the KERNCONF definition and used the GENERIC kernel > and all went fine... ?! > The name of my kernel is spelled correctly. Is the kernconf in /usr/src/sys/i386/conf still there and is it real file (not a symlink to a file on the hostmachine)? -- Melvyn Sopacua freebsd.stable@melvyn.homeunix.org FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 15:11:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7EC516A41F for ; Thu, 15 Dec 2005 15:11:03 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32B0843D58 for ; Thu, 15 Dec 2005 15:11:02 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 1C8032C90B for ; Thu, 15 Dec 2005 16:11:01 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id 55C4C2C90A; Thu, 15 Dec 2005 16:11:00 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 111CD2C906; Thu, 15 Dec 2005 16:11:00 +0100 (CET) From: Massimo Lusetti To: Melvyn Sopacua In-Reply-To: <200512151559.06253.freebsd.stable@melvyn.homeunix.org> References: <200512151121.jBFBL6J9052748@lurza.secnetix.de> <1134657412.4481.7.camel@massimo.datacode.it> <200512151559.06253.freebsd.stable@melvyn.homeunix.org> Content-Type: text/plain Organization: CEDOC - Modena Date: Thu, 15 Dec 2005 16:11:00 +0100 Message-Id: <1134659460.4481.12.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: tracking multiple machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 15:11:03 -0000 On Thu, 2005-12-15 at 15:59 +0100, Melvyn Sopacua wrote: > Is the kernconf in /usr/src/sys/i386/conf still there and is it real file (not > a symlink to a file on the hostmachine)? You're right. I know i miss something stupid. Thanks and sorry for the noise. -- Massimo.run(); From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 15:38:37 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AA0616A41F for ; Thu, 15 Dec 2005 15:38:37 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: from sarevok.lan.melvyn.homeunix.org (i153153.upc-i.chello.nl [62.195.153.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD63543D5C for ; Thu, 15 Dec 2005 15:38:36 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: by sarevok.lan.melvyn.homeunix.org (Postfix, from userid 100) id B251511437; Thu, 15 Dec 2005 16:38:35 +0100 (CET) From: Melvyn Sopacua To: freebsd-stable@freebsd.org Date: Thu, 15 Dec 2005 16:38:33 +0100 User-Agent: KMail/1.8.3 References: <20051215133723.GC74188@freenix.no> <20051215155627.563e69fc@TP51.local> In-Reply-To: <20051215155627.563e69fc@TP51.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512151638.34297.freebsd.stable@melvyn.homeunix.org> Subject: Re: Slightly OT, getting errors from members on this list X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 15:38:37 -0000 On Thursday 15 December 2005 15:56, Fabian Keil wrote: > > From: postgateway@blogger.com > > Quite annoying. $ tail -2 /usr/local/etc/postfix/sender_access postgateway@blogger.com 501 Access denied: Owner not interested in what is broken on your end -- Melvyn Sopacua freebsd.stable@melvyn.homeunix.org FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 17:36:16 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 985B816A41F for ; Thu, 15 Dec 2005 17:36:16 +0000 (GMT) (envelope-from nealie@kobudo.homeunix.net) Received: from neal.nelson.name (neal.nelson.name [82.139.192.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8910B43D45 for ; Thu, 15 Dec 2005 17:36:15 +0000 (GMT) (envelope-from nealie@kobudo.homeunix.net) Received: from [10.0.0.8] (wtibook.home [10.0.0.8]) by neal.nelson.name with esmtp; Thu, 15 Dec 2005 18:36:09 +0100 id 000D4D36.43A1A98A.00000510 In-Reply-To: <43A06BDA.5030602@errno.com> References: <70a5d94afc7213b73c0b44c881c49c76@kobudo.homeunix.net> <43A06BDA.5030602@errno.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Neal Nelson Date: Thu, 15 Dec 2005 18:36:12 +0100 To: Sam Leffler X-Mailer: Apple Mail (2.623) Cc: freebsd-stable@freebsd.org Subject: Re: WPA Access Point X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 17:36:16 -0000 On 14 Dec 2005, at 20:00, Sam Leffler wrote: > Neal Nelson wrote: >> Has anyone got FreeBSD 6.0 to work as a wireless access point using >> WPA? >> I'm running a Prism 2.5 based wireless card and have been using it as >> an access point for years. It stills works OK but I installed the >> hostapd port in order to add WPA authentication. Unfortunately this >> doesn't seem to work as it complains when I run it as follows: >> bsd_configure_wpa: group key cipher=AES-CCM (3) >> ioctl[SIOCS80211]: Invalid argument >> I'm not sure whether hostapd is configured right as there seems to be >> no documentation for it. >> Can anyone shed some light on this or am I barking up the wrong tree >> as far as WPA is concerned? > > The above error is likely because you don't have wlan_ccmp > loaded/configured. However > > ifconfig wi0 list caps > > should indicate the driver lacks support for WPA1/WPA2. Guess it > would be good for hostpad to check that. > > Sam You are quite right on both counts. I built a new kernel with some extra wlan_ options and hostapd runs without complaint now. Of course it still doesn't work as my wi interface doesn't have the WPA capability. On the plus side I've finally managed to configure my system to talk to my Mac with WEP. OK it's not ideal but it's a start and I was unable to get them to talk when I tried it first some time ago. Do you have any idea whether WPA will be added to the wi driver or should I look for another interface card if I want to use this? From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 17:37:22 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A896F16A41F for ; Thu, 15 Dec 2005 17:37:22 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F85543D75 for ; Thu, 15 Dec 2005 17:37:13 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail16.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBFHb5wS002694 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 16 Dec 2005 04:37:07 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBFHb5Hh081844; Fri, 16 Dec 2005 04:37:05 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBFHb4Is081843; Fri, 16 Dec 2005 04:37:04 +1100 (EST) (envelope-from pjeremy) Date: Fri, 16 Dec 2005 04:37:04 +1100 From: Peter Jeremy To: Steven Hartland Message-ID: <20051215173704.GM77268@cirb503493.alcatel.com.au> References: <43A164E8.7040700@rerowe.com> <012101c60176$a0d3ed90$b3db87d4@multiplay.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <012101c60176$a0d3ed90$b3db87d4@multiplay.co.uk> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: Randy Rowe , stable@freebsd.org Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 17:37:22 -0000 On Thu, 2005-Dec-15 12:53:59 -0000, Steven Hartland wrote: >Same here be nice to get a catagoric answer to this. > > Steve >----- Original Message ----- >From: "Randy Rowe" >> >>I have multiple dual and quad Pentium Pro machines running 4.x that have >>been >>remarkably stable using the I686_CPU setting (kudos to the developers!!). >>So I add myself to the list of those that have been removing the >>I586_CPU option. UTSL: The i586 optimised routines were only ever enabled if the CPU was identified as a 586. And these routines have been disabled since mid-2001. See my mail in the "Odd performance problems..." thread for more details. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 17:44:13 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0169016A41F for ; Thu, 15 Dec 2005 17:44:12 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BE4C43D5A for ; Thu, 15 Dec 2005 17:44:11 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail02.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBFHi9PE007440 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 16 Dec 2005 04:44:10 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBFHi9Hh081864 for ; Fri, 16 Dec 2005 04:44:09 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBFHi9X2081863 for freebsd-stable@freebsd.org; Fri, 16 Dec 2005 04:44:09 +1100 (EST) (envelope-from pjeremy) Date: Fri, 16 Dec 2005 04:44:09 +1100 From: Peter Jeremy To: freebsd-stable@freebsd.org Message-ID: <20051215174409.GN77268@cirb503493.alcatel.com.au> References: <20051215132556.GB74188@freenix.no> <200512151422.jBFEM4Ei058512@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512151422.jBFEM4Ei058512@lurza.secnetix.de> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Subject: Re: shmget errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 17:44:13 -0000 On Thu, 2005-Dec-15 15:22:04 +0100, Oliver Fromme wrote: >Also, the following shell snippet might be helpful: > >ipcs | awk '($1=="m"){print $2}' | xargs -n 1 -t ipcrm -m ipca -ma | awk '$9 == "0"{print $2}' | xargs -n 1 -t ipcrm -m has the advantage of only removing segments with no processes attached. >It removes _all_ shared memory segments. Be careful: >Don't do that while any programs are still running which >use SysV shared memory. As with deleting open files, the segment doesn't disappear immediately but only after the last process detaches (see IPC_RMID in shmctm(2)). > You can check that by looking at >the output of ``ipcs -p'': If the process IDs listed under >the CPID and LPID columns don't exist, chances are that the >memory segment isn't in use anymore. Looking at NATTACH in "ipcs -a" is a better approach. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 17:45:38 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5043916A41F for ; Thu, 15 Dec 2005 17:45:38 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal4.es.net (postal4.es.net [198.124.252.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8F7343D6B for ; Thu, 15 Dec 2005 17:45:36 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id IBA74465; Thu, 15 Dec 2005 09:45:35 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id DCDD65D09; Thu, 15 Dec 2005 09:45:33 -0800 (PST) To: Neal Nelson In-reply-to: Your message of "Thu, 15 Dec 2005 18:36:12 +0100." Date: Thu, 15 Dec 2005 09:45:33 -0800 From: "Kevin Oberman" Message-Id: <20051215174533.DCDD65D09@ptavv.es.net> Cc: freebsd-stable@freebsd.org Subject: Re: WPA Access Point X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 17:45:38 -0000 > From: Neal Nelson > Date: Thu, 15 Dec 2005 18:36:12 +0100 > Sender: owner-freebsd-stable@freebsd.org > > On 14 Dec 2005, at 20:00, Sam Leffler wrote: > > > Neal Nelson wrote: > >> Has anyone got FreeBSD 6.0 to work as a wireless access point using > >> WPA? > >> I'm running a Prism 2.5 based wireless card and have been using it as > >> an access point for years. It stills works OK but I installed the > >> hostapd port in order to add WPA authentication. Unfortunately this > >> doesn't seem to work as it complains when I run it as follows: > >> bsd_configure_wpa: group key cipher=AES-CCM (3) > >> ioctl[SIOCS80211]: Invalid argument > >> I'm not sure whether hostapd is configured right as there seems to be > >> no documentation for it. > >> Can anyone shed some light on this or am I barking up the wrong tree > >> as far as WPA is concerned? > > > > The above error is likely because you don't have wlan_ccmp > > loaded/configured. However > > > > ifconfig wi0 list caps > > > > should indicate the driver lacks support for WPA1/WPA2. Guess it > > would be good for hostpad to check that. > > > > Sam > > You are quite right on both counts. I built a new kernel with some > extra wlan_ options and hostapd runs without complaint now. Of course > it still doesn't work as my wi interface doesn't have the WPA > capability. > > On the plus side I've finally managed to configure my system to talk to > my Mac with WEP. OK it's not ideal but it's a start and I was unable to > get them to talk when I tried it first some time ago. > > Do you have any idea whether WPA will be added to the wi driver or > should I look for another interface card if I want to use this? To the best of my knowledge there is no firmware for the Prism2.5 that supports WPA and, without that, I don't think that the driver is going to help. I would love to see if_wi updated to better work with the FreeBSD wlan architecture, but I know that I don't have the time to do it and I would not hold my breath as this chip is getting very long of tooth and probably has not shipped in new hardware for at least two years. I still use it because my laptop has one built-in. I'm due for a new laptop in about a year and I imagine that I will never deal with anything using if_wi after that. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 18:00:08 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCB1A16A41F for ; Thu, 15 Dec 2005 18:00:08 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34A3943D5F for ; Thu, 15 Dec 2005 18:00:04 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.52 (FreeBSD)) id 1EmxOE-0006iZ-A2; Thu, 15 Dec 2005 17:59:38 +0000 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.52 (FreeBSD)) id 1EmxOE-00053V-7l; Thu, 15 Dec 2005 17:59:38 +0000 To: killing@multiplay.co.uk, PeterJeremy@optushome.com.au In-Reply-To: <20051215173704.GM77268@cirb503493.alcatel.com.au> Message-Id: From: Pete French Date: Thu, 15 Dec 2005 17:59:38 +0000 Cc: rerowe@rerowe.com, stable@freebsd.org Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 18:00:08 -0000 > UTSL: The i586 optimised routines were only ever enabled if the CPU > was identified as a 586. And these routines have been disabled since > mid-2001. See my mail in the "Odd performance problems..." thread > for more details. Got some curiuous results when I tested this today by the way. I have a twin processor PIII machine. Did a parallel compile on it. The actuall wall clock time is faster when I add the 586 back in. *but* if you look at the user and system times, the user time has dropped slightly, but the system tme has gone up a lot. So its doing more work, but with a slghtly greater amount of parallelism allow it to finish faster in real time. Can anyone explain that ???? -pete,. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 18:22:55 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC6C916A41F for ; Thu, 15 Dec 2005 18:22:55 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1700643D64 for ; Thu, 15 Dec 2005 18:22:54 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail04.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBFIMpRE025951 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 16 Dec 2005 05:22:52 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBFIMpHh081950; Fri, 16 Dec 2005 05:22:51 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBFIMp8R081949; Fri, 16 Dec 2005 05:22:51 +1100 (EST) (envelope-from pjeremy) Date: Fri, 16 Dec 2005 05:22:51 +1100 From: Peter Jeremy To: Pete French Message-ID: <20051215182250.GO77268@cirb503493.alcatel.com.au> References: <20051215173704.GM77268@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: stable@freebsd.org Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 18:22:55 -0000 On Thu, 2005-Dec-15 17:59:38 +0000, Pete French wrote: >Got some curiuous results when I tested this today by the way. >I have a twin processor PIII machine. Did a parallel compile on >it. The actuall wall clock time is faster when I add the 586 >back in. *but* if you look at the user and system times, the >user time has dropped slightly, but the system tme has gone up >a lot. So its doing more work, but with a slghtly greater amount >of parallelism allow it to finish faster in real time. > >Can anyone explain that ???? I can't see anything in the kernel source code to explain it. Since you don't mention actual times, is the difference statistically significant? (see src/tools/tools/ministat) -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 19:26:00 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE3BA16A423 for ; Thu, 15 Dec 2005 19:26:00 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26CE843D78 for ; Thu, 15 Dec 2005 19:25:47 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.192] ([10.0.0.192]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id jBFJPkA8008346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Dec 2005 11:25:46 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43A1C2FC.6020304@errno.com> Date: Thu, 15 Dec 2005 11:24:44 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Neal Nelson References: <70a5d94afc7213b73c0b44c881c49c76@kobudo.homeunix.net> <43A06BDA.5030602@errno.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: WPA Access Point X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 19:26:01 -0000 Neal Nelson wrote: > On 14 Dec 2005, at 20:00, Sam Leffler wrote: > >> Neal Nelson wrote: >> >>> Has anyone got FreeBSD 6.0 to work as a wireless access point using WPA? >>> I'm running a Prism 2.5 based wireless card and have been using it as >>> an access point for years. It stills works OK but I installed the >>> hostapd port in order to add WPA authentication. Unfortunately this >>> doesn't seem to work as it complains when I run it as follows: >>> bsd_configure_wpa: group key cipher=AES-CCM (3) >>> ioctl[SIOCS80211]: Invalid argument >>> I'm not sure whether hostapd is configured right as there seems to be >>> no documentation for it. >>> Can anyone shed some light on this or am I barking up the wrong tree >>> as far as WPA is concerned? >> >> >> The above error is likely because you don't have wlan_ccmp >> loaded/configured. However >> >> ifconfig wi0 list caps >> >> should indicate the driver lacks support for WPA1/WPA2. Guess it >> would be good for hostpad to check that. >> >> Sam > > > You are quite right on both counts. I built a new kernel with some extra > wlan_ options and hostapd runs without complaint now. Of course it still > doesn't work as my wi interface doesn't have the WPA capability. > > On the plus side I've finally managed to configure my system to talk to > my Mac with WEP. OK it's not ideal but it's a start and I was unable to > get them to talk when I tried it first some time ago. > > Do you have any idea whether WPA will be added to the wi driver or > should I look for another interface card if I want to use this? > > No idea. I consider wi legacy hardware and personally consider it more worthwhile to devote effort to supporting new devices such as Intel cards. OTOH getting wi to support wpa supplicant operation is not a huge amount of work so maybe someone will step up to do it. Sam From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 19:31:00 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8580616A423 for ; Thu, 15 Dec 2005 19:31:00 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2640643D80 for ; Thu, 15 Dec 2005 19:29:56 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.192] ([10.0.0.192]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id jBFJTlA8008379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Dec 2005 11:29:48 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43A1C3ED.5050604@errno.com> Date: Thu, 15 Dec 2005 11:28:45 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20051215174533.DCDD65D09@ptavv.es.net> In-Reply-To: <20051215174533.DCDD65D09@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: WPA Access Point X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 19:31:00 -0000 Kevin Oberman wrote: >>From: Neal Nelson >>Date: Thu, 15 Dec 2005 18:36:12 +0100 >>Sender: owner-freebsd-stable@freebsd.org >> >>On 14 Dec 2005, at 20:00, Sam Leffler wrote: >> >> >>>Neal Nelson wrote: >>> >>>>Has anyone got FreeBSD 6.0 to work as a wireless access point using >>>>WPA? >>>>I'm running a Prism 2.5 based wireless card and have been using it as >>>>an access point for years. It stills works OK but I installed the >>>>hostapd port in order to add WPA authentication. Unfortunately this >>>>doesn't seem to work as it complains when I run it as follows: >>>>bsd_configure_wpa: group key cipher=AES-CCM (3) >>>>ioctl[SIOCS80211]: Invalid argument >>>>I'm not sure whether hostapd is configured right as there seems to be >>>>no documentation for it. >>>>Can anyone shed some light on this or am I barking up the wrong tree >>>>as far as WPA is concerned? >>> >>>The above error is likely because you don't have wlan_ccmp >>>loaded/configured. However >>> >>>ifconfig wi0 list caps >>> >>>should indicate the driver lacks support for WPA1/WPA2. Guess it >>>would be good for hostpad to check that. >>> >>> Sam >> >>You are quite right on both counts. I built a new kernel with some >>extra wlan_ options and hostapd runs without complaint now. Of course >>it still doesn't work as my wi interface doesn't have the WPA >>capability. >> >>On the plus side I've finally managed to configure my system to talk to >>my Mac with WEP. OK it's not ideal but it's a start and I was unable to >>get them to talk when I tried it first some time ago. >> >>Do you have any idea whether WPA will be added to the wi driver or >>should I look for another interface card if I want to use this? > > > To the best of my knowledge there is no firmware for the Prism2.5 that > supports WPA and, without that, I don't think that the driver is going > to help. Sure there is. I believe any rev 1.6.3 or later will do what's needed. Mostly thhis is enable sending host-specific information elements in the management frames and support sending host-encrypted data frames. > > I would love to see if_wi updated to better work with the FreeBSD wlan > architecture, but I know that I don't have the time to do it and I would not > hold my breath as this chip is getting very long of tooth and probably > has not shipped in new hardware for at least two years. I still use it > because my laptop has one built-in. I'm due for a new laptop in about a > year and I imagine that I will never deal with anything using if_wi > after that. Given the cost of cards these days it's easier to just buy a new one. But maybe someone with a vested interest will do the work. I'd like to see it happen and would help but don't have the time to do the work myself. Sam From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 20:05:40 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1A2E16A41F for ; Thu, 15 Dec 2005 20:05:40 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C6D443D64 for ; Thu, 15 Dec 2005 20:05:40 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.52 (FreeBSD)) id 1EmzMB-0009ah-52; Thu, 15 Dec 2005 20:05:39 +0000 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.52 (FreeBSD)) id 1EmzMA-0006Rw-U4; Thu, 15 Dec 2005 20:05:38 +0000 To: PeterJeremy@optushome.com.au In-Reply-To: <20051215182250.GO77268@cirb503493.alcatel.com.au> Message-Id: From: Pete French Date: Thu, 15 Dec 2005 20:05:38 +0000 Cc: stable@freebsd.org Subject: Re: kernel cpu entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 20:05:40 -0000 > I can't see anything in the kernel source code to explain it. Since > you don't mention actual times, is the difference statistically > significant? (see src/tools/tools/ministat) Ministat says: Difference at 95.0% confidence The second set are always smaller than the first set no matter how many times I run it, so it is repeatable. I only wrote down a few of the raw results, but here are a set of three outputs from time (real, user, system) for i686 alone and i586+i686. i686: 496.26 857.54 43.05 501.00 858.03 42.40 517.04 857.90 42.91 i586+i686: 483.70 852.70 51.77 484.93 853.54 50.60 489.26 855.23 46.82 It is a shame I didnt do any without the -j2 on. I suspect that it would show a slowdown, as the user+system times are always lower on the i686 on its own. But when running in parallel you actually get a speedup in elapsed time, even though you are seeing a slowdown on each processor individually. So does adding in i586 somehow increase the potential for parallelism somehow ? Thats the only thing I can think of.... -pete. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 20:49:40 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9926016A420; Thu, 15 Dec 2005 20:49:40 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from skippyii.compar.com (old.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 455AA43D8E; Thu, 15 Dec 2005 20:49:24 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM0011e6ede298.cpe.net.cable.rogers.com [70.28.254.189]) by skippyii.compar.com (8.13.1/8.13.1) with ESMTP id jBFKoQG8027907; Thu, 15 Dec 2005 15:50:38 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <002d01c601b9$206f9940$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: Date: Thu, 15 Dec 2005 15:49:44 -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 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Cc: Scott Long , John Baldwin Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 20:49:40 -0000 >on 30.10.2005 11:36 Uhr Cristiano Deana said the following: >> Hi, >> >> I've seen that 'GENERIC' file has been modified, moving some lines to >> 'DEFAULTS': >> >> device isa >> >> device mem # Memory and kernel memory devices >> device io # I/O device >> >> Why? >> What does it mean? Should we include 'DEFAULTS' in our customized 'GENERIC'? >> Or those lines are no more mandatory? >> > >No, you don't need to include 'DEFAULTS', config(8) will take care of >that for you. > >http://docs.FreeBSD.org/cgi/mid.cgi?200510271713.j9RHDNTo013082 > >AFAICT, this was done in order to automatically include devices which >are essential in most cases so less experienced users won't accidentally >break their systems and later complain that e.g. X doesn't work anymore. > >HTH, > >Phil. I know this has been discussed ad nauseum, but here's my $0.02: Why not mark these entries as 'mandatory' in /usr/src/sys/conf/files* instead? This will cause config to error out if they are not specified in the config, and handles the common case (normal users). . For those power users who really want to disable the devices, we should smarten up the nodevice handling in config(8) to that (nodevice && mandatory) is not an error. Regards, -- Matt Emmerton From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 21:09:49 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 330BC16A41F; Thu, 15 Dec 2005 21:09:49 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8429F43D5F; Thu, 15 Dec 2005 21:09:45 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3892933 for multiple; Thu, 15 Dec 2005 16:07:36 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jBFL9UMW071872; Thu, 15 Dec 2005 16:09:33 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Matt Emmerton" Date: Thu, 15 Dec 2005 16:09:57 -0500 User-Agent: KMail/1.8.2 References: <002d01c601b9$206f9940$1200a8c0@gsicomp.on.ca> In-Reply-To: <002d01c601b9$206f9940$1200a8c0@gsicomp.on.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512151609.58744.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1210/Thu Dec 15 10:23:22 2005 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Scott Long , freebsd-stable@freebsd.org Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 21:09:49 -0000 On Thursday 15 December 2005 03:49 pm, Matt Emmerton wrote: > I know this has been discussed ad nauseum, but here's my $0.02: > > Why not mark these entries as 'mandatory' in /usr/src/sys/conf/files* > instead? > This will cause config to error out if they are not specified in the > config, and handles the common case (normal users). > . > For those power users who really want to disable the devices, we should > smarten up the nodevice handling in config(8) to that (nodevice && > mandatory) is not an error. What happens when you mark some of the files for a device mandatory but not others? How do you make an option that isn't listed in sys/conf/files mandatory? After considering these questions and several others, the conclusion was reached that it was a lot simpler and less error prone to use the same format for defaulting options on or devices on that we use to turn them on in the first place: i.e. a config file. If it really gets peoples panties all up in wads we can move the defaults files to /sys/conf (e.g. sys/conf/DEFAULTS.i386 or even sys/conf/defaults.i386). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 22:03:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FC1A16A420; Thu, 15 Dec 2005 22:03:32 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from skippyii.compar.com (ns1.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id A737B43D95; Thu, 15 Dec 2005 22:03:25 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM0011e6ede298.cpe.net.cable.rogers.com [70.28.254.189]) by skippyii.compar.com (8.13.1/8.13.1) with ESMTP id jBFM4gUh035749; Thu, 15 Dec 2005 17:04:48 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <001f01c601c3$7ba43f50$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: "John Baldwin" References: <002d01c601b9$206f9940$1200a8c0@gsicomp.on.ca> <200512151609.58744.jhb@freebsd.org> Date: Thu, 15 Dec 2005 17:04:02 -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 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Cc: Scott Long , freebsd-stable@freebsd.org Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 22:03:32 -0000 > On Thursday 15 December 2005 03:49 pm, Matt Emmerton wrote: > > I know this has been discussed ad nauseum, but here's my $0.02: > > > > Why not mark these entries as 'mandatory' in /usr/src/sys/conf/files* > > instead? > > This will cause config to error out if they are not specified in the > > config, and handles the common case (normal users). > > . > > For those power users who really want to disable the devices, we should > > smarten up the nodevice handling in config(8) to that (nodevice && > > mandatory) is not an error. > > What happens when you mark some of the files for a device mandatory but not > others? How do you make an option that isn't listed in sys/conf/files > mandatory? After considering these questions and several others, the > conclusion was reached that it was a lot simpler and less error prone to use > the same format for defaulting options on or devices on that we use to turn > them on in the first place: i.e. a config file. If it really gets peoples > panties all up in wads we can move the defaults files to /sys/conf (e.g. > sys/conf/DEFAULTS.i386 or even sys/conf/defaults.i386). Points taken; moving to private e-mail and/or -current for more in-depth discussion. -- Matt Emmerton From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 03:58:15 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78D7016A41F for ; Fri, 16 Dec 2005 03:58:15 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 314D043D62 for ; Fri, 16 Dec 2005 03:58:15 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 1D0E072DDB; Thu, 15 Dec 2005 19:58:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 187F572DD9; Thu, 15 Dec 2005 19:58:15 -0800 (PST) Date: Thu, 15 Dec 2005 19:58:15 -0800 (PST) From: Doug White To: Steven Hartland In-Reply-To: <00e001c600a7$99ec81b0$b3db87d4@multiplay.co.uk> Message-ID: <20051215195730.T96052@carver.gumbysoft.com> References: <00e001c600a7$99ec81b0$b3db87d4@multiplay.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: Problems with ata RAID? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 03:58:15 -0000 On Wed, 14 Dec 2005, Steven Hartland wrote: > Just spotted the following in the logs of one of our machines > There seems to errors across too many disks for it to be disk issues. > Any one seen this before / got any advice? I'd say ad4 went kaboom and is corrupting traffic on its bus, thus the ad5 CRC warnings. (Remember that Parallel ATA drives are master/slave.) > ad4: timeout waiting to issue command > ad4: error issueing WRITE_DMA command > ar0: WARNING - mirror protection lost. RAID0+1 array in DEGRADED mode > ad4: timeout waiting to issue command > ad4: error issueing WRITE_DMA command > ad4: write metadata failed > ad6: req=0xc49b0578 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! > ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2325663 > ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2325695 > ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2325695 > ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2325727 > ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2325632 > ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=393344 > ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=393344 > ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=393344 > ad5: FAILURE - WRITE_DMA status=51 error=84 LBA=393344 > ad4: req=0xc8585258 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! > ad4: req=0xc8585258 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! > ad4: req=0xc8585258 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! > ad4: req=0xc8585258 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! > ad5: FAILURE - SETFEATURES SET TRANSFER MODE status=51 error=4 > ad5: FAILURE - SETFEATURES SET TRANSFER MODE status=51 error=4 > ad5: FAILURE - SETFEATURES ENABLE RCACHE status=51 error=4 > ad5: FAILURE - SETFEATURES ENABLE WCACHE status=51 error=4 > ad5: FAILURE - SET_MULTI status=51 error=4 > ad4: FAILURE - WRITE_DMA timed out LBA=234441585 > ad4: write metadata failed > ad5: FAILURE - WRITE_DMA status=59 error=4 dma=0x06 LBA=234441585 > ad5: write metadata failed > ad6: req=0xc853c190 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! > > [dmesg] > atapci0: port 0xa400-0xa407,0xa800-0xa803,0xac00-0xac07,0xb000-0xb003,0xb400-0xb43f mem > 0xf8120000-0xf813ffff irq 18 at device 12.0 on pci0 > ata2: on atapci0 > ata3: on atapci0 > ad4: 114473MB at ata2-master UDMA100 > ad5: 114473MB at ata2-slave UDMA100 > ad6: 114473MB at ata3-master UDMA100 > ad7: 114473MB at ata3-slave UDMA100 > ar0: 228946MB status: READY > ar0: disk0 READY (master) using ad4 at ata2-master > ar0: disk1 READY (master) using ad5 at ata2-slave > ar0: disk2 READY (mirror) using ad6 at ata3-master > ar0: disk3 READY (mirror) using ad7 at ata3-slave > [/dmesg] > > > > ================================================ > This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. > > In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 > or return the E.mail to postmaster@multiplay.co.uk. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 06:13:18 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58C1516A41F for ; Fri, 16 Dec 2005 06:13:18 +0000 (GMT) (envelope-from freebsd@bitparts.org) Received: from mail.bitparts.org (mail.bitparts.org [66.166.64.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id A61D843D5C for ; Fri, 16 Dec 2005 06:13:17 +0000 (GMT) (envelope-from freebsd@bitparts.org) Received: from [127.0.0.1] (24-107-190-252.dhcp.stls.mo.charter.com [24.107.190.252]) (authenticated bits=0) by mail.bitparts.org (8.13.5/8.13.4) with ESMTP id jBG6DExJ028045 for ; Fri, 16 Dec 2005 00:13:15 -0600 (CST) (envelope-from freebsd@bitparts.org) DomainKey-Signature: a=rsa-sha1; s=mail; d=bitparts.org; c=nofws; q=dns; h=message-id:date:from:user-agent:x-accept-language: mime-version:to:subject:content-type:content-transfer-encoding; b=cLjlTHtMyePrLGJuP/oG0tKW6E1cCWFj09JaSpr38BXwPDvonbok91KsKuyI3RhyO 0Fh++okWAYZlfDpmgnrnqNkfAaoKJhGhc+8I+qvrdePPebqu60lbwGBu6PrzMqFw6QK 4AQ3IDSmqNNYJ7vTlP8yVqgpdXHky6GFxZP7lHA= Message-ID: <43A25AFF.2090501@bitparts.org> Date: Fri, 16 Dec 2005 00:13:19 -0600 From: "J. Buck Caldwell" User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (mail.bitparts.org: authenticated connection) receiver=mail.bitparts.org; client-ip=24.107.190.252; helo=[127.0.0.1]; envelope-from=freebsd@bitparts.org; x-software=spfmilter 0.93 http://www.acme.com/software/spfmilter/; Subject: My ungodly PF config - am I sane and brilliant, or just deluded and dangerous? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 06:13:18 -0000 My company is using FreeBSD for two major applications: our file servers (via Samba), which aren't the subject of this message; and the routers between branches. Some background follows. We have essentially two types of branches - Type A, with thier own cable internet connections, and Type B, who have point-to-point T1 connections to Coprorate and use our internet connection for outside communication. The Type A branches have FreeBSD machines acting as firewall/NAT, and also providing gif endpoints for tunnels to our Corporate office, which also uses a FreeBSD machine to provide firewall/NAT for the Corporate Office and Type B branches. With me so far? Here's the fun part. Our traffic has gotten to the point where I've decided that some traffic shaping (ALTQ) is necessary. I've been experimenting with my home cable internet connection (and gif tunnel to work), and I believe I've come up with a workable solution. However, I'd like to run it by some experts to see if I'm screwing up (or hitting any possible limits) before I try putting it in place live. Here's the config, with some comments/questions int_if = "bge1" # obviously, the Internal interface of our firewall, connected to the corporate internal network ext_if = "bge0" # again, obviously, the external interface, connected to the DMZ, with a publicly routed IP gif_if = "{" gif1 gif3 gif5 gif7 gif10 gif11 gif12 gif13 gif14 gif15 gif19 gif20 gif21 gif25 "}" # all of the gif tunnels to the various branches # options set block-policy return set loginterface $ext_if # scrub scrub in all altq on $ext_if priq bandwidth 4500Kb queue {std_out, ssh_out, mail_out, www_out, notes_out, asna_out, dns_out, gif_out, pri_out} queue std_out priq(default) qlimit 150 queue mail_out priority 2 queue www_out priority 3 queue notes_out priority 4 # We use Notes primarily, so it gets higher priority than normal SMTP/POP3 traffic queue dns_out priority 6 queue ssh_out priority 7 queue gif_out priority 8 # This gets any traffic encapsulated in a gif tunnel or ipsec. queue pri_out priority 15 # nat/rdr nat on $ext_if from $int_if:network to any -> ($ext_if) # it occurs to me, as I post this, that I'll need to change this to account for the Type B branches that are on seperate subnets. # filter rules block all pass quick on lo0 all pass quick on $int_if all pass in quick on $gif_if all # Is there any reason to keep state on any of the following "in" rules? pass in quick on $ext_if proto ipencap all pass in quick on $ext_if proto esp all pass in quick on $ext_if proto tcp all pass in quick on $ext_if proto udp all pass in quick on $ext_if proto icmp all pass out on $gif_if proto udp all keep state queue(std_out, pri_out) pass out on $gif_if proto icmp all keep state queue(std_out, pri_out) pass out on $gif_if proto tcp all modulate state flags S/SA queue(std_out, pri_out) pass out on $gif_if proto tcp from any to any port 22 modulate state flags S/SA queue(ssh_out, pri_out) pass out on $gif_if proto tcp from any to any port 25 modulate state flags S/SA queue(mail_out, pri_out) pass out on $gif_if proto tcp from any to any port 110 modulate state flags S/SA queue(mail_out, pri_out) pass out on $gif_if proto tcp from any to any port 80 modulate state flags S/SA queue(www_out, pri_out) pass out on $gif_if proto tcp from any to any port 443 modulate state flags S/SA queue(www_out, pri_out) pass out on $gif_if proto tcp from any to any port 1352 modulate state flags S/SA queue(notes_out, pri_out) pass out on $gif_if proto udp from any to any port 53 keep state queue(dns_out, pri_out) pass out on $ext_if proto { udp, icmp } all keep state queue(std_out, pri_out) pass out on $ext_if proto tcp all modulate state flags S/SA queue(std_out, pri_out) pass out on $ext_if proto tcp from any to any port 22 modulate state flags S/SA queue(ssh_out, pri_out) pass out on $ext_if proto tcp from any to any port 25 modulate state flags S/SA queue(mail_out, pri_out) pass out on $ext_if proto tcp from any to any port 110 modulate state flags S/SA queue(mail_out, pri_out) pass out on $ext_if proto tcp from any to any port 1352 modulate state flags S/SA queue(notes_out, pri_out) pass out on $ext_if proto tcp from any to any port 80 modulate state flags S/SA queue(www_out, pri_out) pass out on $ext_if proto tcp from any to any port 443 modulate state flags S/SA queue(www_out, pri_out) pass out on $ext_if proto udp from any to any port 53 keep state queue(dns_out, pri_out) pass out on $ext_if proto ipencap all keep state queue(gif_out, pri_out) # Again - any point in keeping state for the gif tunnels or ipsec (below) packets? pass out on $ext_if proto esp all keep state queue(gif_out, pri_out) Believe it or not, pfctl -nv actually parses all of this out and seems to believe it makes sense. The other ends, which usually have only one or possibly two endpoints (branch->corporate and sometimes branch->sister branch) will be significantly simpler, but if the above works, it's easy to transpose to the smaller situation. Something else I just noticed, since this is the "server end" - the point where most of the servers sit, as opposed to the clients - should I change those 'pass' lines from "from any to any port x" to "from any port x to any"? Is that valid? My theory is that I want to first, prioritize the traffic going out on the gif tunnels, then promote the gif packet actually travelling out over the $ext_if above most other traffic. It LOOKS like this will happen, but I want to see if I'm missing anything obvious. In the past, I've used NetBSD and ipfilter, so I'm relitively new to PF and wanted a second opinion. Thanks to anyone for answering, or for pointing to a more appropriate venue for the question! -J. Buck Caldwell From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 07:04:08 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 158A516A41F; Fri, 16 Dec 2005 07:04:08 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12AD843D66; Fri, 16 Dec 2005 07:04:06 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jBG745en016094; Fri, 16 Dec 2005 00:04:05 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43A266E5.3080103@samsco.org> Date: Fri, 16 Dec 2005 00:04:05 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current , stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: Subject: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 07:04:08 -0000 All, The following is the approximate schedule for FreeBSD releases in 2006: Jan 30: Freeze RELENG_5 and RELENG_6 Mar 20: Release FreeBSD 6.1 Apr 3: Release FreeBSD 5.5 Jun 12: Freeze RELENG_6 Jul 31: Release FreeBSD 6.2 Oct 23: Freeze RELENG_6 Dec 11: Release FreeBSD 6.3 A 'freeze' means that the tree will be closed to changes except with specific approval, and the focus will be on producing, testing, and fixing release candidates. The release dates are targets that we hope to make, but we will continue with the policy of only releasing once all of the showstoppers are cleared, i.e. we will release when it is ready. FreeBSD 5 5.5 will be the final release from the RELENG_5 tree. We are doing it to provide support for users who have committed to FreeBSD 5 and who need more time to transition to FreeBSD 6. However, in order to keep forward progress with FreeBSD 6, we will produce this in parallel with the 6.1 release, and thus it will not be our main focus. Users who are using FreeBSD 5 are strongly encouraged to evaluate FreeBSD 6. After this final release, the security team will provide security update support through 2007. FreeBSD 6 There will be three FreeBSD 6 releases in 2006. It will be our primary focus for bugfixes, performance enhancements, and incremental functionality and driver additions. There will likely be one more release in 2007, after which we will begin focus on FreeBSD 7. FreeBSD 7 We will start preparing for FreeBSD 7.0 in June 2007. I'll hopefully update the release engineering pages soon to reflect this. If you have any questions, please feel free to contact me and the rest of the release engineering team. Thanks!ott Scott From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 08:27:08 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F82616A41F; Fri, 16 Dec 2005 08:27:08 +0000 (GMT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AE3843D55; Fri, 16 Dec 2005 08:27:06 +0000 (GMT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (localhost [127.0.0.1]) by tao.thought.org (8.13.1/8.13.1) with ESMTP id jBG8R57Y055040; Fri, 16 Dec 2005 00:27:05 -0800 (PST) (envelope-from kline@tao.thought.org) Received: (from kline@localhost) by tao.thought.org (8.13.1/8.13.1/Submit) id jBG8R4CP055039; Fri, 16 Dec 2005 00:27:04 -0800 (PST) (envelope-from kline) Date: Fri, 16 Dec 2005 00:27:04 -0800 From: Gary Kline To: Scott Long Message-ID: <20051216082704.GA52634@thought.org> References: <43A266E5.3080103@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43A266E5.3080103@samsco.org> User-Agent: Mutt/1.4.2.1i X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing 19 years of service to the Unix community Cc: stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 08:27:08 -0000 On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: > All, > > The following is the approximate schedule for FreeBSD releases in 2006: > > Jan 30: Freeze RELENG_5 and RELENG_6 > Mar 20: Release FreeBSD 6.1 > Apr 3: Release FreeBSD 5.5 > Jun 12: Freeze RELENG_6 > Jul 31: Release FreeBSD 6.2 > Oct 23: Freeze RELENG_6 > Dec 11: Release FreeBSD 6.3 > > A 'freeze' means that the tree will be closed to changes except with > specific approval, and the focus will be on producing, testing, and > fixing release candidates. The release dates are targets that we hope > to make, but we will continue with the policy of only releasing once > all of the showstoppers are cleared, i.e. we will release when it is > ready. > > FreeBSD 5 > 5.5 will be the final release from the RELENG_5 tree. We are doing it > to provide support for users who have committed to FreeBSD 5 and who > need more time to transition to FreeBSD 6. However, in order to keep > forward progress with FreeBSD 6, we will produce this in parallel with > the 6.1 release, and thus it will not be our main focus. Users who are > using FreeBSD 5 are strongly encouraged to evaluate FreeBSD 6. After > this final release, the security team will provide security update > support through 2007. Sounds like an ambitious schedule... All my FBSD servers are at least up to 5.3; my laptop is happy at 5.4. I have what I believe to be a rationalquestion. Why should I go beyond v5.5? More to the point, why can't minor security tweaks be maintained indefinitely for 5.5? What will releases -6 and -7 offer that can;t reasonably be dropped into -5? gary -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 08:35:05 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E8B216A41F; Fri, 16 Dec 2005 08:35:05 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7912543D55; Fri, 16 Dec 2005 08:35:00 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jBG8Ywug016608; Fri, 16 Dec 2005 01:34:59 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43A27C32.6020501@samsco.org> Date: Fri, 16 Dec 2005 01:34:58 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gary Kline References: <43A266E5.3080103@samsco.org> <20051216082704.GA52634@thought.org> In-Reply-To: <20051216082704.GA52634@thought.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 08:35:05 -0000 Gary Kline wrote: > On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: > >>All, >> >>The following is the approximate schedule for FreeBSD releases in 2006: >> >>Jan 30: Freeze RELENG_5 and RELENG_6 >>Mar 20: Release FreeBSD 6.1 >>Apr 3: Release FreeBSD 5.5 >>Jun 12: Freeze RELENG_6 >>Jul 31: Release FreeBSD 6.2 >>Oct 23: Freeze RELENG_6 >>Dec 11: Release FreeBSD 6.3 >> >>A 'freeze' means that the tree will be closed to changes except with >>specific approval, and the focus will be on producing, testing, and >>fixing release candidates. The release dates are targets that we hope >>to make, but we will continue with the policy of only releasing once >>all of the showstoppers are cleared, i.e. we will release when it is >>ready. >> >>FreeBSD 5 >>5.5 will be the final release from the RELENG_5 tree. We are doing it >>to provide support for users who have committed to FreeBSD 5 and who >>need more time to transition to FreeBSD 6. However, in order to keep >>forward progress with FreeBSD 6, we will produce this in parallel with >>the 6.1 release, and thus it will not be our main focus. Users who are >>using FreeBSD 5 are strongly encouraged to evaluate FreeBSD 6. After >>this final release, the security team will provide security update >>support through 2007. > > > Sounds like an ambitious schedule... All my FBSD servers > are at least up to 5.3; my laptop is happy at 5.4. I have > what I believe to be a rationalquestion. Why should I go > beyond v5.5? More to the point, why can't minor security > tweaks be maintained indefinitely for 5.5? Security updates will be maintained for quite a while. However, it takes manpower to test each proposed security change, so it's very hard to justify doing them 'indefinitely'. The stated policy from the security team is 2 years. So they will probably support 5.5 into 2008, but I wanted to be conservative in my statement in case they have different plans. > What will > releases -6 and -7 offer that can;t reasonably be dropped > into -5? Significant performance and stability enhancements that simply cannot be broken up and backported to FreeBSD 5. We are marching towards a 'Giant-less' kernel, which means continuing better SMP performance and better UP responsiveness. With 6.0 we are finally starting to see the benefit of the SMPng work that we've been doing for 5 years. Scott From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 08:44:04 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E17D16A420 for ; Fri, 16 Dec 2005 08:44:04 +0000 (GMT) (envelope-from sperber@deinprogramm.de) Received: from h615406.serverkompetenz.net (h615406.serverkompetenz.net [81.169.143.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id B92C143D66 for ; Fri, 16 Dec 2005 08:43:59 +0000 (GMT) (envelope-from sperber@deinprogramm.de) Received: from h615406.serverkompetenz.net (localhost [127.0.0.1]) by h615406.serverkompetenz.net (Postfix) with ESMTP id 3F25217108; Fri, 16 Dec 2005 09:41:14 +0100 (MET) Received: from Michael-Sperbers-Computer.deinprogramm.de (p54A0931F.dip0.t-ipconnect.de [84.160.147.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by h615406.serverkompetenz.net (Postfix) with ESMTP id 612EF17107; Fri, 16 Dec 2005 09:41:13 +0100 (MET) Received: by Michael-Sperbers-Computer.deinprogramm.de (Postfix, from userid 2246) id 49688380EE7; Fri, 16 Dec 2005 09:43:55 +0100 (CET) From: Michael Sperber To: freebsd-stable@FreeBSD.ORG References: <200512150943.jBF9habb049585@lurza.secnetix.de> Date: Fri, 16 Dec 2005 09:43:54 +0100 In-Reply-To: <200512150943.jBF9habb049585@lurza.secnetix.de> (Oliver Fromme's message of "Thu, 15 Dec 2005 10:43:36 +0100 (CET)") Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) XEmacs/21.5-b21 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Oliver Fromme Subject: Re: mountd fails intermittently X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 08:44:04 -0000 Oliver Fromme writes: > Michael Sperber wrote: > > Oliver Fromme writes: > > > That looks like your rpcbind(8) process died. Can you > > > check that with ps? Also, are there any warnings or > > > errors reported in /var/log/messages? > > > > No, it's still running. It shows up in rpcinfo (as does nfsd), > > But mountd does not show up there? It shows up, too. It just doesn't respond to pings. > Now the one question is: What are the circumstances under > which the problem can be reproduced? :-) Of course I'm > aware that that's probably a tough question. It's pretty reproducible: A mount attempt from my one problematic client will do it. > 1. First of all, it might be helpful to see the contents > of your /etc/exports. To be honest, I don't think that > it is causing the problem, but you never know. /storage/disk1 192.168.1.100 > 2. Does your mountd log anything to /var/log/messages? > No. > 3. What flags are you using with rpcbind and mountd, rpcbind: no flags mountd: -r (but problem shows up without it, too) > if > any? What flags are you using with the mount command > line (i.e. anything unusual)? No flags: mount_nfs matt://storag/disk1 > 4. Please post the output from these commands (preferably > before failure and after failure, if possible): > # rpcinfo > # sockstat | egrep "mountd|rpc" Hrm. I see that just running these commands (on the server) pretty reliably puts it into failure mode. So here's the output from one run: program version netid address service owner 100000 4 tcp 0.0.0.0.0.111 rpcbind superuser 100000 3 tcp 0.0.0.0.0.111 rpcbind superuser 100000 2 tcp 0.0.0.0.0.111 rpcbind superuser 100000 4 udp 0.0.0.0.0.111 rpcbind superuser 100000 3 udp 0.0.0.0.0.111 rpcbind superuser 100000 2 udp 0.0.0.0.0.111 rpcbind superuser 100000 4 tcp6 ::.0.111 rpcbind superuser 100000 3 tcp6 ::.0.111 rpcbind superuser 100000 4 udp6 ::.0.111 rpcbind superuser 100000 3 udp6 ::.0.111 rpcbind superuser 100000 4 local /var/run/rpcbind.sock rpcbind superuser 100000 3 local /var/run/rpcbind.sock rpcbind superuser 100000 2 local /var/run/rpcbind.sock rpcbind superuser 100003 2 udp 0.0.0.0.8.1 nfs superuser 100003 3 udp 0.0.0.0.8.1 nfs superuser 100003 2 udp6 ::.8.1 nfs superuser 100003 3 udp6 ::.8.1 nfs superuser 100003 2 tcp 0.0.0.0.8.1 nfs superuser 100003 3 tcp 0.0.0.0.8.1 nfs superuser 100003 2 tcp6 ::.8.1 nfs superuser 100003 3 tcp6 ::.8.1 nfs superuser 100005 1 udp 0.0.0.0.3.247 mountd superuser 100005 3 udp 0.0.0.0.3.247 mountd superuser 100005 1 tcp 0.0.0.0.2.99 mountd superuser 100005 3 tcp 0.0.0.0.2.99 mountd superuser 100005 1 udp6 ::.3.246 mountd superuser 100005 3 udp6 ::.3.246 mountd superuser 100005 1 tcp6 ::.2.98 mountd superuser 100005 3 tcp6 ::.2.98 mountd superuser root mountd 72379 4 udp4 *:1015 *:* root mountd 72379 7 tcp4 *:611 *:* root mountd 72379 8 udp6 *:1014 *:* root mountd 72379 9 tcp6 *:610 *:* root rpcbind 54162 4 udp6 *:* *:* root rpcbind 54162 7 stream /var/run/rpcbind.sock root rpcbind 54162 8 udp6 *:111 *:* root rpcbind 54162 9 udp6 *:642 *:* root rpcbind 54162 10 tcp6 *:111 *:* root rpcbind 54162 11 udp4 *:111 *:* root rpcbind 54162 12 udp4 *:673 *:* root rpcbind 54162 13 tcp4 *:111 *:* > 5. If all else fails, maybe tracing the mountd process > during a failing mount attempt might be helpful. > Personally I prefer strace (from the ports collection) > for the more useful output, but you can also use ktrace > which is in the base system. I'll try that sometime over the weekend. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 08:57:53 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7397016A41F for ; Fri, 16 Dec 2005 08:57:53 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FB2443D5C for ; Fri, 16 Dec 2005 08:57:52 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (eryjgx@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBG8voIg099759 for ; Fri, 16 Dec 2005 09:57:51 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBG8vol2099758; Fri, 16 Dec 2005 09:57:50 +0100 (CET) (envelope-from olli) Date: Fri, 16 Dec 2005 09:57:50 +0100 (CET) Message-Id: <200512160857.jBG8vol2099758@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <20051216082704.GA52634@thought.org> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 08:57:53 -0000 Gary Kline wrote: > Sounds like an ambitious schedule... All my FBSD servers > are at least up to 5.3; my laptop is happy at 5.4. I have > what I believe to be a rationalquestion. Why should I go > beyond v5.5? Because 6 better, faster, more colorful and more fun. :-) But seriously ... I'm running all my machines at home on RELENG_6 (6-stable by now) for half a year already, especially including my notebook. A lot of things that didn't work with 5.x or required a lot of fiddling now "just run" out of the box with FreeBSD 6, and it also feels a bit faster. Also, power-saving works better, so my notebook runs longer on battery. Stability is the same or even better -- I haven't had a single panic in those six months for which I've been using RELENG_6 (except a few panics upon shutdown, but after syncing the disks so it didn't hurt anything; I guess it's an ACPI issue with that particular mainboard, because it happens only on one of the machines). The upgrade from 5.x to 6.x is completely painless and no more risky or difficult than from 5.3 to 5.4. I've seen reports of a few people who had problems with 6.0, but personally I didn't have any, and I wouldn't want to go back. In fact I can't think of a single reason why I wouldn't upgrade a FreeBSD machine to 6.x. YMMV. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Perl will consistently give you what you want, unless what you want is consistency." -- Larry Wall From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 09:17:14 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FBDA16A41F for ; Fri, 16 Dec 2005 09:17:14 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 614E743D46 for ; Fri, 16 Dec 2005 09:17:13 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 92321 invoked by uid 399); 16 Dec 2005 09:17:12 -0000 Received: from localhost (HELO ?192.168.1.101?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 16 Dec 2005 09:17:12 -0000 Message-ID: <43A28616.8010900@FreeBSD.org> Date: Fri, 16 Dec 2005 01:17:10 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20051203) MIME-Version: 1.0 To: Gary Kline References: <43A266E5.3080103@samsco.org> <20051216082704.GA52634@thought.org> In-Reply-To: <20051216082704.GA52634@thought.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 09:17:14 -0000 Gary Kline wrote: > Sounds like an ambitious schedule... All my FBSD servers > are at least up to 5.3; my laptop is happy at 5.4. I have > what I believe to be a rationalquestion. Why should I go > beyond v5.5? There is one school of thought that says you shouldn't. If it works for you, there is no real need to upgrade. > More to the point, why can't minor security > tweaks be maintained indefinitely for 5.5? We don't support any branch of FreeBSD indefinitely. > What will > releases -6 and -7 offer that can;t reasonably be dropped > into -5? New features that require protocol/ABI changes, etc. for one. For example, I'm working on adding ports/local rc.d scripts to the overall rcorder, and that change won't go back into RELENG_5 because it constitutes a major paradigm shift, and we don't mess with -stable branches in that way. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 10:50:06 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7F7216A41F for ; Fri, 16 Dec 2005 10:50:06 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from web36212.mail.mud.yahoo.com (web36212.mail.mud.yahoo.com [209.191.68.238]) by mx1.FreeBSD.org (Postfix) with SMTP id 0479043D5A for ; Fri, 16 Dec 2005 10:50:05 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: (qmail 68900 invoked by uid 60001); 16 Dec 2005 10:50:05 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Ob8bFG60vHo49DUTOtyOS/WX2iPRat2PAX/LP+H+9XAEkvSyMZzR8jxxFD8KskuEUImGc//C2tR82z4uNx1d1vYCYprG3Mia7Sb3cf8BzseO1+lV25CX5b1DtTxclKR+kPrJt2V5C6jzcycGrVWBuGR4BdUPJ7eFtklL6U9byeg= ; Message-ID: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> Received: from [147.46.44.181] by web36212.mail.mud.yahoo.com via HTTP; Fri, 16 Dec 2005 02:50:05 PST Date: Fri, 16 Dec 2005 02:50:05 -0800 (PST) From: Rob To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 10:50:06 -0000 Gary Kline wrote: > On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: > >>All, >> >>The following is the approximate schedule for FreeBSD releases in 2006: >> >>Jan 30: Freeze RELENG_5 and RELENG_6 >>Mar 20: Release FreeBSD 6.1 >>Apr 3: Release FreeBSD 5.5 >>Jun 12: Freeze RELENG_6 >>Jul 31: Release FreeBSD 6.2 >>Oct 23: Freeze RELENG_6 >>Dec 11: Release FreeBSD 6.3 >> >>A 'freeze' means that the tree will be closed to changes except with >>specific approval, and the focus will be on producing, testing, and >>fixing release candidates. The release dates are targets that we hope >>to make, but we will continue with the policy of only releasing once >>all of the showstoppers are cleared, i.e. we will release when it is >>ready. >> >>FreeBSD 5 >>5.5 will be the final release from the RELENG_5 tree. We are doing it >>to provide support for users who have committed to FreeBSD 5 and who >>need more time to transition to FreeBSD 6. However, in order to keep >>forward progress with FreeBSD 6, we will produce this in parallel with >>the 6.1 release, and thus it will not be our main focus. Users who are >>using FreeBSD 5 are strongly encouraged to evaluate FreeBSD 6. After >>this final release, the security team will provide security update >>support through 2007. > > > Sounds like an ambitious schedule... All my FBSD servers > are at least up to 5.3; my laptop is happy at 5.4. I have > what I believe to be a rationalquestion. Why should I go > beyond v5.5? More to the point, why can't minor security > tweaks be maintained indefinitely for 5.5? What will > releases -6 and -7 offer that can;t reasonably be dropped > into -5? A "me too" here for 5-Stable. I have a test PC, that was running 5-Stable using an additional swapfile to extend swap space. Never any problems at all with 5. After upgrading to 6-stable, I got regular hang-ups of the system (endless loop?) when swapspace is used extensively. Never happened with 5. I wild guess of mine is that there's problem with the 'enhanced filesystem access' in 6. I've reported this issue, and also provided backtraces of kernel dumps, although I'm not an expert in kernel debugging. However, no reponse so far. For me 6, as of now, is not yet as stable as 5 used to be. Regards, Rob. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 11:02:09 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB5EE16A41F for ; Fri, 16 Dec 2005 11:02:09 +0000 (GMT) (envelope-from paulo@nlink.com.br) Received: from smtp.nlink.com.br (smtp.nlink.com.br [201.12.59.3]) by mx1.FreeBSD.org (Postfix) with SMTP id DA73543D58 for ; Fri, 16 Dec 2005 11:02:06 +0000 (GMT) (envelope-from paulo@nlink.com.br) Received: (qmail 85605 invoked from network); 16 Dec 2005 11:02:04 -0000 Received: from unknown (HELO ?201.12.59.126?) (paulo@intra.nlink.com.br@201.12.59.126) by smtp.nlink.com.br with SMTP; 16 Dec 2005 11:02:04 -0000 Message-ID: <43A29E8F.8030101@nlink.com.br> Date: Fri, 16 Dec 2005 08:01:35 -0300 From: Paulo Fragoso User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Diskless /libexec/ld-elf.so.1: Cannot execute objects on / X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 11:02:10 -0000 Hi, After upgrade from FreeBSD 5.3 to FREEBSD_5_4 (cvs), our diskless machines didn't work correctly, many applications using dynamic libraries didn't start, this error was showed: /libexec/ld-elf.so.1: Cannot execute objects on / We found on all diskless machines had MNT_NOEXEC flags set on (fstatfs). After that we have changed rtld.c changed: --- rtld.c.orig Thu Dec 15 17:26:41 2005 +++ rtld.c Thu Dec 15 17:38:15 2005 @@ -1267,7 +1267,7 @@ close(fd); return NULL; } - if (fs.f_flags & MNT_NOEXEC) { + if (fs.f_flags & MNT_NOEXEC && strcmp(fs.f_mntonname,"/") ) { _rtld_error("Cannot execute objects on %s\n", fs.f_mntonname); close(fd); return NULL; Now, all diskless stations works fine. Is there another solution for this case? Thanks, Paulo Fragoso. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 11:31:08 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D14316A41F for ; Fri, 16 Dec 2005 11:31:08 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55AF843D5E for ; Fri, 16 Dec 2005 11:31:06 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002124634.msg for ; Fri, 16 Dec 2005 11:30:40 +0000 Message-ID: <00c801c60234$23fdd330$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Doug White" References: <00e001c600a7$99ec81b0$b3db87d4@multiplay.co.uk> <20051215195730.T96052@carver.gumbysoft.com> Date: Fri, 16 Dec 2005 11:30:34 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Processed: multiplay.co.uk, Fri, 16 Dec 2005 11:30:40 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: multiplay.co.uk, Fri, 16 Dec 2005 11:30:41 +0000 Cc: freebsd-stable@freebsd.org Subject: Re: Problems with ata RAID? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 11:31:08 -0000 ----- Original Message ----- From: "Doug White" Would that also explain the errors on ad6 though? Seems quite strange to be getting errors on 3 out of the 4 disks in the 0+1 array. > I'd say ad4 went kaboom and is corrupting traffic on its bus, thus the ad5 > CRC warnings. (Remember that Parallel ATA drives are master/slave.) > >> ad4: timeout waiting to issue command >> ad4: error issueing WRITE_DMA command >> ar0: WARNING - mirror protection lost. RAID0+1 array in DEGRADED mode >> ad4: timeout waiting to issue command >> ad4: error issueing WRITE_DMA command >> ad4: write metadata failed >> ad6: req=0xc49b0578 WRITE_DMA semaphore timeout !! DANGER Will Robinson !! >> ad5: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2325663 Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 11:31:20 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B95AE16A41F for ; Fri, 16 Dec 2005 11:31:20 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from ms-smtp-03.rdc-nyc.rr.com (ms-smtp-03-smtplb.rdc-nyc.rr.com [24.29.109.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A2BD43D55 for ; Fri, 16 Dec 2005 11:31:20 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from mail.scottro.net (cpe-68-175-68-211.nyc.res.rr.com [68.175.68.211]) by ms-smtp-03.rdc-nyc.rr.com (8.12.10/8.12.7) with ESMTP id jBGBTLME021071 for ; Fri, 16 Dec 2005 06:29:21 -0500 (EST) Received: by mail.scottro.net (Postfix, from userid 1001) id 23CF14181; Fri, 16 Dec 2005 06:31:17 -0500 (EST) Date: Fri, 16 Dec 2005 06:31:17 -0500 From: Scott Robbins To: freebsd-stable@freebsd.org Message-ID: <20051216113117.GA52639@mail.scottro.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> User-Agent: mutt-ng/devel-r581 (FreeBSD) X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 11:31:20 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Dec 16, 2005 at 02:50:05AM -0800, Rob wrote: > Gary Kline wrote: > > On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long > wrote: > > > >>All, > >> > >>The following is the approximate schedule for > FreeBSD releases in 2006: > >> > > Sounds like an ambitious schedule... All my FBSD > servers > > are at least up to 5.3; my laptop is happy at 5.4. > I have > > what I believe to be a rationalquestion. > > A "me too" here for 5-Stable. > > I have a test PC, that was running 5-Stable using an > additional swapfile to extend swap space. Never any > problems at all with 5. > > After upgrading to 6-stable, I got regular hang-ups of > the system (endless loop?) when swapspace is used > extensively. Never happened with 5. I have to add my vote for 6, as did someone else in an earlier post. Like some others, I always found 5.x a bit slower than 4.x (No benchmarks, completely subjective.) From the very beginning, I've found 6.x to be stable and quickly moved some non-critical servers to it. After testing, we moved the more critical servers to it as well, and have been quite happy withe results. Again, completely subjective, but from the beginning 6.x seemed faster and more responsive than 5.x - -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Buffy: Have I ever let you down? Giles: Do you want me to answer that, or shall I just glare? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoqWF+lTVdes0Z9YRAoKhAKCKDOxqSbwz9qwf9HowpmyOP249PwCfbjY0 LjZzXXCn/Jy76/8JA+p+0A4= =yVGK -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 13:16:38 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEB5716A41F for ; Fri, 16 Dec 2005 13:16:38 +0000 (GMT) (envelope-from paulo@nlink.com.br) Received: from smtp.nlink.com.br (smtp.nlink.com.br [201.12.59.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 4769943D8B for ; Fri, 16 Dec 2005 13:16:28 +0000 (GMT) (envelope-from paulo@nlink.com.br) Received: (qmail 3786 invoked from network); 16 Dec 2005 13:16:26 -0000 Received: from unknown (HELO ?201.12.59.126?) (paulo@intra.nlink.com.br@201.12.59.126) by smtp.nlink.com.br with SMTP; 16 Dec 2005 13:16:26 -0000 Message-ID: <43A2BE24.8090905@nlink.com.br> Date: Fri, 16 Dec 2005 10:16:20 -0300 From: Paulo Fragoso User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paulo Fragoso References: <43A29E8F.8030101@nlink.com.br> In-Reply-To: <43A29E8F.8030101@nlink.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Diskless /libexec/ld-elf.so.1: Cannot execute objects on / X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 13:16:38 -0000 Paulo Fragoso wrote: > Hi, > > After upgrade from FreeBSD 5.3 to FREEBSD_5_4 (cvs), our diskless > machines didn't work correctly, many applications using dynamic > libraries didn't start, this error was showed: > > /libexec/ld-elf.so.1: Cannot execute objects on / > > We found on all diskless machines had MNT_NOEXEC flags set on (fstatfs). > After that we have changed rtld.c changed: > Ops, all remote mount points defined with read-only on server has MNT_NOEXEC flag seted on the clients (diskless), is there a bug with fstatfs function? server: /usr/X11R6 -ro -network A.B.C.D -mask 255.255.255.0 client: A.B.C.S:/usr/X11R6 /usr/X11R6 nfs ro,tcp,nfsv3,-w=32768,-r=32768 0 0 On the cliente NFS the /usr/X11R6 has MNT_NOEXEC seted! Paulo Fragoso. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 14:39:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E218616A41F for ; Fri, 16 Dec 2005 14:39:39 +0000 (GMT) (envelope-from ob@gruft.de) Received: from obh.snafu.de (obh.snafu.de [213.73.92.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D11143D73 for ; Fri, 16 Dec 2005 14:39:38 +0000 (GMT) (envelope-from ob@gruft.de) Received: from ob by obh.snafu.de with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EnGkC-000KPd-U2 for freebsd-stable@freebsd.org; Fri, 16 Dec 2005 15:39:36 +0100 Date: Fri, 16 Dec 2005 15:39:36 +0100 From: Oliver Brandmueller To: freebsd-stable@freebsd.org Message-ID: <20051216143936.GF34429@e-Gitt.NET> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Sender: Oliver Brandmueller Subject: NFS UDP mounts on RELENG_6? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 14:39:40 -0000 Hi, I'm experiencing problems when trying to mount NFS filesystems from a RELENG_6 server (FreeBSD hudson 6.0-STABLE FreeBSD 6.0-STABLE #0: Wed Dec 14 16:59:55 CET 2005 root@hudson:/usr/obj/usr/src/sys/NFS-32-FBSD6 i386) to either 5.4-STABLE or 6-STABLE clients. mounting works fine, but afterwards the access to the filesystem on the client stalls. As soon as I mount the FS with a TCP mount everything works as expected. The mounts worked fine on UDP when the server was 5.4-STABLE. There is just a plain GigE switch involved, no firewalls or routing. Anyone else experiencing those problems or having an idea? - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 14:59:12 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BAE716A41F for ; Fri, 16 Dec 2005 14:59:12 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id F302643D5F for ; Fri, 16 Dec 2005 14:59:10 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so511929wxc for ; Fri, 16 Dec 2005 06:59:10 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JuZzbGlLzMBi6b94EsJmvGaC1kXyL4DS1HpQMeYLW+QT4zLS2ylZ3EzIpx4ljttDFEy2zVf9CjIBK3s3x/eM9XojI9iRkGgFOuhIFZKsjClmQCi8J8Tf3FOXHo1A2NdODlH64oQezvXmtfPQ+v6rjswHcZiS0QDInwzcbgiwLRM= Received: by 10.70.44.16 with SMTP id r16mr1010444wxr; Fri, 16 Dec 2005 06:59:09 -0800 (PST) Received: by 10.70.36.7 with HTTP; Fri, 16 Dec 2005 06:59:09 -0800 (PST) Message-ID: <70e8236f0512160659h3379253dw468e5aad3f741002@mail.gmail.com> Date: Fri, 16 Dec 2005 14:59:09 +0000 From: Joao Barros To: Scott Long In-Reply-To: <43A266E5.3080103@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43A266E5.3080103@samsco.org> Cc: stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 14:59:12 -0000 On 12/16/05, Scott Long wrote: > FreeBSD 7 > We will start preparing for FreeBSD 7.0 in June 2007. > > I'll hopefully update the release engineering pages soon to reflect > this. If you have any questions, please feel free to contact me and the > rest of the release engineering team. Thanks!ott There have been some questions on the lists about what to expect from release x.y and I personnally have always looked at the TODO list like http://www.freebsd.org/releases/6.0R/todo.html For 6.0 I noticed there were more updates on that page for bugs and their fixes than for features per se. My sugestion, maybe at a first stage setting the TODO list has it's advantages, one knows what to expect from a release, it's clearly stated and documented there and the developers can see their goals. This is valid for minor and major releases of course. How about it? -- Joao Barros From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 15:31:00 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A209E16A41F for ; Fri, 16 Dec 2005 15:31:00 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07E5743D62 for ; Fri, 16 Dec 2005 15:30:58 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 12209 invoked from network); 16 Dec 2005 15:30:57 -0000 Received: from unknown (HELO TP51.local) ([pbs]775067@[217.187.182.222]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 16 Dec 2005 15:30:57 -0000 Date: Fri, 16 Dec 2005 16:30:31 +0100 From: Fabian Keil To: Oliver Brandmueller Message-ID: <20051216163031.6d5ce939@TP51.local> In-Reply-To: <20051216143936.GF34429@e-Gitt.NET> References: <20051216143936.GF34429@e-Gitt.NET> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.6; i386-portbld-freebsd5.4) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_u7UD/nmEr+6qCiMz2r3/TrX"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-stable@freebsd.org Subject: Re: NFS UDP mounts on RELENG_6? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 15:31:00 -0000 --Sig_u7UD/nmEr+6qCiMz2r3/TrX Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Oliver Brandmueller wrote: > I'm experiencing problems when trying to mount NFS filesystems from a > RELENG_6 server (FreeBSD hudson 6.0-STABLE FreeBSD 6.0-STABLE > #0: Wed Dec 14 16:59:55 CET 2005 =20 > root@hudson:/usr/obj/usr/src/sys/NFS-32-FBSD6 i386) > to either 5.4-STABLE or 6-STABLE clients. mounting works fine, but=20 > afterwards the access to the filesystem on the client stalls. As soon > as I mount the FS with a TCP mount everything works as expected. >=20 > The mounts worked fine on UDP when the server was 5.4-STABLE. There > is just a plain GigE switch involved, no firewalls or routing. >=20 > Anyone else experiencing those problems or having an idea? I just copied some files (<200 MB) from a NFS Server running FreeBSD africanqueen.local 6.0-STABLE FreeBSD 6.0-STABLE #5: Thu Dec 15 19:31:12 CET 2005 fk@africanqueen.local:/usr/obj/usr/src/sys/AFRICANQUEEN i386 without problems. My client runs FreeBSD 5.4, I use GigE as well, but no switch. Fabian --=20 http://www.fabiankeil.de/ --Sig_u7UD/nmEr+6qCiMz2r3/TrX Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDot2ljV8GA4rMKUQRAv/4AKCv+OOGyuUlPhZ6kPOET2+uJLouFgCeLDTy 9G5AmiBkgCmK9ISBeQaJvZQ= =wq/F -----END PGP SIGNATURE----- --Sig_u7UD/nmEr+6qCiMz2r3/TrX-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 16:30:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D17C616A41F for ; Fri, 16 Dec 2005 16:30:03 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E2FE43D4C for ; Fri, 16 Dec 2005 16:30:00 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 846ABB80F for ; Fri, 16 Dec 2005 11:29:54 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <43A25AFF.2090501@bitparts.org> References: <43A25AFF.2090501@bitparts.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <28458AB8-854C-475A-8CF4-8BE979C0794D@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Fri, 16 Dec 2005 11:29:52 -0500 To: freebsd-stable X-Mailer: Apple Mail (2.746.2) Subject: Re: My ungodly PF config - am I sane and brilliant, or just deluded and dangerous? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 16:30:04 -0000 On Dec 16, 2005, at 1:13 AM, J. Buck Caldwell wrote: > Here's the fun part. Our traffic has gotten to the point where I've > decided that some traffic shaping (ALTQ) is necessary. I've been > experimenting with my home cable internet connection (and gif > tunnel to work), and I believe I've come up with a workable > solution. However, I'd like to run it by some experts to see if I'm > screwing up (or hitting any possible limits) before I try putting > it in place live. You may wish to take a look at an embedded GUI based firewall system like pfSense to help you configure this. It has a traffic shaping wizard and can do IPsec VPNs as well. It is based on FreeBSD 6.0 so will run on whatever hardware you've got already. See http://www.pfsense.com/ From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 16:45:29 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C332716A41F for ; Fri, 16 Dec 2005 16:45:29 +0000 (GMT) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0703543D77 for ; Fri, 16 Dec 2005 16:45:22 +0000 (GMT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.13.4/8.13.4) with ESMTP id jBGGjMsW069078 for ; Fri, 16 Dec 2005 08:45:22 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.13.4/8.13.4) with ESMTP id jBGGjL5F079871 for ; Fri, 16 Dec 2005 08:45:21 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.13.4/8.13.4/Submit) id jBGGjKt0079870 for freebsd-stable@freebsd.org; Fri, 16 Dec 2005 08:45:20 -0800 (PST) (envelope-from frank@exit.com) X-Authentication-Warning: realtime.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: freebsd-stable@freebsd.org In-Reply-To: <200512160857.jBG8vol2099758@lurza.secnetix.de> References: <200512160857.jBG8vol2099758@lurza.secnetix.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Fri, 16 Dec 2005 08:45:20 -0800 Message-Id: <1134751520.79824.2.camel@realtime.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.87.1/1210/Thu Dec 15 07:23:22 2005 on tinker.exit.com X-Virus-Status: Clean Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 16:45:29 -0000 On Fri, 2005-12-16 at 09:57 +0100, Oliver Fromme wrote: > I've seen reports of a few people who had problems with > 6.0, but personally I didn't have any, and I wouldn't > want to go back. In fact I can't think of a single > reason why I wouldn't upgrade a FreeBSD machine to 6.x. Well, there is _one_ reason. I, too, have (almost) all of my machines up to 6-stable, with the very notable exception of the one that runs asterisk. Unfortunately, last I looked, the zaptel drivers hadn't been ported to 6. I found this out the hard way when I upgraded and my VOIP setup failed spectacularly. I then downgraded back to 5.4 and have been there ever since, siiigh. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 16:49:50 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 131DE16A41F for ; Fri, 16 Dec 2005 16:49:50 +0000 (GMT) (envelope-from delphij@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93F2643D4C for ; Fri, 16 Dec 2005 16:49:49 +0000 (GMT) (envelope-from delphij@gmail.com) Received: by wproxy.gmail.com with SMTP id i31so664020wra for ; Fri, 16 Dec 2005 08:49:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=KA/jcp8ePP2nBJ/kGi4VrKIh4xTBmsGnhvB2nzGMxo4vJCd7L7qL8ABEfRawXBlYR6VzFhBk4sGz+cckt7oXzAvAJRBWSpsZGyFwiJ3g0oFf/05s55r2DN105ATqeK18f56OCFaIHsdlU06lwCQTJqzPvXUYfzjGpYB6pXxrkfY= Received: by 10.65.35.12 with SMTP id n12mr13523qbj; Fri, 16 Dec 2005 08:49:48 -0800 (PST) Received: by 10.65.72.5 with HTTP; Fri, 16 Dec 2005 08:49:48 -0800 (PST) Message-ID: Date: Sat, 17 Dec 2005 00:49:48 +0800 From: Xin LI To: freebsd-stable MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline Cc: sos@FreeBSD.org Subject: indefinite wait buffer: Does this indicate hardware issue? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: delphij@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 16:49:50 -0000 RGVhciBmb2xrcywKCkkgaGF2ZSBhIGJveCBpbmRpY2F0aW5nIHRoZSBmb2xsb3dpbmcgc29tZXRp bWVzOgoic3dhcF9wYWdlcjogaW5kZWZpbml0ZSB3YWl0IGJ1ZmZlcjogYnVmb2JqOiAwLCBibGtu bzogMjYyMTY5LCBzaXplOiA0MDk2IgoKSXQncyBydW5uaW5nIEZyZWVCU0QgNi4wLVJFTEVBU0Us IHdpdGggdHdvIE1heHRvciA3WTI1MFAwIGhhcmQgZGlza3MKYXR0YWNoZWQgdG8gSW50ZWwgSUNI NSBVRE1BMTAwIGNvbnRyb2xsZXIgd2l0aCBody5hdGEud2MgZGlzYWJsZWQuCgpEb2VzIHRoaXMg aW5kaWNhdGUgYSBoYXJkd2FyZSBpc3N1ZSwgb3Igc29tZSBidWdzIGVsc2V3aGVyZT8KCkNoZWVy cywKLS0KWGluIExJIDxkZWxwaGlqQGRlbHBoaWoubmV0PiBodHRwOi8vd3d3LmRlbHBoaWoubmV0 Cg== From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 17:24:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4F2316A41F for ; Fri, 16 Dec 2005 17:24:22 +0000 (GMT) (envelope-from weirdo@tehran.lain.pl) Received: from tehran.lain.pl (tehran.lain.pl [85.221.230.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1958B43D4C for ; Fri, 16 Dec 2005 17:24:21 +0000 (GMT) (envelope-from weirdo@tehran.lain.pl) Received: from weirdo by tehran.lain.pl with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EnJJZ-000Fvx-5L for freebsd-stable@freebsd.org; Fri, 16 Dec 2005 18:24:17 +0100 Date: Fri, 16 Dec 2005 18:24:17 +0100 From: Stanislaw Halik To: freebsd-stable@freebsd.org Message-ID: <20051216172417.GA61005@tehran.lain.pl> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://tehran.lain.pl/public.key User-Agent: Mutt/1.5.11 Subject: Re: indefinite wait buffer: Does this indicate hardware issue? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 17:24:23 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Xin LI wrote: > I have a box indicating the following sometimes: > "swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262169, size: 4096" > It's running FreeBSD 6.0-RELEASE, with two Maxtor 7Y250P0 hard disks > attached to Intel ICH5 UDMA100 controller with hw.ata.wc disabled. > Does this indicate a hardware issue, or some bugs elsewhere? are you using swapfiles? swap memory through files's performance is kind of lower than in swap partitions and it might be the cause. i've got same messages from a server with swap file, but nothing which would affect stability. --=20 Stanis=B3aw Halik, http://tehran.lain.pl --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDovhAadU+vjT62TERAuXaAJ9Y+DVbcNiYYk9RmzY77d66o0azxACfTrpO ORFiKoQGllZuThbW3lPwCSU= =v6eZ -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 17:27:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5275116A41F for ; Fri, 16 Dec 2005 17:27:44 +0000 (GMT) (envelope-from w8hdkim@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0DDD43D5A for ; Fri, 16 Dec 2005 17:27:43 +0000 (GMT) (envelope-from w8hdkim@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so661515nzo for ; Fri, 16 Dec 2005 09:27:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=SMx/N2ms7RQlUVCUe8U+7A4ChvB8UpkPoubEouUcg0DLA30J/ur6vPmIyaJcebQre1IYuTWFR8RYcYijaV5jXc05ykKCz3wq6peELtDgC+J2F6vx3Ka72PQOioSdZS0/6PZ0OeGShsuc782nW6FBnZLSrFrutYOLHXr6yXVnb0w= Received: by 10.36.79.5 with SMTP id c5mr1310265nzb; Fri, 16 Dec 2005 09:27:42 -0800 (PST) Received: by 10.36.153.3 with HTTP; Fri, 16 Dec 2005 09:27:42 -0800 (PST) Message-ID: <89dbfdc30512160927i3c992fa0gaa0ed776220eca57@mail.gmail.com> Date: Fri, 16 Dec 2005 12:27:42 -0500 From: Kim Culhan To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 17:27:44 -0000 On Fri, December 16, 2005 11:45 am, Frank Mayhar said: > Well, there is _one_ reason. I, too, have (almost) all of my machines > up to 6-stable, with the very notable exception of the one that runs > asterisk. Unfortunately, last I looked, the zaptel drivers hadn't been > ported to 6. I found this out the hard way when I upgraded and my VOIP > setup failed spectacularly. I then downgraded back to 5.4 and have been > there ever since, siiigh. -- The zaptel drivers are working fine on 6, check the archives of the asterisk-bsd list: http://lists.digium.com/pipermail/asterisk-bsd/2005-December/001363.html The latest asterisk from CVS HEAD compiles and runs very well on FreeBSD 6-STABLE -give it a try. -kim -- w8hdkim@gmail.com From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 17:36:10 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53F8116A41F; Fri, 16 Dec 2005 17:36:10 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6256243D77; Fri, 16 Dec 2005 17:35:44 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jBGHZDMK019337; Fri, 16 Dec 2005 10:35:13 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43A2FAD2.7020508@samsco.org> Date: Fri, 16 Dec 2005 10:35:14 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: delphij@delphij.net References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-stable , sos@FreeBSD.org Subject: Re: indefinite wait buffer: Does this indicate hardware issue? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 17:36:10 -0000 Xin LI wrote: > Dear folks, > > I have a box indicating the following sometimes: > "swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262169, size: 4096" > > It's running FreeBSD 6.0-RELEASE, with two Maxtor 7Y250P0 hard disks > attached to Intel ICH5 UDMA100 controller with hw.ata.wc disabled. > > Does this indicate a hardware issue, or some bugs elsewhere? > > Cheers, > -- It means that either the hardware or driver lost a transaction, or that some sort LOR-type situation happened in the VM that is preventing the transaction from completing. First of all, do you have more than 4GB of RAM? Scott From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 17:42:58 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15BDA16A41F for ; Fri, 16 Dec 2005 17:42:58 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from geri.cc.fer.hr (geri.cc.fer.hr [161.53.72.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 525CA43D64 for ; Fri, 16 Dec 2005 17:42:54 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from geri.cc.fer.hr (localhost.cc.fer.hr [127.0.0.1]) by geri.cc.fer.hr (8.13.4/8.13.1) with ESMTP id jBGHdI8F042054 for ; Fri, 16 Dec 2005 18:39:18 +0100 (CET) (envelope-from ivoras@fer.hr) Received: from localhost (ivoras@localhost) by geri.cc.fer.hr (8.13.4/8.13.1/Submit) with ESMTP id jBGHdIui042051 for ; Fri, 16 Dec 2005 18:39:18 +0100 (CET) (envelope-from ivoras@fer.hr) X-Authentication-Warning: geri.cc.fer.hr: ivoras owned process doing -bs Date: Fri, 16 Dec 2005 18:39:18 +0100 (CET) From: Ivan Voras Sender: ivoras@geri.cc.fer.hr To: stable@freebsd.org Message-ID: <20051216183602.S41990@geri.cc.fer.hr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: gmirror SCSI+IDE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 17:42:58 -0000 For some funny reasons, I'll probably have to setup a gmirror between a SCSI disk device and a IDE one, and won't have much time for testing. So I'm wondering did anyone do such a thing and are there any caveats. For example, AFAIK SCSI devices are under Giant and IDE are not - is there any reason this would make problems? -- Preserve wildlife -- pickle a squirrel today! From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 17:50:11 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4B7616A41F for ; Fri, 16 Dec 2005 17:50:11 +0000 (GMT) (envelope-from delphij@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED33443D4C for ; Fri, 16 Dec 2005 17:50:10 +0000 (GMT) (envelope-from delphij@gmail.com) Received: by wproxy.gmail.com with SMTP id i31so676915wra for ; Fri, 16 Dec 2005 09:50:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hsKstkF+FapBCgE5HBlhFxJ/78bnSfja7cuEV7ODYKYWhmXXarjpYqSIyZD3Jqd1oYD24GX8oVukm8EDqmzlM7Cp0ly1TvirDRMy/UnL5WtgKTD83ha295aTWsXh/isAIt1bf4/k9si9CyoWKC0lfWSnZQjIAzob4WxWf5joGac= Received: by 10.64.242.4 with SMTP id p4mr55257qbh; Fri, 16 Dec 2005 09:50:08 -0800 (PST) Received: by 10.65.72.5 with HTTP; Fri, 16 Dec 2005 09:50:08 -0800 (PST) Message-ID: Date: Sat, 17 Dec 2005 01:50:08 +0800 From: Xin LI To: Stanislaw Halik In-Reply-To: <20051216172417.GA61005@tehran.lain.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20051216172417.GA61005@tehran.lain.pl> Cc: freebsd-stable@freebsd.org Subject: Re: indefinite wait buffer: Does this indicate hardware issue? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: delphij@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 17:50:11 -0000 SGksCgpPbiAxMi8xNy8wNSwgU3RhbmlzbGF3IEhhbGlrIDx3ZWlyZG9AdGVocmFuLmxhaW4ucGw+ IHdyb3RlOgo+IFhpbiBMSSA8ZGVscGhpakBnbWFpbC5jb20+IHdyb3RlOgo+ID4gSSBoYXZlIGEg Ym94IGluZGljYXRpbmcgdGhlIGZvbGxvd2luZyBzb21ldGltZXM6Cj4gPiAic3dhcF9wYWdlcjog aW5kZWZpbml0ZSB3YWl0IGJ1ZmZlcjogYnVmb2JqOiAwLCBibGtubzogMjYyMTY5LCBzaXplOiA0 MDk2Igo+ID4gRG9lcyB0aGlzIGluZGljYXRlIGEgaGFyZHdhcmUgaXNzdWUsIG9yIHNvbWUgYnVn cyBlbHNld2hlcmU/Cj4KPiBhcmUgeW91IHVzaW5nIHN3YXBmaWxlcz8gc3dhcCBtZW1vcnkgdGhy b3VnaCBmaWxlcydzIHBlcmZvcm1hbmNlIGlzIGtpbmQKPiBvZiBsb3dlciB0aGFuIGluIHN3YXAg cGFydGl0aW9ucyBhbmQgaXQgbWlnaHQgYmUgdGhlIGNhdXNlLiBpJ3ZlIGdvdAo+IHNhbWUgbWVz c2FnZXMgZnJvbSBhIHNlcnZlciB3aXRoIHN3YXAgZmlsZSwgYnV0IG5vdGhpbmcgd2hpY2ggd291 bGQKPiBhZmZlY3Qgc3RhYmlsaXR5LgoKTm8uICBJIHVzZWQgdHdvIHN3YXAgcGFydGl0aW9ucyB0 aGF0IGlzIG9uIHR3byBkaXNrcy4uLgoKQ2hlZXJzLAotLQpYaW4gTEkgPGRlbHBoaWpAZGVscGhp ai5uZXQ+IGh0dHA6Ly93d3cuZGVscGhpai5uZXQK From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 17:53:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6998616A41F for ; Fri, 16 Dec 2005 17:53:39 +0000 (GMT) (envelope-from delphij@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB77C43D5F for ; Fri, 16 Dec 2005 17:53:38 +0000 (GMT) (envelope-from delphij@gmail.com) Received: by wproxy.gmail.com with SMTP id i31so677623wra for ; Fri, 16 Dec 2005 09:53:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UQeBJa7zpm28E0nwumWAC/QcXWP43zQlASKuNqLtwwPgBS6Nf7EULyzXyDDdt1QEKkiqemxzhzQUWSzoKSpN9v5hiX2b9JIRu7j7XLOGU16P2W0AtTBZxyTiLZdbb58ztO3W6q3mPs78bkRQA8IWrjLtplfsKgFPop+KATsEa1c= Received: by 10.64.10.17 with SMTP id 17mr44416qbj; Fri, 16 Dec 2005 09:53:37 -0800 (PST) Received: by 10.65.72.5 with HTTP; Fri, 16 Dec 2005 09:53:37 -0800 (PST) Message-ID: Date: Sat, 17 Dec 2005 01:53:37 +0800 From: Xin LI To: Scott Long In-Reply-To: <43A2FAD2.7020508@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <43A2FAD2.7020508@samsco.org> Cc: freebsd-stable Subject: Re: indefinite wait buffer: Does this indicate hardware issue? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: delphij@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 17:53:39 -0000 SGksIFNjb3R0LAoKT24gMTIvMTcvMDUsIFNjb3R0IExvbmcgPHNjb3R0bEBzYW1zY28ub3JnPiB3 cm90ZToKWy4uLl0KPiBJdCBtZWFucyB0aGF0IGVpdGhlciB0aGUgaGFyZHdhcmUgb3IgZHJpdmVy IGxvc3QgYSB0cmFuc2FjdGlvbiwgb3IgdGhhdAo+IHNvbWUgc29ydCBMT1ItdHlwZSBzaXR1YXRp b24gaGFwcGVuZWQgaW4gdGhlIFZNIHRoYXQgaXMgcHJldmVudGluZyB0aGUKPiB0cmFuc2FjdGlv biBmcm9tIGNvbXBsZXRpbmcuICBGaXJzdCBvZiBhbGwsIGRvIHlvdSBoYXZlIG1vcmUgdGhhbiA0 R0Igb2YKPiBSQU0/CgpObywgYWN0dWFsbHkgaXQgaGFzIG9ubHkgMUdCIG9mIG1lbW9yeS4uLiAg QlRXLiBXb3VsZG4ndCBhIExPUiBjYXVzZQpkZWFkbG9jayBpZiBpdCBpcyBwcmV2ZW50aW5nIHRo ZSB0cmFuc2FjdGlvbiBmcm9tIGNvbXBsZXRpbmc/CgpDaGVlcnMsCi0tClhpbiBMSSA8ZGVscGhp akBkZWxwaGlqLm5ldD4gaHR0cDovL3d3dy5kZWxwaGlqLm5ldAo= From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 18:42:02 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D07316A41F for ; Fri, 16 Dec 2005 18:42:02 +0000 (GMT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0E6443D78 for ; Fri, 16 Dec 2005 18:41:52 +0000 (GMT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (localhost [127.0.0.1]) by tao.thought.org (8.13.1/8.13.1) with ESMTP id jBGIfoYv058557 for ; Fri, 16 Dec 2005 10:41:51 -0800 (PST) (envelope-from kline@tao.thought.org) Received: (from kline@localhost) by tao.thought.org (8.13.1/8.13.1/Submit) id jBGIfoEn058556 for freebsd-stable@freebsd.org; Fri, 16 Dec 2005 10:41:50 -0800 (PST) (envelope-from kline) Date: Fri, 16 Dec 2005 10:41:49 -0800 From: Gary Kline To: freebsd-stable@freebsd.org Message-ID: <20051216184149.GC58262@thought.org> References: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> <20051216113117.GA52639@mail.scottro.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051216113117.GA52639@mail.scottro.net> User-Agent: Mutt/1.4.2.1i X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing 19 years of service to the Unix community Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 18:42:02 -0000 On Fri, Dec 16, 2005 at 06:31:17AM -0500, Scott Robbins wrote: > > A "me too" here for 5-Stable. > > > > I have a test PC, that was running 5-Stable using an > > additional swapfile to extend swap space. Never any > > problems at all with 5. > > > > After upgrading to 6-stable, I got regular hang-ups of > > the system (endless loop?) when swapspace is used > > extensively. Never happened with 5. I didn't move until 5 until 5.2+; it was a major move. There were lots of things to get-right. So maybe by 6.5, 6 will be granite stable. I've been using FBSD since 2.0.5, and while lots of solid features have been thoughtfully added, I just don't see that 6 buys that much more than 5.x. Maybe 7.x, tho... gary > > I have to add my vote for 6, as did someone else in an earlier post. > Like some others, I always found 5.x a bit slower than 4.x (No > benchmarks, completely subjective.) From the very beginning, I've found > 6.x to be stable and quickly moved some non-critical servers to it. > > After testing, we moved the more critical servers to it as well, and > have been quite happy withe results. > > Again, completely subjective, but from the beginning 6.x seemed faster > and more responsive than 5.x > Hmm. A series of benchmarks might prove some points. Back in Aug, 2001 I ran stress tests and other benchmarks to test *this* hardware. I pushed things to a loadave of > 70. Everything held. Maybe we should consider something like this. A series of hard stress tests as well as objective benchmarks as we go forward. It would give one some metrics... . gary -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 19:00:36 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34DB816A436; Fri, 16 Dec 2005 19:00:36 +0000 (GMT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6F7143D5C; Fri, 16 Dec 2005 19:00:34 +0000 (GMT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (localhost [127.0.0.1]) by tao.thought.org (8.13.1/8.13.1) with ESMTP id jBGJ0XZu058687; Fri, 16 Dec 2005 11:00:33 -0800 (PST) (envelope-from kline@tao.thought.org) Received: (from kline@localhost) by tao.thought.org (8.13.1/8.13.1/Submit) id jBGJ0Vts058686; Fri, 16 Dec 2005 11:00:31 -0800 (PST) (envelope-from kline) Date: Fri, 16 Dec 2005 11:00:31 -0800 From: Gary Kline To: Joao Barros Message-ID: <20051216190031.GD58262@thought.org> References: <43A266E5.3080103@samsco.org> <70e8236f0512160659h3379253dw468e5aad3f741002@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <70e8236f0512160659h3379253dw468e5aad3f741002@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing 19 years of service to the Unix community Cc: stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 19:00:36 -0000 On Fri, Dec 16, 2005 at 02:59:09PM +0000, Joao Barros wrote: > On 12/16/05, Scott Long wrote: > > > FreeBSD 7 > > We will start preparing for FreeBSD 7.0 in June 2007. > > > > I'll hopefully update the release engineering pages soon to reflect > > this. If you have any questions, please feel free to contact me and the > > rest of the release engineering team. Thanks!ott > > There have been some questions on the lists about what to expect from > release x.y and I personnally have always looked at the TODO list like > http://www.freebsd.org/releases/6.0R/todo.html > For 6.0 I noticed there were more updates on that page for bugs and > their fixes than for features per se. My sugestion, maybe at a first > stage setting the TODO list has it's advantages, one knows what to > expect from a release, it's clearly stated and documented there and > the developers can see their goals. > This is valid for minor and major releases of course. > > How about it? > Are you volunteering to post the TODO lists here on -stable every N months? I think it's a great idea to have some clues about where we're going, or hope to be going. gary > -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 19:04:02 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A75916A41F; Fri, 16 Dec 2005 19:04:02 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DA1E43D73; Fri, 16 Dec 2005 19:03:51 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jBGJ3mTA019804; Fri, 16 Dec 2005 12:03:48 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43A30F94.2030909@samsco.org> Date: Fri, 16 Dec 2005 12:03:48 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gary Kline References: <43A266E5.3080103@samsco.org> <70e8236f0512160659h3379253dw468e5aad3f741002@mail.gmail.com> <20051216190031.GD58262@thought.org> In-Reply-To: <20051216190031.GD58262@thought.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: Joao Barros , stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 19:04:02 -0000 Gary Kline wrote: > On Fri, Dec 16, 2005 at 02:59:09PM +0000, Joao Barros wrote: > >>On 12/16/05, Scott Long wrote: >> >> >>>FreeBSD 7 >>>We will start preparing for FreeBSD 7.0 in June 2007. >>> >>>I'll hopefully update the release engineering pages soon to reflect >>>this. If you have any questions, please feel free to contact me and the >>>rest of the release engineering team. Thanks!ott >> >>There have been some questions on the lists about what to expect from >>release x.y and I personnally have always looked at the TODO list like >>http://www.freebsd.org/releases/6.0R/todo.html >>For 6.0 I noticed there were more updates on that page for bugs and >>their fixes than for features per se. My sugestion, maybe at a first >>stage setting the TODO list has it's advantages, one knows what to >>expect from a release, it's clearly stated and documented there and >>the developers can see their goals. >>This is valid for minor and major releases of course. >> >>How about it? >> > > > Are you volunteering to post the TODO lists here on -stable > every N months? I think it's a great idea to have some > clues about where we're going, or hope to be going. > > gary > > > > The release TODO list is maintained on the FreeBSD.org website, though it's usually only active during release cycles. I used to also email it out in text format to the mailing lists on a weekly basis. Scott From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 19:25:33 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F7E016A4FF for ; Fri, 16 Dec 2005 19:25:33 +0000 (GMT) (envelope-from dsyphers@u.washington.edu) Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB20643D9B for ; Fri, 16 Dec 2005 19:25:03 +0000 (GMT) (envelope-from dsyphers@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGJP38V010951 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 11:25:03 -0800 X-Auth-Received: from yggdrasil.seektruth.org (c-67-171-38-33.hsd1.wa.comcast.net [67.171.38.33]) (authenticated authid=dsyphers) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGJP2UF031440 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 16 Dec 2005 11:25:02 -0800 From: David Syphers To: freebsd-stable@freebsd.org Date: Fri, 16 Dec 2005 11:25:01 -0800 User-Agent: KMail/1.8.2 References: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> <20051216113117.GA52639@mail.scottro.net> <20051216184149.GC58262@thought.org> In-Reply-To: <20051216184149.GC58262@thought.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512161125.02157.dsyphers@u.washington.edu> X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Cc: Gary Kline Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 19:25:34 -0000 On Friday 16 December 2005 10:41 am, Gary Kline wrote: > On Fri, Dec 16, 2005 at 06:31:17AM -0500, Scott Robbins wrote: > > > After upgrading to 6-stable, I got regular hang-ups of > > > the system (endless loop?) when swapspace is used > > > extensively. Never happened with 5. > > I didn't move until 5 until 5.2+; it was a major move. > There were lots of things to get-right. So maybe by > 6.5, 6 will be granite stable. I feel compelled to point out that 5 wasn't called -stable until 5.3. 5.0-5.2 were early adopter releases. So 6.n isn't comparable to 5.n (as always YMMV). My understanding is that the whole point of this expedited release process is to avoid the feature creep that leads to huge and sometimes painful leaps (like 4 to 5 was). -David -- "What's the good of having mastery over cosmic balance and knowing the secrets of fate if you can't blow something up?" -Terry Pratchett From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 19:25:38 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EDB716A420 for ; Fri, 16 Dec 2005 19:25:38 +0000 (GMT) (envelope-from mandrews@bit0.com) Received: from mindcrime.bit0.com (bit0.com [216.24.42.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2379743D98 for ; Fri, 16 Dec 2005 19:25:27 +0000 (GMT) (envelope-from mandrews@bit0.com) Received: from localhost (localhost.bit0.com [127.0.0.1]) by mindcrime.bit0.com (Postfix) with ESMTP id AC7DA730037; Fri, 16 Dec 2005 14:25:26 -0500 (EST) Received: from mindcrime.bit0.com ([127.0.0.1]) by localhost (mindcrime.bit0.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01910-09; Fri, 16 Dec 2005 14:25:25 -0500 (EST) Received: from localhost (localhost.bit0.com [127.0.0.1]) by mindcrime.bit0.com (Postfix) with ESMTP; Fri, 16 Dec 2005 14:25:25 -0500 (EST) Date: Fri, 16 Dec 2005 14:25:24 -0500 (EST) From: Mike Andrews To: Paulo Fragoso In-Reply-To: <43A29E8F.8030101@nlink.com.br> Message-ID: <20051216142215.B2542@bit0.com> References: <43A29E8F.8030101@nlink.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at bit0.com Cc: freebsd-stable@freebsd.org Subject: Re: Diskless /libexec/ld-elf.so.1: Cannot execute objects on / X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 19:25:38 -0000 On Fri, 16 Dec 2005, Paulo Fragoso wrote: > After upgrade from FreeBSD 5.3 to FREEBSD_5_4 (cvs), our diskless > machines didn't work correctly, many applications using dynamic > libraries didn't start, this error was showed: > > /libexec/ld-elf.so.1: Cannot execute objects on / > > We found on all diskless machines had MNT_NOEXEC flags set on (fstatfs). > After that we have changed rtld.c changed: > > --- rtld.c.orig Thu Dec 15 17:26:41 2005 > +++ rtld.c Thu Dec 15 17:38:15 2005 > @@ -1267,7 +1267,7 @@ > close(fd); > return NULL; > } > - if (fs.f_flags & MNT_NOEXEC) { > + if (fs.f_flags & MNT_NOEXEC && strcmp(fs.f_mntonname,"/") ) { > _rtld_error("Cannot execute objects on %s\n", > fs.f_mntonname); > close(fd); > return NULL; > > Now, all diskless stations works fine. > > Is there another solution for this case? We had the same problem with our netboot cluster, and going from RELENG_5_4 (5.4-RELEASE) up to RELENG_5 (5-STABLE) fixed it. Mike Andrews * mandrews@bit0.com * http://www.bit0.com It's not news, it's Fark.com. Carpe cavy! From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 19:39:50 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6FDF16A41F; Fri, 16 Dec 2005 19:39:50 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34A5943D69; Fri, 16 Dec 2005 19:39:46 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 53DAD1A3C27; Fri, 16 Dec 2005 11:39:43 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9C42151257; Fri, 16 Dec 2005 14:39:42 -0500 (EST) Date: Fri, 16 Dec 2005 14:39:42 -0500 From: Kris Kennaway To: delphij@delphij.net Message-ID: <20051216193942.GA92029@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable , sos@FreeBSD.org Subject: Re: indefinite wait buffer: Does this indicate hardware issue? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 19:39:51 -0000 --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 17, 2005 at 12:49:48AM +0800, Xin LI wrote: > Dear folks, >=20 > I have a box indicating the following sometimes: > "swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262169, size: 4096" >=20 > It's running FreeBSD 6.0-RELEASE, with two Maxtor 7Y250P0 hard disks > attached to Intel ICH5 UDMA100 controller with hw.ata.wc disabled. >=20 > Does this indicate a hardware issue, or some bugs elsewhere? In that configuration, probably a hardware issue. Is it always the same block? This message triggers as a false positive in other cases when swapping is too slow, like if you swap to a swapfile on a heavily loaded filesystem. Kris --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoxf+Wry0BWjoQKURAjQwAKCRcvdVJh75OZ/SJcf9Ap0wo8qMfgCfQR86 TqTSggIjTa5JKLGT45CGEi4= =2nfS -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 19:42:56 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1B0E16A41F for ; Fri, 16 Dec 2005 19:42:56 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D4EC43D62 for ; Fri, 16 Dec 2005 19:42:56 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 4D4FC3EB8; Fri, 16 Dec 2005 13:42:55 -0600 (CST) Date: Fri, 16 Dec 2005 13:42:55 -0600 To: Gary Kline Message-ID: <20051216194255.GB31497@soaustin.net> References: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> <20051216113117.GA52639@mail.scottro.net> <20051216184149.GC58262@thought.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051216184149.GC58262@thought.org> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 19:42:57 -0000 On Fri, Dec 16, 2005 at 10:41:49AM -0800, Gary Kline wrote: > I didn't move until 5 until 5.2+; it was a major move. > There were lots of things to get-right. So maybe by > 6.5, 6 will be granite stable. (Disclaimer: I am not on re@ but I do watch the bugs come in as one of the bugmasters). We completely redid the way we did release engineering between the 5.X series and 6.X series to avoid ever inflicting that much pain again. The jump from 5.2 to 5.3 was huge and we learned many things not to do. The jump from 5.3 to 5.4 was pretty minor -- but so is the jump from 5.4 to 6.0. The emphasis was on a smaller feature set and a much longer (painfully long :-) ) period of QA. The result in the PR database is that for 6.0 vs 5.4, although there are a number of regressions (in particular, certain i386 hardware), the number of entries is far, far, less than for the 5.2.1 to 5.3 transition. So I would urge people to change their view of 6.0. From what I can tell it's one of our strongest releases. It certainly must be the strongest .0 release. In any case, I don't believe there are going to be .5 and .6 releases going forwards. This will keep us, in the future, from spending so much time on MFCs. Some of this background is further detailed in an article I wrote: http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/version-guide/past-schedules.html I hope that people will find the information there useful. And, if someone ever wants to write that 5.X vs 6.X vs 7.X feature list comparison, now would be a good time :-) mcl From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 20:06:37 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6F2016A41F for ; Fri, 16 Dec 2005 20:06:37 +0000 (GMT) (envelope-from delphij@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id E58EF43D46 for ; Fri, 16 Dec 2005 20:06:36 +0000 (GMT) (envelope-from delphij@gmail.com) Received: by zproxy.gmail.com with SMTP id 14so1442302nzn for ; Fri, 16 Dec 2005 12:06:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XYrc2wd77tpDLZ42YWiIg42yQDHOcln5Y4Hu4WsOtJn5fEsTMhABrulKCkJmfZX1E2wtMNLrwOXPrBD18EzY6Bte+cR4D+kbhvhfaq0tDsW1pmD0+Q95nV8TgICbD/08mNq4pHRSJ287PlvQleLOA2ZNwW4Tru07hLp0C7Ue8XY= Received: by 10.65.197.20 with SMTP id z20mr1493804qbp; Fri, 16 Dec 2005 12:06:36 -0800 (PST) Received: by 10.65.72.5 with HTTP; Fri, 16 Dec 2005 12:06:36 -0800 (PST) Message-ID: Date: Sat, 17 Dec 2005 04:06:36 +0800 From: Xin LI To: Kris Kennaway In-Reply-To: <20051216193942.GA92029@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20051216193942.GA92029@xor.obsecurity.org> Cc: freebsd-stable , sos@freebsd.org Subject: Re: indefinite wait buffer: Does this indicate hardware issue? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: delphij@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 20:06:38 -0000 SGksIEtyaXMsCgpPbiAxMi8xNy8wNSwgS3JpcyBLZW5uYXdheSA8a3Jpc0BvYnNlY3VyaXR5Lm9y Zz4gd3JvdGU6ClsuLi5dCj4gSW4gdGhhdCBjb25maWd1cmF0aW9uLCBwcm9iYWJseSBhIGhhcmR3 YXJlIGlzc3VlLiAgSXMgaXQgYWx3YXlzIHRoZQo+IHNhbWUgYmxvY2s/CgpObywgaXQncyBzb21l dGltZXMgb3RoZXIsIGFuZCBpcyBxdWl0ZSBpbmZyZXF1ZW50LiAgT24gdGhlIG90aGVyIGhhbmQs Cm5laXRoZXIgU01BUlQgbm9yIGVycm9yIGhhcyByZXBvcnRlZCBzb21lIGluY2lkZW50LCBzbyBJ IHdhcyBzdHVjawp3aGVuIGxvb2tpbmcgb24gaGFyZHdhcmUgaXNzdWVzLCBhcyB0aGUgbWVzc2Fn ZSBkb2VzIG5vdCBpbmRpY2F0ZQp3aGljaCBkaXNrKHMpIG1heSBoYXZlIHByb2JsZW0uLi4KCkNo ZWVycywKLS0KWGluIExJIDxkZWxwaGlqQGRlbHBoaWoubmV0PiBodHRwOi8vd3d3LmRlbHBoaWou bmV0Cg== From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 20:20:55 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 320D616A41F for ; Fri, 16 Dec 2005 20:20:55 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: from sarevok.lan.melvyn.homeunix.org (i153153.upc-i.chello.nl [62.195.153.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EF9343D62 for ; Fri, 16 Dec 2005 20:20:46 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: by sarevok.lan.melvyn.homeunix.org (Postfix, from userid 100) id 350AF11454; Fri, 16 Dec 2005 21:20:45 +0100 (CET) From: Melvyn Sopacua To: freebsd-stable@freebsd.org Date: Fri, 16 Dec 2005 21:20:44 +0100 User-Agent: KMail/1.8.3 References: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> <20051216184149.GC58262@thought.org> <20051216194255.GB31497@soaustin.net> In-Reply-To: <20051216194255.GB31497@soaustin.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512162120.45053.freebsd.stable@melvyn.homeunix.org> Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 20:20:55 -0000 On Friday 16 December 2005 20:42, Mark Linimon wrote: > And, if someone ever wants to write that 5.X vs 6.X vs 7.X feature list > comparison, now would be a good time :-) Well, here's a nice start (and a question or two slipped in) - dmesg diff between two GENERIC kernels 5 vs 6 stable of the same date, same hardware. Noise reduced (mem range flips on hw, 'same' entries): -FreeBSD 5.4-STABLE #3: Sun Nov 20 03:52:04 CET 2005 - root@sarevok.lan.melvyn.homeunix.org:/usr/obj/usr/src/sys/GENERIC +FreeBSD 6.0-STABLE #1: Wed Dec 7 01:36:46 CET 2005 + root@sarevok.lan.melvyn.homeunix.org:/usr/obj/usr/current/src/sys/GENERIC Features=0xa7e9f9bf + Features2=0x180 Q: What are those extra features and are they useful? ;-) +npx0: [FAST] -cpu0: on acpi0 +cpu0: on acpi0 Q: Guessing that's a formatting difference, rather then 6.x not recognizing the states (sysctl hw.acpi.cpu.cx_supported confirms 4 states) -ACPI link \\_SB_.PCI0.LNKB has invalid initial irq 11, ignoring +pci_link1: BIOS IRQ 11 for 0.31.INTB is invalid Q: Could this be midi? +uhci0: [GIANT-LOCKED] +uhci1: [GIANT-LOCKED] +uhci2: [GIANT-LOCKED] Q: Again - is this formatting or are these (and the ones below) still under Giant in 6.x but not in 5.x? -pci0: at device 29.7 (no driver attached) +ehci0: mem 0xf4fffc00-0xf4ffffff irq 11 at device 29.7 on pci0 +ehci0: [GIANT-LOCKED] +usb3: EHCI version 1.0 +usb3: companion controllers, 2 ports each: usb0 usb1 usb2 +usb3: on ehci0 +usb3: USB revision 2.0 +uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 +uhub3: 6 ports with 6 removable, self powered Kudos! -atapci0: port 0xbfa0-0xbfaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 -ata0: channel #0 on atapci0 -ata1: channel #1 on atapci0 -pcm0: port 0xbc40-0xbc7f,0xb800-0xb8ff mem 0xf4fff400-0xf4fff4ff,0xf4fff800-0xf4fff9ff irq 5 at device 31.5 on pci0 -pcm0: +atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf at device 31.1 on pci0 +ata0: on atapci0 +ata1: on atapci0 +pci0: at device 31.5 (no driver attached) Didn't have snd_ich_load="YES" in loader.conf yet. pcm0 appears the same and is GIANT-LOCKED on 6. +atkbd0: [GIANT-LOCKED] +psm0: [GIANT-LOCKED] -Timecounter "TSC" frequency 1398819442 Hz quality 800 -Timecounters tick every 10.000 msec +Timecounter "TSC" frequency 1398819606 Hz quality 800 +Timecounters tick every 1.000 msec Q: This is a big scarey difference :p This isn't a printf bug I presume? -acd0: CDRW at ata1-master PIO4 +acd0: CDRW at ata1-master UDMA33 That's *very* nice! -- Melvyn Sopacua freebsd.stable@melvyn.homeunix.org FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 20:29:43 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA67E16A420 for ; Fri, 16 Dec 2005 20:29:43 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58FD843D79 for ; Fri, 16 Dec 2005 20:29:43 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: by ion.gank.org (mail, from userid 1001) id C6FB82AA00; Fri, 16 Dec 2005 14:29:42 -0600 (CST) Date: Fri, 16 Dec 2005 14:29:39 -0600 From: Craig Boston To: Melvyn Sopacua Message-ID: <20051216202938.GA36252@nowhere> Mail-Followup-To: Craig Boston , Melvyn Sopacua , freebsd-stable@freebsd.org References: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> <20051216184149.GC58262@thought.org> <20051216194255.GB31497@soaustin.net> <200512162120.45053.freebsd.stable@melvyn.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512162120.45053.freebsd.stable@melvyn.homeunix.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 20:29:43 -0000 On Fri, Dec 16, 2005 at 09:20:44PM +0100, Melvyn Sopacua wrote: > + Features2=0x180 > > Q: What are those extra features and are they useful? ;-) Enhanced Speedstep and Thermal Management. They're useful if you want to use powerd to conserve power / reduce heat generation. (load the cpufreq driver and look in sysctl dev.cpu) > -cpu0: on acpi0 > +cpu0: on acpi0 > > Q: Guessing that's a formatting difference, rather then 6.x not recognizing > the states (sysctl hw.acpi.cpu.cx_supported confirms 4 states) Not sure on this, but you're probably better off using EST anyway as I think it gives you more control over the processor frequency. > +uhci0: [GIANT-LOCKED] > +uhci1: [GIANT-LOCKED] > +uhci2: [GIANT-LOCKED] > > Q: Again - is this formatting or are these (and the ones below) still under > Giant in 6.x but not in 5.x? Just formatting. USB (and a lot more) was under GIANT in 5.x as well, but 5.x didn't tell you which drivers were running under GIANT. 6.x does as a gentle reminder that those areas need to be worked on ;) Craig From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 20:45:08 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8937316A41F for ; Fri, 16 Dec 2005 20:45:08 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D1CA43D5E for ; Fri, 16 Dec 2005 20:45:07 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail03.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBGKj40U012700 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 17 Dec 2005 07:45:04 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBGKj3Hh086274; Sat, 17 Dec 2005 07:45:04 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBGKj388086273; Sat, 17 Dec 2005 07:45:03 +1100 (EST) (envelope-from pjeremy) Date: Sat, 17 Dec 2005 07:45:03 +1100 From: Peter Jeremy To: Melvyn Sopacua Message-ID: <20051216204503.GR77268@cirb503493.alcatel.com.au> References: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> <20051216184149.GC58262@thought.org> <20051216194255.GB31497@soaustin.net> <200512162120.45053.freebsd.stable@melvyn.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512162120.45053.freebsd.stable@melvyn.homeunix.org> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 20:45:08 -0000 On Fri, 2005-Dec-16 21:20:44 +0100, Melvyn Sopacua wrote: >Features=0xa7e9f9bf >+ Features2=0x180 > >Q: What are those extra features and are they useful? ;-) This is just printing out the CPU features bitmasks. The difference is that the CPU identification code in 6.x looks at the bitmap returned in %ecx after a cpuid 1. The features were always there, 6.x just prints them out. As for usefulness... EST - Enhanced SpeedStep TM2 - Thermal Monitor 2 >+uhci0: [GIANT-LOCKED] >+uhci1: [GIANT-LOCKED] >+uhci2: [GIANT-LOCKED] > >Q: Again - is this formatting or are these (and the ones below) still under >Giant in 6.x but not in 5.x? No. 6.x is just more verbose. I thought these had all been hidden behind 'verbose' as they are primarily hints to the developers. >-pci0: at device 29.7 (no driver attached) >+ehci0: mem >0xf4fffc00-0xf4ffffff irq 11 at device 29.7 on pci0 >+ehci0: [GIANT-LOCKED] > >Kudos! I'm still trying to get my USB2 to do anything more than probe :-( >-Timecounter "TSC" frequency 1398819442 Hz quality 800 >-Timecounters tick every 10.000 msec >+Timecounter "TSC" frequency 1398819606 Hz quality 800 >+Timecounters tick every 1.000 msec > >Q: This is a big scarey difference :p This isn't a printf bug I presume? Which bit? The TSC is notoriously unstable and a relative change of 1.2e-7 can be ignored. If you look at kern.clockrate, you'll see that hz now defaults to 1000. >-acd0: CDRW at ata1-master PIO4 >+acd0: CDRW at ata1-master UDMA33 > >That's *very* nice! Again, that's just a change in defaults. Problems were found with DMA to ATAPI devices so the decision was made to default to PIO4 in 5.x. You can set hw.ata.atapi_dma to 1 in 5.x if you want to (see acd(4)). -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 20:53:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FFCC16A41F for ; Fri, 16 Dec 2005 20:53:32 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0556143D5F for ; Fri, 16 Dec 2005 20:53:31 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Fri, 16 Dec 2005 12:53:28 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 4D7BF5D09; Fri, 16 Dec 2005 12:53:27 -0800 (PST) To: Craig Boston In-reply-to: Your message of "Fri, 16 Dec 2005 14:29:39 CST." <20051216202938.GA36252@nowhere> Date: Fri, 16 Dec 2005 12:53:27 -0800 From: "Kevin Oberman" Message-Id: <20051216205327.4D7BF5D09@ptavv.es.net> Cc: freebsd-stable@freebsd.org, Melvyn Sopacua Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 20:53:32 -0000 > Date: Fri, 16 Dec 2005 14:29:39 -0600 > From: Craig Boston > Sender: owner-freebsd-stable@freebsd.org > > > -cpu0: on acpi0 > > +cpu0: on acpi0 > > > > Q: Guessing that's a formatting difference, rather then 6.x not recognizing > > the states (sysctl hw.acpi.cpu.cx_supported confirms 4 states) > > Not sure on this, but you're probably better off using EST anyway as I > think it gives you more control over the processor frequency. No. There is no conflict between Cx states and EST. Cx states specifies how deeply the CPU will sleep when idle. EST controls processor speed and voltage. In most cases, your REALLY want to use both of these. They are very significant in saving power. (Of course, USB tends to limit the effectiveness of Cx states. I need to run without USB to get really good battery life and to make suspend (S3) really ut power drain. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 20:55:08 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DA8716A41F for ; Fri, 16 Dec 2005 20:55:08 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail24.syd.optusnet.com.au (mail24.syd.optusnet.com.au [211.29.133.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA8DF43D55 for ; Fri, 16 Dec 2005 20:55:01 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail24.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBGKskHR014025 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 17 Dec 2005 07:54:48 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBGKskHh086320; Sat, 17 Dec 2005 07:54:46 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBGKskwd086319; Sat, 17 Dec 2005 07:54:46 +1100 (EST) (envelope-from pjeremy) Date: Sat, 17 Dec 2005 07:54:46 +1100 From: Peter Jeremy To: delphij@delphij.net Message-ID: <20051216205446.GS77268@cirb503493.alcatel.com.au> References: <20051216193942.GA92029@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-stable Subject: Re: indefinite wait buffer: Does this indicate hardware issue? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 20:55:08 -0000 On Sat, 2005-Dec-17 04:06:36 +0800, Xin LI wrote: >No, it's sometimes other, and is quite infrequent. On the other hand, >neither SMART nor error has reported some incident, so I was stuck >when looking on hardware issues, as the message does not indicate >which disk(s) may have problem... A hardware error should have been reported as such. But if you suspect a disk problem, try dd'ing the swap partition (or the whole disk) to /dev/null. If you can read the whole partition, you can probably write to it. (Or you could dd /dev/zero to the partitions whilst swap is not attached - eg in single user after boot). If you suspect retries are a problem, monitor the I/O rate with iostat or systat and see if it suddenly drops. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 21:05:09 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 523BC16A422 for ; Fri, 16 Dec 2005 21:05:09 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: from sarevok.lan.melvyn.homeunix.org (i153153.upc-i.chello.nl [62.195.153.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4935643D4C for ; Fri, 16 Dec 2005 21:05:03 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: by sarevok.lan.melvyn.homeunix.org (Postfix, from userid 100) id 86CE511454; Fri, 16 Dec 2005 22:04:34 +0100 (CET) From: Melvyn Sopacua To: freebsd-stable@freebsd.org Date: Fri, 16 Dec 2005 22:04:33 +0100 User-Agent: KMail/1.8.3 References: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> <200512162120.45053.freebsd.stable@melvyn.homeunix.org> <20051216204503.GR77268@cirb503493.alcatel.com.au> In-Reply-To: <20051216204503.GR77268@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512162204.34400.freebsd.stable@melvyn.homeunix.org> Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 21:05:09 -0000 On Friday 16 December 2005 21:45, Peter Jeremy wrote: > EST - Enhanced SpeedStep > TM2 - Thermal Monitor 2 Hm, guess I'll play with mbmon to see if this shows more then one monitor (assuming the 2 is the number of, not the protocol version). > >-pci0: at device 29.7 (no driver attached) > >+ehci0: mem > >0xf4fffc00-0xf4ffffff irq 11 at device 29.7 on pci0 > >+ehci0: [GIANT-LOCKED] > > > >Kudos! > > I'm still trying to get my USB2 to do anything more than probe :-( Ouch, well guess I'll have to find that memory stick I should have around here somewhere. > >-Timecounter "TSC" frequency 1398819442 Hz quality 800 > >-Timecounters tick every 10.000 msec > >+Timecounter "TSC" frequency 1398819606 Hz quality 800 > >+Timecounters tick every 1.000 msec > > > >Q: This is a big scarey difference :p This isn't a printf bug I presume? > > Which bit? The TSC is notoriously unstable and a relative change of > 1.2e-7 can be ignored. If you look at kern.clockrate, you'll see that > hz now defaults to 1000. Ah! That explains why rtc was complaining on 5.x but magically stopped doing that on 6. > >-acd0: CDRW at ata1-master PIO4 > >+acd0: CDRW at ata1-master UDMA33 > > > >That's *very* nice! > > Again, that's just a change in defaults. Problems were found with DMA to > ATAPI devices so the decision was made to default to PIO4 in 5.x. You can > set hw.ata.atapi_dma to 1 in 5.x if you want to (see acd(4)). Problems as in long waits on `burncd blank` and subsequent i/o errors and unmountable disks that disappear after reboot? -- Melvyn Sopacua freebsd.stable@melvyn.homeunix.org FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 21:38:54 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5960616A41F for ; Fri, 16 Dec 2005 21:38:54 +0000 (GMT) (envelope-from feanor@kh405.net) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C42743D72 for ; Fri, 16 Dec 2005 21:38:45 +0000 (GMT) (envelope-from feanor@kh405.net) Received: from melkor.kh405.net (plb95-2-82-236-78-224.fbx.proxad.net [82.236.78.224]) by smtp5-g19.free.fr (Postfix) with ESMTP id 9D8DC16FEC for ; Fri, 16 Dec 2005 22:38:44 +0100 (CET) Received: by melkor.kh405.net (Postfix, from userid 1001) id C4974611E; Fri, 16 Dec 2005 22:38:45 +0100 (CET) Date: Fri, 16 Dec 2005 22:38:45 +0100 From: Marwan Burelle To: freebsd-stable@freebsd.org Message-ID: <20051216213845.GA800@melkor.kh405.net> References: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> <20051216113117.GA52639@mail.scottro.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <20051216113117.GA52639@mail.scottro.net> User-Agent: Mutt/1.4.2.1i Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 21:38:54 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 16, 2005 at 06:31:17AM -0500, Scott Robbins wrote: > I have to add my vote for 6, as did someone else in an earlier post.=20 > Like some others, I always found 5.x a bit slower than 4.x (No > benchmarks, completely subjective.) From the very beginning, I've found > 6.x to be stable and quickly moved some non-critical servers to it. I will add my me too here. I move my home computer to 6.0 when I get back a connexion at home. My office computer used to seem far faster than my home one (quite normal for a 3.2 GHz PIV against an Athlon 1800+, with twice memory) but after some weeks of 6.0 on my Athlon and _many_ ports building (mostly because of the damned f*** last OCaml release) the relative difference seems far less impressive. This also quite subjective, but my feeling is that speed impressions is as important as real speed improvements, at least for workstation. Just note that my actual usage is only LaTeX (PhD writing =2E.. ) and ports building. This was my 2 cents. --=20 Marwan Burelle, http://www.lri.fr/~burelle ( burelle@lri.fr | Marwan.Burelle@ens.fr ) http://www.cduce.org --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDozPlI+2UvUKfgvgRApnoAKCZ28X9kFNQoFbEWB3+a7F58gp1IwCgk705 elxH+rvHBUOvbBYtOFFDrM4= =fTla -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 22:44:56 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1629816A41F for ; Fri, 16 Dec 2005 22:44:56 +0000 (GMT) (envelope-from lonewolf-freebsd@earthmagic.org) Received: from ppp162-248.static.internode.on.net (ppp162-248.static.internode.on.net [150.101.162.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93B8C43D81 for ; Fri, 16 Dec 2005 22:44:49 +0000 (GMT) (envelope-from lonewolf-freebsd@earthmagic.org) Received: from [192.168.2.3] (sarah.zone2.earthmagic.org [192.168.2.3]) by ppp162-248.static.internode.on.net (Postfix-MSA) with ESMTP id 7A47691F1; Sat, 17 Dec 2005 09:44:47 +1100 (EST) Message-ID: <43A3435E.7000100@earthmagic.org> Date: Sat, 17 Dec 2005 09:44:46 +1100 From: Johny Mattsson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051003) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, paulo@nlink.com.br References: <43A29E8F.8030101@nlink.com.br> <20051216142215.B2542@bit0.com> In-Reply-To: <20051216142215.B2542@bit0.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Diskless /libexec/ld-elf.so.1: Cannot execute objects on / X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 22:44:56 -0000 On 12/17/05 06:25, Mike Andrews wrote: > On Fri, 16 Dec 2005, Paulo Fragoso wrote: >> After upgrade from FreeBSD 5.3 to FREEBSD_5_4 (cvs), our diskless >> machines didn't work correctly, many applications using dynamic >> libraries didn't start, this error was showed: >> >> /libexec/ld-elf.so.1: Cannot execute objects on / > > We had the same problem with our netboot cluster, and going from > RELENG_5_4 (5.4-RELEASE) up to RELENG_5 (5-STABLE) fixed it. Confirmed. This problem was fixed shortly after 5.4-RELEASE. I'm running a 5.4 from Aug 22, and it has the fix in it. If you need the precise patch, you should be able to search the archives from August and find it. Cheers, /Johny -- Johny Mattsson - Making IT work ,-. ,-. ,-. When all else fails, http://www.earthmagic.org _.' `-' `-' Murphy's Law still works! From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 23:17:16 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B10516A422 for ; Fri, 16 Dec 2005 23:17:16 +0000 (GMT) (envelope-from pdquilty@adelphia.net) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10DB143D5F for ; Fri, 16 Dec 2005 23:17:07 +0000 (GMT) (envelope-from pdquilty@adelphia.net) Received: from pdq-lan103 ([68.67.198.69]) by mta9.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051216231656.MFK14388.mta9.adelphia.net@pdq-lan103> for ; Fri, 16 Dec 2005 18:16:56 -0500 From: "Peter D. Quilty" To: freebsd-stable@freebsd.org Content-Type: multipart/mixed; boundary="=-ahjj6+H3lie1zWviRRqY" Date: Fri, 16 Dec 2005 18:16:55 -0500 Message-Id: <1134775015.2892.28.camel@pdq-9100> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Subject: Need help with crash analysis X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Peter D. Quilty" List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 23:17:16 -0000 --=-ahjj6+H3lie1zWviRRqY Content-Type: text/plain Content-Transfer-Encoding: 7bit I have a Dell Inspiron 9100 laptop that has been crashing lately. It seems to happen when there is a moderate disk load and the network load is > 6 Mbits/sec. I can usually replicate it by running "portsdb -fUu" while downloading or copying large files across the network. I have tried the following in an attempt to isolate the problem, but nothing has worked. * disabling ACPI * disabling hyperthreading * disabling SMP * switching back to the 4BSD scheduler from ULE I ran kgdb against kernel.debug and the crash dump, but don't quite know how to interpret it or where to go from here. I've attached my kernel config file, dmesg.boot, and the outputs from kldstat and kgdb. I recently upgraded my router/access point at home from 802.11b to 802.11g to take advantage of the faster network cards in my laptops and I am wondering if that could be exposing a bug or race condition. I tried putting my network card back in 11b mode (instead of 11g) and I don't see the problem nearly as often. Does anyone have any suggestions as to how to troubleshoot this further? I have saved the relevant kernel files and crash dumps, in case I need to reference them again. -- Peter D. Quilty pdquilty@adelphia.net 703-906-5633 GnuPG Key: http://users.adelphia.net/~pdquilty/gpg-pubkey.asc GnuPG Key Fingerprint: A46A 0E56 D13E 5617 4696 2B04 0D0C E34D CB6D D107 --=-ahjj6+H3lie1zWviRRqY Content-Disposition: attachment; filename=PDQ.9100 Content-Type: text/plain; name=PDQ.9100; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit makeoptions DEBUG=-g machine i386 cpu I686_CPU ident "PDQ.9100" options INCLUDE_CONFIG_FILE options ROOTDEVNAME=\"ufs:ad0s1a\" options SMP options SCHED_ULE options PREEMPTION options MPTABLE_FORCE_HTT options IPI_PREEMPTION options INET options FFS options SOFTUPDATES options UFS_DIRHASH options MSDOSFS options SMBFS options CD9660 options PROCFS options PSEUDOFS options COMPAT_LINUX options LINPROCFS options COMPAT_43 options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV options ADAPTIVE_GIANT options NETSMB options NETSMBCRYPTO options LIBMCHAIN options LIBICONV device apic device isa device pci device ata device atadisk device atapicd device atapicam options ATA_STATIC_ID device scbus device da device cd device pass device atkbdc device atkbd device psm device vga device splash device sc device npx device pmtimer device cbb device pccard device cardbus device sio device miibus device bfe device wlan device wlan_wep device ath_hal device ath_rate_sample device ath device loop device mem device io device random device ether device pty device snp device bpf device uhci device ehci device usb device umass device ums device firewire device sbp device sound device snd_ich --=-ahjj6+H3lie1zWviRRqY Content-Disposition: attachment; filename=dmesg.boot Content-Type: text/plain; name=dmesg.boot; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Copyright (c) 1992-2005 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 6.0-RELEASE #16: Wed Dec 14 14:34:52 EST 2005 root@pdq-9100:/usr/obj/usr/src/sys/PDQ.9100 ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (2992.51-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Features2=0x4400> Hyperthreading: 2 logical CPUs real memory = 1073389568 (1023 MB) avail memory = 1041309696 (993 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard netsmb_dev: loaded kqemu version 0x00010200 kqemu: KQEMU installed, max_instances=4 max_locked_mem=129932kB. ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pci_link0: irq 11 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 11 on acpi0 pci_link3: irq 11 on acpi0 pci_link4: on acpi0 pci_link5: irq 11 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 acpi_acad0: on acpi0 battery0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe8000000-0xefffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 drm0: port 0xc000-0xc0ff mem 0xf0000000-0xf7ffffff,0xfcff0000-0xfcffffff irq 16 at device 0.0 on pci1 info: [drm] AGP at 0xe8000000 128MB info: [drm] Initialized radeon 1.16.0 20050311 on minor 0 uhci0: port 0xbf80-0xbf9f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xbf60-0xbf7f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xbf40-0xbf5f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xbf20-0xbf3f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xf8fffc00-0xf8ffffff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib2: at device 30.0 on pci0 pci2: on pcib2 bfe0: mem 0xfaffe000-0xfaffffff irq 18 at device 0.0 on pci2 miibus0: on bfe0 bmtphy0: on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bfe0: Ethernet address: 00:0f:1f:29:30:18 cbb0: at device 1.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 fwohci0: <1394 Open Host Controller Interface> mem 0xfaffd800-0xfaffdfff,0xfaff8000-0xfaffbfff irq 19 at device 1.1 on pci2 fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 44:4f:c0:00:24:8a:54:81 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ath0: mem 0xfafe0000-0xfafeffff irq 17 at device 3.0 on pci2 ath0: Ethernet address: 00:0b:6b:35:bd:5d ath0: mac 5.9 phy 4.3 radio 3.6 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pcm0: port 0xd800-0xd8ff,0xdc40-0xdc7f mem 0xf8fff800-0xf8fff9ff,0xf8fff400-0xf8fff4ff irq 17 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: pci0: at device 31.6 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model GlidePoint, device ID 0 sio0 port 0x3f8-0x3ff,0x270-0x277 irq 4 drq 3 on acpi0 sio0: type 16550A pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: vendor 0x0430 product 0x0100, rev 1.10/1.05, addr 2, iclass 3/1 ums0: 3 buttons. Timecounters tick every 1.000 msec acpi_acad0: acline initialization start acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times battery0: battery initialization start ad0: 57231MB at ata0-master UDMA100 battery0: battery initialization done, tried 1 times acd0: CDRW at ata1-master UDMA33 SMP: AP CPU #1 Launched! cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted --=-ahjj6+H3lie1zWviRRqY Content-Disposition: attachment; filename=kgdb Content-Type: text/plain; name=kgdb; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x10 fault code = supervisor read, page not present instruction pointer = 0x20:0xc066d174 stack pointer = 0x28:0xe36198bc frame pointer = 0x28:0x0 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 = 38 (swi1: net) trap number = 12 panic: page fault cpuid = 0 Uptime: 1h0m21s Dumping 1023 MB (2 chunks) chunk 0: 1MB (158 pages) Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x1c fault code = supervisor write, page not present instruction pointer = 0x20:0xc054a3a8 stack pointer = 0x28:0xe5084c8c frame pointer = 0x28:0xe5084ccc 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 = 36 (swi4: clock sio) trap number = 12 ... ok chunk 1: 1023MB (261802 pages) 1007 (CTRL-C to abort) 991 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 975 959 943 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) quit --=-ahjj6+H3lie1zWviRRqY Content-Disposition: attachment; filename=kldstat Content-Type: text/plain; name=kldstat; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Id Refs Address Size Name 1 34 0xc0400000 400f38 kernel 2 1 0xc0801000 4184 if_tap.ko 3 1 0xc0806000 5f4c ugen.ko 4 10 0xc080c000 1459c agp.ko 5 2 0xc0821000 11178 drm.ko 6 1 0xc0833000 1e944 radeon.ko 7 1 0xc0852000 bde0 kqemu.ko 8 3 0xc085e000 3548 ucom.ko 9 1 0xc0862000 2e0c uvisor.ko 10 1 0xc0865000 434c uplcom.ko 11 1 0xc086a000 6be0 wlan_ccmp.ko 12 1 0xc0871000 4050 wlan_tkip.ko 13 16 0xc0876000 5fbfc acpi.ko 14 1 0xc28d1000 5000 g_md.ko 15 1 0xc2acf000 2d000 pf.ko 16 1 0xc2bf9000 2000 green_saver.ko --=-ahjj6+H3lie1zWviRRqY-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 00:05:51 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96BDC16A420 for ; Sat, 17 Dec 2005 00:05:51 +0000 (GMT) (envelope-from hartzell@satchel.alerce.com) Received: from merlin.alerce.com (w094.z064001164.sjc-ca.dsl.cnc.net [64.1.164.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD23143D68 for ; Sat, 17 Dec 2005 00:05:49 +0000 (GMT) (envelope-from hartzell@satchel.alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 2903521A0; Fri, 16 Dec 2005 16:05:43 -0800 (PST) Received: from satchel.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by merlin.alerce.com (Postfix) with ESMTP id 03853214E; Fri, 16 Dec 2005 16:05:42 -0800 (PST) Received: from satchel.alerce.com (localhost [127.0.0.1]) by satchel.alerce.com (8.13.4/8.13.4) with ESMTP id jBH05qWq086221; Fri, 16 Dec 2005 16:05:52 -0800 (PST) (envelope-from hartzell@satchel.alerce.com) Received: (from hartzell@localhost) by satchel.alerce.com (8.13.4/8.13.4/Submit) id jBH05p7Z086214; Fri, 16 Dec 2005 16:05:51 -0800 (PST) (envelope-from hartzell) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17315.22111.426723.110802@satchel.alerce.com> Date: Fri, 16 Dec 2005 16:05:51 -0800 To: "Kevin Oberman" In-Reply-To: <20051216205327.4D7BF5D09@ptavv.es.net> References: <20051216202938.GA36252@nowhere> <20051216205327.4D7BF5D09@ptavv.es.net> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 00:05:51 -0000 Kevin Oberman writes: > [...] > No. There is no conflict between Cx states and EST. Cx states specifies > how deeply the CPU will sleep when idle. EST controls processor speed > and voltage. In most cases, your REALLY want to use both of these. They > are very significant in saving power. (Of course, USB tends to limit the > effectiveness of Cx states. I need to run without USB to get really good > battery life and to make suspend (S3) really ut power drain. Can you expand a bit on that "Of course USB...". What's the problem with USB? Can one just kunload it before suspend? g. From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 00:43:22 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33AA916A41F for ; Sat, 17 Dec 2005 00:43:22 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2793D43D5C for ; Sat, 17 Dec 2005 00:43:21 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so593732wxc for ; Fri, 16 Dec 2005 16:43:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CObsC0GR/TPA9P/zt6RYOHaSgRn6wzcG/3NMyUuOn+7Eq29wdVbIF0viWCfuqqmMauRxc++oUg/J1wti/GOyUK+Qh+UwObzpkb590ugqsL41/ws08X/3kxx5c1Gju/5rlwiiU02SgQ/QuW4/xpbJxs9iDTBFD5lplCE0pCr+KAQ= Received: by 10.70.87.2 with SMTP id k2mr1716227wxb; Fri, 16 Dec 2005 16:43:20 -0800 (PST) Received: by 10.70.36.7 with HTTP; Fri, 16 Dec 2005 16:43:20 -0800 (PST) Message-ID: <70e8236f0512161643t605ff100see3100bf99604ba0@mail.gmail.com> Date: Sat, 17 Dec 2005 00:43:20 +0000 From: Joao Barros To: Scott Long In-Reply-To: <43A30F94.2030909@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43A266E5.3080103@samsco.org> <70e8236f0512160659h3379253dw468e5aad3f741002@mail.gmail.com> <20051216190031.GD58262@thought.org> <43A30F94.2030909@samsco.org> Cc: Gary Kline , stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 00:43:22 -0000 > Gary Kline wrote: > > Are you volunteering to post the TODO lists here on -stable > > every N months? I think it's a great idea to have some > > clues about where we're going, or hope to be going. No I am not. But you are right on the "it's a great idea to have some clues about where we're going, or hope to be going" part. That was my poin= t. On 12/16/05, Scott Long wrote: > The release TODO list is maintained on the FreeBSD.org website, As I pointed, available for anyone interested in knowing what's going on. > though > it's usually only active during release cycles. Yes, but until that time only by reading yours and other Dev's answers to the same questions one knows where a Release is heading. The users know what to expect and the Dev's know what they set themselfes to do :-) -- Joao Barros From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 01:13:02 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3191116A41F; Sat, 17 Dec 2005 01:13:02 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A5A743D6B; Sat, 17 Dec 2005 01:12:58 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-157-23-19.jan.bellsouth.net [70.157.23.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 3E1E5AD; Fri, 16 Dec 2005 19:12:57 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id CFF1D61C21; Fri, 16 Dec 2005 19:12:55 -0600 (CST) Date: Fri, 16 Dec 2005 19:12:55 -0600 From: "Matthew D. Fuller" To: Joao Barros Message-ID: <20051217011255.GL63497@over-yonder.net> References: <43A266E5.3080103@samsco.org> <70e8236f0512160659h3379253dw468e5aad3f741002@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <70e8236f0512160659h3379253dw468e5aad3f741002@mail.gmail.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 01:13:02 -0000 On Fri, Dec 16, 2005 at 02:59:09PM +0000 I heard the voice of Joao Barros, and lo! it spake thus: > > There have been some questions on the lists about what to expect > from release x.y and I personnally have always looked at the TODO > list like http://www.freebsd.org/releases/6.0R/todo.html It's always been my impression that the todo list is put together as we close in on a release as a "these things still need to get done". It's not really a "here are the things this release offers over the previous one"... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 03:55:49 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D39B16A41F for ; Sat, 17 Dec 2005 03:55:49 +0000 (GMT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id A174C43D5A for ; Sat, 17 Dec 2005 03:55:48 +0000 (GMT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (localhost [127.0.0.1]) by tao.thought.org (8.13.1/8.13.1) with ESMTP id jBH3tkcr084709; Fri, 16 Dec 2005 19:55:47 -0800 (PST) (envelope-from kline@tao.thought.org) Received: (from kline@localhost) by tao.thought.org (8.13.1/8.13.1/Submit) id jBH3tjfG084696; Fri, 16 Dec 2005 19:55:45 -0800 (PST) (envelope-from kline) Date: Fri, 16 Dec 2005 19:55:44 -0800 From: Gary Kline To: Mark Linimon Message-ID: <20051217035544.GA61448@thought.org> References: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> <20051216113117.GA52639@mail.scottro.net> <20051216184149.GC58262@thought.org> <20051216194255.GB31497@soaustin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051216194255.GB31497@soaustin.net> User-Agent: Mutt/1.4.2.1i X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing 19 years of service to the Unix community Cc: Gary Kline , freebsd-stable@freebsd.org Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 03:55:49 -0000 On Fri, Dec 16, 2005 at 01:42:55PM -0600, Mark Linimon wrote: > On Fri, Dec 16, 2005 at 10:41:49AM -0800, Gary Kline wrote: > > I didn't move until 5 until 5.2+; it was a major move. > > There were lots of things to get-right. So maybe by > > 6.5, 6 will be granite stable. > > (Disclaimer: I am not on re@ but I do watch the bugs come in as one of > the bugmasters). > > We completely redid the way we did release engineering between the 5.X > series and 6.X series to avoid ever inflicting that much pain again. > > The jump from 5.2 to 5.3 was huge and we learned many things not to do. > The jump from 5.3 to 5.4 was pretty minor -- but so is the jump from > 5.4 to 6.0. The emphasis was on a smaller feature set and a much longer > (painfully long :-) ) period of QA. The win for me with 5.2.1 last summer was tha it finally let me begin to get my ThinkPad 600E working. 5.3 may have been required to bring the bizarre sound chip to life. It's got some some kind of microsoft idiosyncrasy. I'm at .3-STABLE everywhere and now moving cautiously to .4. YES to your smaller jumps. If memory serves, we made two fairly hard moves. First from 2.x.y to 3.x to get rid of a.out; then 4.x to 5.x for the new filesystem paradigm. I can see anything beyond the i868 being in the 64-bit world; (*sigh*) :-) > > The result in the PR database is that for 6.0 vs 5.4, although there > are a number of regressions (in particular, certain i386 hardware), the > number of entries is far, far, less than for the 5.2.1 to 5.3 transition. > > So I would urge people to change their view of 6.0. From what I can > tell it's one of our strongest releases. It certainly must be the > strongest .0 release. > > In any case, I don't believe there are going to be .5 and .6 releases > going forwards. This will keep us, in the future, from spending so > much time on MFCs. I'm still planning on not upping to 6 until 6.2 or better. Not unless 6.0/.1 has absolutely push-button audio so I can play real, mp3, m3u, ogg, windows-audio/whatever! > > Some of this background is further detailed in an article I wrote: > > http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/version-guide/past-schedules.html > > I hope that people will find the information there useful. Good one! thanks for putting that together. == Q == Does anybody know why there is no article.freebsd.org v-site that people could find stuff like this more easily? It probab;y could be done with a link/symlink and a DNS entry for the virtual website. gary > > And, if someone ever wants to write that 5.X vs 6.X vs 7.X feature list > comparison, now would be a good time :-) > > mcl -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 10:55:05 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBD6916A41F for ; Sat, 17 Dec 2005 10:55:05 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1C6243D5A for ; Sat, 17 Dec 2005 10:55:04 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (atmzeb@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBHAt2iW049715 for ; Sat, 17 Dec 2005 11:55:02 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBHAt2aG049714; Sat, 17 Dec 2005 11:55:02 +0100 (CET) (envelope-from olli) Date: Sat, 17 Dec 2005 11:55:02 +0100 (CET) Message-Id: <200512171055.jBHAt2aG049714@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <200512162120.45053.freebsd.stable@melvyn.homeunix.org> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 10:55:05 -0000 Melvyn Sopacua wrote: > Features=0xa7e9f9bf LUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE> > + Features2=0x180 > > Q: What are those extra features Enhanced Speedstep, Thermal Monitor 2. > and are they useful? ;-) Yes. The kernel's cpufreq framework will use them. > -ACPI link \\_SB_.PCI0.LNKB has invalid initial irq 11, ignoring > +pci_link1: BIOS IRQ 11 for 0.31.INTB is invalid > > Q: Could this be midi? Possibly. Look at the output of "pciconf -lv" and search for the entry for bus 0, slot 31. > -Timecounter "TSC" frequency 1398819442 Hz quality 800 > -Timecounters tick every 10.000 msec > +Timecounter "TSC" frequency 1398819606 Hz quality 800 > +Timecounters tick every 1.000 msec > > Q: This is a big scarey difference :p This isn't a printf bug I presume? No, the default of HZ changed from 100 to 1000. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "I have stopped reading Stephen King novels. Now I just read C code instead." -- Richard A. O'Keefe From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 11:32:24 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAB7416A41F; Sat, 17 Dec 2005 11:32:24 +0000 (GMT) (envelope-from shurd@sasktel.net) Received: from misav08.sasknet.sk.ca (misav08.sasknet.sk.ca [142.165.20.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E2B843D5E; Sat, 17 Dec 2005 11:32:23 +0000 (GMT) (envelope-from shurd@sasktel.net) Received: from bgmpomr2.sasknet.sk.ca ([142.165.72.23]) by misav08 with InterScan Messaging Security Suite; Sat, 17 Dec 2005 05:32:22 -0600 Received: from [192.168.0.193] ([142.165.59.202]) by bgmpomr2.sasknet.sk.ca (SaskTel eMessaging Service) with ESMTPA id <0IRN005EC41W8A10@bgmpomr2.sasknet.sk.ca>; Sat, 17 Dec 2005 05:32:22 -0600 (CST) Date: Sat, 17 Dec 2005 05:32:20 -0600 From: Stephen Hurd In-reply-to: <43A27C32.6020501@samsco.org> To: Scott Long Message-id: <43A3F744.7040301@sasktel.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-ca, en-gb, en-us, en References: <43A266E5.3080103@samsco.org> <20051216082704.GA52634@thought.org> <43A27C32.6020501@samsco.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051108 Cc: Gary Kline , stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 11:32:25 -0000 > Security updates will be maintained for quite a while. However, it > takes manpower to test each proposed security change, so it's very hard > to justify doing them 'indefinitely'. The stated policy from the > security team is 2 years. So they will probably support 5.5 into > 2008, but I wanted to be conservative in my statement in case they > have different plans. It seems to me like FBSD may be pushing too much to a new major version. Although NBSD is stepping up the "-release" versions significantly, I feel that FBSD (and friends, but this is hardly the place for B&W about them) are/is moving a bit too quickly. While the SMP changes are nice and all (my main application server at home is a dual coppermine 1GHz), the tty (for example) seems to be getting more and more unstable as it goes on... this seems to a certain degree to be that features in -CURRENT are barely cooking let alone baking, and talk is already that 5.x is obsolete. Pushing off GIANT was a 5.x goal iirc, and making existing changes stable is a per-major goal (again, imho). It seems like the version numbers aren't actually meaningfull anymore. I mean... I'm used to a FBSD that would change majors when an API and/or ABI *needed* changing. It feels like it's happening 'cause it'd be "cool" to have a 7.x now. The FBSD pthread support for example has been better than Linux since libc_r... and it's only improved. But I can't actualy *rely* on anything specific working. A project I work on has had a THREADS_ACTUALLY_WORK flag available for Linux when they acually do (not yet, let's not talk about sigwait()) for the last few years. But I can't depend on a major version for strtold()... can't even depend on a > comparison. It's hard to know what to depend on now... "Things are Changing" and you need to know exactly what you need to discover what is required. A few years ago, I was flabbergasted when I was asked for a way to identify the libc version under FBSD. The need to do something like that never occured to me.... the possibility of having libc "out of sync" with the kernel never even crossed my mind, and the reason was that the whole thing was one system. It's starting to feel a lot more like some Linux system now... only without the spiffy up2date thinger to go with it. Upgrading from major to major has been something I never minded when needed, but it's too needed now and there's nothing to make it happy. Either the OBSD "no need to rebuild GENERIC" model is being accepted, or we're dumping the "/etc/,/usr/*/etc/*" backup and restore model. I love rcNG for example... but my OPL3 no longer does anything usefull... I had an AWE32 with gobs of RAM plugged in and had to use the Voxware drivers until I couldn't... and now I *need* to use timidity because what other choice do I have? I guess I'm old-fashioned, but I just recently managed to have my LaserWriter 16/600 (using the built-in AUI port) be as easy to set up with CUPS as with printcap I was happy and joyfull. But I had to *manually* do the /usr/bin/* and /usr/sbin/* symlinks *and rebuild KDE samba, and OOo. Why? Probobly 'cause I had lpr working before... does the vaunted handbook even suggest CUPS is there the slighest hint of a migration path? My home NIS and NFS server recently became a Solaris 10 one because it Just Works -- despite the inetd, local service, etc horribleness (still not an AMd fan... mount /home via NFS and don't worry) but I'm worried... even I, a FBSD fanatic am moving my servives off of my various FBSD boxes. Why? They may not work when Things are Better. FBSD currently out "sells" any *nix you pick... *BSD, */Linux, heck, *X.. but when Apache and PostgreSQL move to Linux as their primary system (and the world yawns... let's not talk about BDB) this is a wake-up call... I still haven't tried DragonFly, I think their development model is surpassed by FBSD. But hey, they fixed their clock and no other BSD did. Small incremental fixes. Have we lost that? One tool for the job. Perl killed it? FBSD is *NOT* a kernel bsdtar is *way* too late to make excuses for... where did the pascal compiler go? > Significant performance and stability enhancements that simply cannot > be broken up and backported to FreeBSD 5. We are marching towards a > 'Giant-less' kernel, which means continuing better SMP performance and > better UP responsiveness. With 6.0 we are finally starting to see the > benefit of the SMPng work that we've been doing for 5 years. iirc, this was a 5.x goal. We get a Major with no reason. Release notes between Majors are BORING... one needs to look at the userland to get anything they expect to use, and *BASIC* subsystems like the tty suffer. Will UP ever match what it once was? From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 15:58:06 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24E4216A41F for ; Sat, 17 Dec 2005 15:58:06 +0000 (GMT) (envelope-from frank@ircnow.org) Received: from scott.blazing.de (scott.blazing.de [80.86.187.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F15E43D5A for ; Sat, 17 Dec 2005 15:58:05 +0000 (GMT) (envelope-from frank@ircnow.org) Received: by scott.blazing.de (Postfix, from userid 510) id 16C9A823A1; Sat, 17 Dec 2005 16:58:03 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on scott.blazing.de X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from shodan.gnuless.de (shodan.gnuless.de [85.14.216.230]) by scott.blazing.de (Postfix) with ESMTP id 439F582398 for ; Sat, 17 Dec 2005 16:58:01 +0100 (CET) Received: by shodan.gnuless.de (nbSMTP-1.00) for uid 1002 frank@ircnow.org; Sat, 17 Dec 2005 16:58:01 +0100 (CET) Date: Sat, 17 Dec 2005 16:58:01 +0100 From: Frank Steinborn To: stable@freebsd.org Message-ID: <20051217155800.GA63807@scott.blazing.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline X-PGP: 41F1741D User-Agent: mutt-ng/devel-r581 (FreeBSD) Cc: Subject: Update from 6.0-RELEASE fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 15:58:06 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello,=20 i'm trying to update to -STABLE from today from a 6.0-RELEASE and make installworld fails here: /usr/share/man/man3/lwres_getaddrsbyname.3.gz -> /usr/share/man/man3/lwres_resutil.3.gz /usr/share/man/man3/lwres_getnamebyaddr.3.gz -> /usr/share/man/man3/lwres_resutil.3.gz /usr/share/man/man3/lwres_string_parse.3.gz -> /usr/share/man/man3/lwres_resutil.3.gz =3D=3D=3D> libexec (install) =3D=3D=3D> libexec/atrun (install) install -s -o root -g wheel -m 555 atrun /usr/libexec install -o root -g wheel -m 444 atrun.8.gz /usr/share/man/man8 =3D=3D=3D> libexec/bootpd (install) install -s -o root -g wheel -m 555 bootpd /usr/libexec strip: /usr/libexec/bootpd: Memory exhausted install: wait: No such file or directory *** Error code 70 Any hints on that? I updated to -STABLE from other Releases too without problems (almost the same configuration on the boxes). Thanks, Frank --UugvWAfsgieZRqgk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDpDWIK0akcUHxdB0RAnmcAJ9XcGb4Q7AhbkjvKsSACK0hvRy8IACfQC3U 3aPq71DGd1gu+PehPtN7nek= =EcOc -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 16:18:15 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D27D116A41F for ; Sat, 17 Dec 2005 16:18:15 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8800243D62 for ; Sat, 17 Dec 2005 16:18:14 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6B30A1A3C27; Sat, 17 Dec 2005 08:18:14 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8AAE45154A; Sat, 17 Dec 2005 11:18:13 -0500 (EST) Date: Sat, 17 Dec 2005 11:18:13 -0500 From: Kris Kennaway To: Frank Steinborn Message-ID: <20051217161813.GA59494@xor.obsecurity.org> References: <20051217155800.GA63807@scott.blazing.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline In-Reply-To: <20051217155800.GA63807@scott.blazing.de> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: Update from 6.0-RELEASE fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 16:18:15 -0000 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 17, 2005 at 04:58:01PM +0100, Frank Steinborn wrote: > Hello,=20 >=20 > i'm trying to update to -STABLE from today from a 6.0-RELEASE and make > installworld fails here: >=20 > /usr/share/man/man3/lwres_getaddrsbyname.3.gz -> > /usr/share/man/man3/lwres_resutil.3.gz > /usr/share/man/man3/lwres_getnamebyaddr.3.gz -> > /usr/share/man/man3/lwres_resutil.3.gz > /usr/share/man/man3/lwres_string_parse.3.gz -> > /usr/share/man/man3/lwres_resutil.3.gz > =3D=3D=3D> libexec (install) > =3D=3D=3D> libexec/atrun (install) > install -s -o root -g wheel -m 555 atrun /usr/libexec > install -o root -g wheel -m 444 atrun.8.gz /usr/share/man/man8 > =3D=3D=3D> libexec/bootpd (install) > install -s -o root -g wheel -m 555 bootpd /usr/libexec > strip: /usr/libexec/bootpd: Memory exhausted Well, is it? Kris --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDpDpFWry0BWjoQKURAmX3AKCCDR5iDOVi2mtosi2npJskcEJ3kgCgpsNr zsL1rVRn7JmfcaRqD5xX0cQ= =Dk9D -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 16:37:33 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E180316A41F for ; Sat, 17 Dec 2005 16:37:33 +0000 (GMT) (envelope-from frank@ircnow.org) Received: from scott.blazing.de (scott.blazing.de [80.86.187.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AC8043D60 for ; Sat, 17 Dec 2005 16:37:33 +0000 (GMT) (envelope-from frank@ircnow.org) Received: by scott.blazing.de (Postfix, from userid 510) id 449BC82397; Sat, 17 Dec 2005 17:37:32 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on scott.blazing.de X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from shodan.gnuless.de (shodan.gnuless.de [85.14.216.230]) by scott.blazing.de (Postfix) with ESMTP id 7C07682296 for ; Sat, 17 Dec 2005 17:37:26 +0100 (CET) Received: by shodan.gnuless.de (nbSMTP-1.00) for uid 1002 frank@ircnow.org; Sat, 17 Dec 2005 17:37:26 +0100 (CET) Date: Sat, 17 Dec 2005 17:37:26 +0100 From: Frank Steinborn To: freebsd-stable@freebsd.org Message-ID: <20051217163726.GA22281@scott.blazing.de> Mail-Followup-To: freebsd-stable@freebsd.org References: <20051217155800.GA63807@scott.blazing.de> <20051217161813.GA59494@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH" Content-Disposition: inline In-Reply-To: <20051217161813.GA59494@xor.obsecurity.org> X-PGP: 41F1741D User-Agent: mutt-ng/devel-r581 (FreeBSD) Subject: Re: Update from 6.0-RELEASE fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 16:37:34 -0000 --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Kris Kennaway wrote: > > strip: /usr/libexec/bootpd: Memory exhausted >=20 > Well, is it? I don't think so, i have nothing in logs that something is going to be killed and i still have space in swap. Frank --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD4DBQFDpD7FK0akcUHxdB0RAhiNAKCySKdZuJkU7cT2HquHLfiYhmsQXgCYrhkf 8qbpKLBGG3y2FI3Nu7vH7A== =WBxY -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 16:44:49 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69F7C16A41F for ; Sat, 17 Dec 2005 16:44:49 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7AE343D58 for ; Sat, 17 Dec 2005 16:44:48 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 247145D6C; Sat, 17 Dec 2005 11:44:48 -0500 (EST) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19312-08; Sat, 17 Dec 2005 11:44:47 -0500 (EST) Received: from [192.168.1.3] (pool-68-161-122-227.ny325.east.verizon.net [68.161.122.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id EB11D5C20; Sat, 17 Dec 2005 11:44:46 -0500 (EST) Message-ID: <43A44089.5050109@mac.com> Date: Sat, 17 Dec 2005 11:44:57 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20051217155800.GA63807@scott.blazing.de> <20051217161813.GA59494@xor.obsecurity.org> In-Reply-To: <20051217161813.GA59494@xor.obsecurity.org> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: stable@freebsd.org, Frank Steinborn Subject: Re: Update from 6.0-RELEASE fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 16:44:49 -0000 Kris Kennaway wrote: > On Sat, Dec 17, 2005 at 04:58:01PM +0100, Frank Steinborn wrote: >> i'm trying to update to -STABLE from today from a 6.0-RELEASE and make >> installworld fails here: [ ... ] >>===> libexec/bootpd (install) >> install -s -o root -g wheel -m 555 bootpd /usr/libexec >> strip: /usr/libexec/bootpd: Memory exhausted > > Well, is it? Some people are more verbose than needed. Kris is not one of those people. :-) However, Kris sometimes manages to generate such terse replies that you have to know the answer to the question you've asked before his reply makes sense. While brevity is a paramount virtue in writing-- and about that topic, I cannot say too much [1]-- however, Frank, you might want to consider the output of "swapinfo" and "top -o size". Perhaps you don't have enough swap configured, or none at all? -- -Chuck [1]: "Bear in mind, at all times and in all circumstances, whatever the subject under discussion-- be it never so dear to your heart and worthy of thoughtful consideration at far greater length than that to which you are regretfully obliged to constrain it-- that conciseness is a virtue of such paramount importance that the present writer would ever dream of relinquishing it, even for a moment; bearing in mind as well, that the related and yet not wholly identical temptation to entangle both the narrative and the reader in a thousand branching paths of digression, from which initally attractive yet ultimately fruitless byways (like those deceptively promising mountain trails which, when followed, gradually diminish to faint and narrow tracks and thence to mere nothingness, leaving the traveller stranded at some spot deserted by humanity not through whim or chance, but justly, on account of its intrinsic lack of any interest whatsoever) one may only with great difficulty find one's way back to the main thread, must also be sternly avoided. Every time you explain this point to the reader, follow it with a firmly worded assurance that that is exaactly what you intend to do. Believe yourself when you say it." (Steven Brust and T. Heyden.) From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 16:58:07 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77BA716A41F for ; Sat, 17 Dec 2005 16:58:07 +0000 (GMT) (envelope-from frank@ircnow.org) Received: from scott.blazing.de (scott.blazing.de [80.86.187.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id E915E43D46 for ; Sat, 17 Dec 2005 16:58:06 +0000 (GMT) (envelope-from frank@ircnow.org) Received: by scott.blazing.de (Postfix, from userid 510) id CAB64823AB; Sat, 17 Dec 2005 17:58:05 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on scott.blazing.de X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from shodan.gnuless.de (shodan.gnuless.de [85.14.216.230]) by scott.blazing.de (Postfix) with ESMTP id 6B03D82296 for ; Sat, 17 Dec 2005 17:58:04 +0100 (CET) Received: by shodan.gnuless.de (nbSMTP-1.00) for uid 1002 frank@ircnow.org; Sat, 17 Dec 2005 17:58:04 +0100 (CET) Date: Sat, 17 Dec 2005 17:58:04 +0100 From: Frank Steinborn To: freebsd-stable@freebsd.org Message-ID: <20051217165804.GB22281@scott.blazing.de> Mail-Followup-To: freebsd-stable@freebsd.org References: <20051217155800.GA63807@scott.blazing.de> <20051217161813.GA59494@xor.obsecurity.org> <43A44089.5050109@mac.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H+4ONPRPur6+Ovig" Content-Disposition: inline In-Reply-To: <43A44089.5050109@mac.com> X-PGP: 41F1741D User-Agent: mutt-ng/devel-r581 (FreeBSD) Subject: Re: Update from 6.0-RELEASE fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 16:58:07 -0000 --H+4ONPRPur6+Ovig Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Chuck Swiger wrote: > While brevity is a paramount virtue in writing-- and about that topic, I = cannot > say too much [1]-- however, Frank, you might want to consider the output = of > "swapinfo" and "top -o size". >=20 > Perhaps you don't have enough swap configured, or none at all? Okay, i had a look at swapinfo and top while it's installing and even nothing is swapped, so i think it's definitely not a memory/swap issue... Frank --H+4ONPRPur6+Ovig Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDpEObK0akcUHxdB0RAkIvAJsHsDijOFEudfJY7kwN9aiV5gs+5ACdFnyJ mYLlgsnStBG9Ird1m9/ooZc= =sLPC -----END PGP SIGNATURE----- --H+4ONPRPur6+Ovig-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 17:09:30 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F4C416A41F for ; Sat, 17 Dec 2005 17:09:30 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: from sarevok.lan.melvyn.homeunix.org (i153153.upc-i.chello.nl [62.195.153.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB6B243D49 for ; Sat, 17 Dec 2005 17:09:29 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: by sarevok.lan.melvyn.homeunix.org (Postfix, from userid 100) id C110A11454; Sat, 17 Dec 2005 18:09:28 +0100 (CET) From: Melvyn Sopacua To: freebsd-stable@freebsd.org Date: Sat, 17 Dec 2005 18:09:27 +0100 User-Agent: KMail/1.8.3 References: <20051217155800.GA63807@scott.blazing.de> <20051217161813.GA59494@xor.obsecurity.org> <20051217163726.GA22281@scott.blazing.de> In-Reply-To: <20051217163726.GA22281@scott.blazing.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512171809.28097.freebsd.stable@melvyn.homeunix.org> Subject: Re: Update from 6.0-RELEASE fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 17:09:30 -0000 On Saturday 17 December 2005 17:37, Frank Steinborn wrote: > Kris Kennaway wrote: > > > strip: /usr/libexec/bootpd: Memory exhausted > > > > Well, is it? > > I don't think so, i have nothing in logs that something is going to be > killed and i still have space in swap. Can you strip bootpd after install? -- Melvyn Sopacua freebsd.stable@melvyn.homeunix.org FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 17:14:17 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A66BF16A41F for ; Sat, 17 Dec 2005 17:14:17 +0000 (GMT) (envelope-from martinkov@pobox.sk) Received: from smtp.dkm.cz (smtp.dkm.cz [62.24.64.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 9696E43D73 for ; Sat, 17 Dec 2005 17:14:07 +0000 (GMT) (envelope-from martinkov@pobox.sk) Received: (qmail 25685 invoked by uid 0); 17 Dec 2005 17:14:02 -0000 Received: from r5k4.chello.upc.cz (HELO ?86.49.10.4?) (86.49.10.4) by smtp.dkm.cz with SMTP; 17 Dec 2005 17:14:02 -0000 Message-ID: <43A44759.805@pobox.sk> Date: Sat, 17 Dec 2005 18:14:01 +0100 From: martinko User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051205 X-Accept-Language: sk, cs, en-gb, en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20051216202938.GA36252@nowhere> <20051216205327.4D7BF5D09@ptavv.es.net> In-Reply-To: <20051216205327.4D7BF5D09@ptavv.es.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Melvyn Sopacua , freebsd-stable@freebsd.org Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 17:14:17 -0000 Kevin Oberman wrote: >>Date: Fri, 16 Dec 2005 14:29:39 -0600 >>From: Craig Boston >>Sender: owner-freebsd-stable@freebsd.org >> >> >>>-cpu0: on acpi0 >>>+cpu0: on acpi0 >>> >>>Q: Guessing that's a formatting difference, rather then 6.x not recognizing >>>the states (sysctl hw.acpi.cpu.cx_supported confirms 4 states) >> >>Not sure on this, but you're probably better off using EST anyway as I >>think it gives you more control over the processor frequency. > > > No. There is no conflict between Cx states and EST. Cx states specifies > how deeply the CPU will sleep when idle. EST controls processor speed > and voltage. In most cases, your REALLY want to use both of these. They > are very significant in saving power. (Of course, USB tends to limit the > effectiveness of Cx states. I need to run without USB to get really good > battery life and to make suspend (S3) really ut power drain. Kevin, I used to have 3 Cx states supported when I started with FreeBSD on version 5.3. Since I upgraded to 5.4 and recently to 6.0, all I can see is just one supported Cx state. I much wonder why. (?) Cheers, Martin From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 18:22:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14DBF16A41F for ; Sat, 17 Dec 2005 18:22:27 +0000 (GMT) (envelope-from billn@ywave.com) Received: from smtpout1.ywave.com (ycomradius.yelmtel.com [216.227.100.60]) by mx1.FreeBSD.org (Postfix) with SMTP id 4EB8F43D64 for ; Sat, 17 Dec 2005 18:22:26 +0000 (GMT) (envelope-from billn@ywave.com) Received: (qmail 27942 invoked by uid 502); 17 Dec 2005 18:22:25 -0000 Received: from dsl13091.ywave.com (HELO ?10.0.0.25?) (billn@66.243.212.91) by 0 with SMTP; 17 Dec 2005 18:22:25 -0000 X-CLIENT-IP: 66.243.212.91 X-CLIENT-HOST: dsl13091.ywave.com Message-ID: <43A45789.7080601@ywave.com> Date: Sat, 17 Dec 2005 10:23:05 -0800 From: Bill Nicholls User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.7.12) Gecko/20050922 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20051217120101.BBEDB16A440@hub.freebsd.org> In-Reply-To: <20051217120101.BBEDB16A440@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Release Schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 18:22:27 -0000 Let me add my voice to this discussion. I have been a happy user of FreeBSD from 4.0 thru 4.11, but have stumbled repeatedly on 5.x and now 6.0. For some reason, I can get these (5 & 6) installed, but not stable or running KDE, yet 4.11 runs solid for months. In addition, not being able to run KDE from Generic has been an additional headache. This has become such a problem that I finally loaded Suse Linux 10 on my alternate disk so I can move ahead. I use dual 9G disks and alternate installs, stairstepping from one release to the next, with the ability to boot back to an older release. This has worked well until now. This is particularly bad timing because FreeBSD is my *preferred* OS for significant parts of my work, and it was planned to host an important DB project on another machine bought for that purpose. I was hoping that 6.0 would enable me to move ahead on my FreeBSD workstation, and then on my DB project. Instead I am stalled and forced to go to a less preferred solution. I don't know what, if anything, I am doing wrong. I gave away an expensive SOYO MB because FreeBSD would not install, later found out that the advanced SOYO ACPI was the problem, apparently solved later. Color me frustrated. For me the issue is very simple - I need to install release X.Y, install KDE, configure X and get to work. Becoming an internals expert or even small time developer is not what I need to do even though I have done that kind of work in the past. Now I concentrate on getting applications into production, with OS maintenence limited to chasing glitches. Color me very frustrated. I've been used to great stability on FreeBSD, less frequent changes than Linux, and fewer problems. The system just *worked*. No longer. I don't blame anybody on the team for this issue because from my POV, the attention on getting better SMP and generally upgrading the kernel quality was and is a good objective. However, along the way, a few less obvious characteristics have lost out. When it gets to the point that I am forced to use something else despite my efforts, then attention needs to be spent making FreeBSD work 'Out of the Box' again. Simple is good - you can always get complicated if that is your preference, but for a lot of us, FreeBSD is a tool, not a career. Again, this is not a flame but a plea to make the system simply work. BillN http://www.billswrite.com From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 20:35:05 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 476CA16A41F for ; Sat, 17 Dec 2005 20:35:05 +0000 (GMT) (envelope-from frank@ircnow.org) Received: from scott.blazing.de (scott.blazing.de [80.86.187.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5388C43D58 for ; Sat, 17 Dec 2005 20:35:04 +0000 (GMT) (envelope-from frank@ircnow.org) Received: by scott.blazing.de (Postfix, from userid 510) id 3BA1A823BE; Sat, 17 Dec 2005 21:35:03 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on scott.blazing.de X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from shodan.nognu.de (unknown [85.14.216.230]) by scott.blazing.de (Postfix) with ESMTP id 45712823AE for ; Sat, 17 Dec 2005 21:35:00 +0100 (CET) Received: by shodan.nognu.de (nbSMTP-1.00) for uid 1002 frank@ircnow.org; Sat, 17 Dec 2005 21:35:00 +0100 (CET) Date: Sat, 17 Dec 2005 21:34:58 +0100 From: Frank Steinborn To: freebsd-stable@freebsd.org Message-ID: <20051217203457.GA84442@scott.blazing.de> Mail-Followup-To: freebsd-stable@freebsd.org References: <20051217155800.GA63807@scott.blazing.de> <20051217161813.GA59494@xor.obsecurity.org> <20051217163726.GA22281@scott.blazing.de> <200512171809.28097.freebsd.stable@melvyn.homeunix.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <200512171809.28097.freebsd.stable@melvyn.homeunix.org> X-PGP: 41F1741D User-Agent: mutt-ng/devel-r581 (FreeBSD) Subject: Re: Update from 6.0-RELEASE fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 20:35:05 -0000 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Melvyn Sopacua wrote: > Can you strip bootpd after install? If you mean whether I can run "strip bootpd": kellerkind:/usr/src# strip bootpd strip: 'bootpd': No such file I'm clueless at the moment. Frank --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDpHZxK0akcUHxdB0RAvvIAKDLXOJlVYgGhBdmJPFNU4eamqLf/gCfVeOm W5yxReu3Gh18Fv0nbI/4vRk= =h0Gk -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 20:41:21 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC77316A41F for ; Sat, 17 Dec 2005 20:41:21 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: from sarevok.lan.melvyn.homeunix.org (i153153.upc-i.chello.nl [62.195.153.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4F3843D5E for ; Sat, 17 Dec 2005 20:41:20 +0000 (GMT) (envelope-from freebsd.stable@melvyn.homeunix.org) Received: by sarevok.lan.melvyn.homeunix.org (Postfix, from userid 100) id 9A8AB11437; Sat, 17 Dec 2005 21:41:19 +0100 (CET) From: Melvyn Sopacua To: freebsd-stable@freebsd.org Date: Sat, 17 Dec 2005 21:41:17 +0100 User-Agent: KMail/1.8.3 References: <20051217155800.GA63807@scott.blazing.de> <200512171809.28097.freebsd.stable@melvyn.homeunix.org> <20051217203457.GA84442@scott.blazing.de> In-Reply-To: <20051217203457.GA84442@scott.blazing.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512172141.18017.freebsd.stable@melvyn.homeunix.org> Subject: Re: Update from 6.0-RELEASE fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 20:41:21 -0000 On Saturday 17 December 2005 21:34, Frank Steinborn wrote: > Melvyn Sopacua wrote: > > Can you strip bootpd after install? > > If you mean whether I can run "strip bootpd": > > kellerkind:/usr/src# strip bootpd > strip: 'bootpd': No such file > > I'm clueless at the moment. strip /usr/libexec/bootpd -- Melvyn Sopacua freebsd.stable@melvyn.homeunix.org FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 21:17:38 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E722716A41F for ; Sat, 17 Dec 2005 21:17:38 +0000 (GMT) (envelope-from delphij@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6262F43D46 for ; Sat, 17 Dec 2005 21:17:38 +0000 (GMT) (envelope-from delphij@gmail.com) Received: by wproxy.gmail.com with SMTP id i31so884164wra for ; Sat, 17 Dec 2005 13:17:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=czD/0zlv3S0n798C0kkXj+fSsglikaM+7klI3DHwmkRleNYs5E94UH3Zg/Cpz4sHVOMR3OLyNMz40nB2tL3x5heGM0WFVu1kmtezTawPVysPXqn+SabRF+a6W+u0T38X8lokBmKJNL94thAAWd8YOFm9XvJdJFHNwv0gdKPcv2s= Received: by 10.65.183.7 with SMTP id k7mr1068547qbp; Sat, 17 Dec 2005 13:17:37 -0800 (PST) Received: by 10.65.72.5 with HTTP; Sat, 17 Dec 2005 13:17:37 -0800 (PST) Message-ID: Date: Sun, 18 Dec 2005 05:17:37 +0800 From: Xin LI To: Peter Jeremy In-Reply-To: <20051216205446.GS77268@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20051216193942.GA92029@xor.obsecurity.org> <20051216205446.GS77268@cirb503493.alcatel.com.au> Cc: freebsd-stable Subject: Re: indefinite wait buffer: Does this indicate hardware issue? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: delphij@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 21:17:39 -0000 SGksIFBldGVyLAoKT24gMTIvMTcvMDUsIFBldGVyIEplcmVteSA8UGV0ZXJKZXJlbXlAb3B0dXNo b21lLmNvbS5hdT4gd3JvdGU6Cj4gT24gU2F0LCAyMDA1LURlYy0xNyAwNDowNjozNiArMDgwMCwg WGluIExJIHdyb3RlOgo+ID5ObywgaXQncyBzb21ldGltZXMgb3RoZXIsIGFuZCBpcyBxdWl0ZSBp bmZyZXF1ZW50LiAgT24gdGhlIG90aGVyIGhhbmQsCj4gPm5laXRoZXIgU01BUlQgbm9yIGVycm9y IGhhcyByZXBvcnRlZCBzb21lIGluY2lkZW50LCBzbyBJIHdhcyBzdHVjawo+ID53aGVuIGxvb2tp bmcgb24gaGFyZHdhcmUgaXNzdWVzLCBhcyB0aGUgbWVzc2FnZSBkb2VzIG5vdCBpbmRpY2F0ZQo+ ID53aGljaCBkaXNrKHMpIG1heSBoYXZlIHByb2JsZW0uLi4KPgo+IEEgaGFyZHdhcmUgZXJyb3Ig c2hvdWxkIGhhdmUgYmVlbiByZXBvcnRlZCBhcyBzdWNoLiAgQnV0IGlmIHlvdQo+IHN1c3BlY3Qg YSBkaXNrIHByb2JsZW0sIHRyeSBkZCdpbmcgdGhlIHN3YXAgcGFydGl0aW9uIChvciB0aGUgd2hv bGUKPiBkaXNrKSB0byAvZGV2L251bGwuICBJZiB5b3UgY2FuIHJlYWQgdGhlIHdob2xlIHBhcnRp dGlvbiwgeW91IGNhbgo+IHByb2JhYmx5IHdyaXRlIHRvIGl0LiAgKE9yIHlvdSBjb3VsZCBkZCAv ZGV2L3plcm8gdG8gdGhlIHBhcnRpdGlvbnMKPiB3aGlsc3Qgc3dhcCBpcyBub3QgYXR0YWNoZWQg LSBlZyBpbiBzaW5nbGUgdXNlciBhZnRlciBib290KS4gIElmIHlvdQo+IHN1c3BlY3QgcmV0cmll cyBhcmUgYSBwcm9ibGVtLCBtb25pdG9yIHRoZSBJL08gcmF0ZSB3aXRoIGlvc3RhdCBvcgo+IHN5 c3RhdCBhbmQgc2VlIGlmIGl0IHN1ZGRlbmx5IGRyb3BzLgoKQWN0dWFsbHkgSSBhbHJlYWR5IHRy aWVkIHRvIGRkIHdpdGggbm8gbHVjay4uLiAgSSBzdXNwZWN0IHRoYXQgdGhlCmNhYmxlIG1heSBo YXZlIHNvbWUgcHJvYmxlbXMsIHRob3VnaCwgYXMgYSBoYXJkIGRpc2sgaXMgd29ya2luZyBhdApo YWxmIHNwZWVkIG9mIHRoZSBvdGhlciBvbmUgKHNheSwgaXQncyBub3QgYSBzdWRkZW4gZHJvcCku Li4gIEJ1dCB3aWxsCnRoaXMgY2F1c2UgdGhlIHdhcm5pbmc/CgpDaGVlcnMsCi0tClhpbiBMSSA8 ZGVscGhpakBkZWxwaGlqLm5ldD4gaHR0cDovL3d3dy5kZWxwaGlqLm5ldAo= From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 21:54:40 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 874BF16A41F; Sat, 17 Dec 2005 21:54:40 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C8FC43D5F; Sat, 17 Dec 2005 21:54:40 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jBHLsdQL021353; Sat, 17 Dec 2005 13:54:39 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jBHLsYtK093159; Sat, 17 Dec 2005 13:54:34 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jBHLsYas093158; Sat, 17 Dec 2005 13:54:34 -0800 (PST) (envelope-from jrhett) Date: Sat, 17 Dec 2005 13:54:34 -0800 From: Joe Rhett To: Scott Long Message-ID: <20051217215434.GB92180@svcolo.com> References: <43A266E5.3080103@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43A266E5.3080103@samsco.org> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 21:54:40 -0000 On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: > There will be three FreeBSD 6 releases in 2006. While this is nice, may I suggest that it is time to put aside/delay one release cycle and come up with a binary update mechanism supported well by the OS? Increasing the speed of releases is good. Increasing the number of deployed systems out of date because there are no easy binary upgrade mechanisms is bad. It has been bad, it's getting worse. -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 21:55:10 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89B6F16A41F for ; Sat, 17 Dec 2005 21:55:10 +0000 (GMT) (envelope-from frank@ircnow.org) Received: from scott.blazing.de (scott.blazing.de [80.86.187.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A57643D68 for ; Sat, 17 Dec 2005 21:55:09 +0000 (GMT) (envelope-from frank@ircnow.org) Received: by scott.blazing.de (Postfix, from userid 510) id F39E5823CF; Sat, 17 Dec 2005 22:55:07 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on scott.blazing.de X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from shodan.nognu.de (unknown [85.14.216.230]) by scott.blazing.de (Postfix) with ESMTP id F1674823C6 for ; Sat, 17 Dec 2005 22:55:05 +0100 (CET) Received: by shodan.nognu.de (nbSMTP-1.00) for uid 1002 frank@ircnow.org; Sat, 17 Dec 2005 22:55:05 +0100 (CET) Date: Sat, 17 Dec 2005 22:55:05 +0100 From: Frank Steinborn To: freebsd-stable@freebsd.org Message-ID: <20051217215505.GA29499@scott.blazing.de> Mail-Followup-To: freebsd-stable@freebsd.org References: <20051217155800.GA63807@scott.blazing.de> <200512171809.28097.freebsd.stable@melvyn.homeunix.org> <20051217203457.GA84442@scott.blazing.de> <200512172141.18017.freebsd.stable@melvyn.homeunix.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline In-Reply-To: <200512172141.18017.freebsd.stable@melvyn.homeunix.org> X-PGP: 41F1741D User-Agent: mutt-ng/devel-r581 (FreeBSD) Subject: Re: Update from 6.0-RELEASE fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 21:55:10 -0000 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Melvyn Sopacua wrote: > strip /usr/libexec/bootpd strip: '/usr/libexec/bootpd': No such file Frank --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDpIk5K0akcUHxdB0RAjO2AKCAog2kB0XZC8Py9D16eoCXVxiqHQCbB6Uv 0oBBGe8mnQmSK5FwVfokkMc= =0Doo -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 22:00:27 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8638F16A41F; Sat, 17 Dec 2005 22:00:27 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CAFA43D53; Sat, 17 Dec 2005 22:00:27 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jBHM0RQL021620; Sat, 17 Dec 2005 14:00:27 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jBHM0LK0094649; Sat, 17 Dec 2005 14:00:21 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jBHM0LiU094647; Sat, 17 Dec 2005 14:00:21 -0800 (PST) (envelope-from jrhett) Date: Sat, 17 Dec 2005 14:00:21 -0800 From: Joe Rhett To: Scott Long Message-ID: <20051217220021.GB93998@svcolo.com> References: <43A266E5.3080103@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43A266E5.3080103@samsco.org> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: stable@freebsd.org, current Subject: Fast releases demand binary updates.. (Was: Release schedule for 2006) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 22:00:27 -0000 On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: > There will be three FreeBSD 6 releases in 2006. While this is nice, may I suggest that it is time to put aside/delay one release cycle and come up with a binary update mechanism supported well by the OS? Increasing the speed of releases is good. Increasing the number of deployed systems out of date because there are no easy binary upgrade mechanisms is bad. It has been bad, it's getting worse. -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 22:08:14 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA15016A41F; Sat, 17 Dec 2005 22:08:14 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr7.xs4all.nl (smtp-vbr7.xs4all.nl [194.109.24.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEB9143D5C; Sat, 17 Dec 2005 22:08:13 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr7.xs4all.nl (8.13.3/8.13.3) with ESMTP id jBHM8818024849; Sat, 17 Dec 2005 23:08:08 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id jBHM87gT028757; Sat, 17 Dec 2005 23:08:07 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id jBHM873S028756; Sat, 17 Dec 2005 23:08:07 +0100 (CET) (envelope-from wb) Date: Sat, 17 Dec 2005 23:08:07 +0100 From: Wilko Bulte To: Joe Rhett Message-ID: <20051217220807.GA28741@freebie.xs4all.nl> References: <43A266E5.3080103@samsco.org> <20051217215434.GB92180@svcolo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051217215434.GB92180@svcolo.com> X-OS: FreeBSD 6.0-STABLE User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 22:08:14 -0000 On Sat, Dec 17, 2005 at 01:54:34PM -0800, Joe Rhett wrote.. > On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: > > There will be three FreeBSD 6 releases in 2006. > > While this is nice, may I suggest that it is time to put aside/delay one > release cycle and come up with a binary update mechanism supported well by > the OS? Increasing the speed of releases is good. Increasing the number > of deployed systems out of date because there are no easy binary upgrade > mechanisms is bad. > > It has been bad, it's getting worse. So, when will you fix it? Or hire someone to fix it? FreeBSD after all is mostly a volunteer operation. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 22:35:45 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DB7D16A41F; Sat, 17 Dec 2005 22:35:45 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from server.t-hosting.hu (server.t-hosting.hu [217.20.133.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id E85B343D53; Sat, 17 Dec 2005 22:35:44 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from localhost (localhost [127.0.0.1]) by server.t-hosting.hu (Postfix) with ESMTP id 01895998419; Sat, 17 Dec 2005 23:35:43 +0100 (CET) Received: from server.t-hosting.hu ([127.0.0.1]) by localhost (server.t-hosting.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 44714-04; Sat, 17 Dec 2005 23:35:39 +0100 (CET) Received: from [80.98.231.227] (catv-5062e7e3.catv.broadband.hu [80.98.231.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.t-hosting.hu (Postfix) with ESMTP id 916259983EE; Sat, 17 Dec 2005 23:35:39 +0100 (CET) Message-ID: <43A492B6.6050305@t-hosting.hu> Date: Sat, 17 Dec 2005 23:35:34 +0100 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Wilko Bulte References: <43A266E5.3080103@samsco.org> <20051217215434.GB92180@svcolo.com> <20051217220807.GA28741@freebie.xs4all.nl> In-Reply-To: <20051217220807.GA28741@freebie.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at t-hosting.hu Cc: Joe Rhett , stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 22:35:45 -0000 Wilko Bulte wrote: >On Sat, Dec 17, 2005 at 01:54:34PM -0800, Joe Rhett wrote.. > > >>On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: >> >> >>>There will be three FreeBSD 6 releases in 2006. >>> >>> >>While this is nice, may I suggest that it is time to put aside/delay one >>release cycle and come up with a binary update mechanism supported well by >>the OS? Increasing the speed of releases is good. Increasing the number >>of deployed systems out of date because there are no easy binary upgrade >>mechanisms is bad. >> >>It has been bad, it's getting worse. >> >> > >So, when will you fix it? Or hire someone to fix it? FreeBSD after >all is mostly a volunteer operation. > > > I agree. And after all, tracking a security branch isn't too difficult, but the most people think that they have to do a complete "make buildworld" after a security advisory, but this isn't true. For example there was that cvsbug issue in September: ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-05:20.cvsbug.asc One can read here: b) Execute the following commands as root: # cd /usr/src # patch < /path/to/patch # cd /usr/src/gnu/usr.bin/cvs/cvsbug # make obj && make depend && make && make install # cd /usr/src/gnu/usr.bin/send-pr # make obj && make depend && make && make install Is that difficult? I don't think so. No reboot required and it doesn't take more than 5 minutes even on a slower machine. Only the vulnerabilities in the kernel are problematic for servers, since they require a reboot. I think I'll submit a PR with a patch to clarify this in Handbook. Do you consider this useful? Regards, Gabor Kovesdan From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 23:20:53 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D74016A41F for ; Sat, 17 Dec 2005 23:20:53 +0000 (GMT) (envelope-from mark@mkproductions.org) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CAA343D4C for ; Sat, 17 Dec 2005 23:20:51 +0000 (GMT) (envelope-from mark@mkproductions.org) Received: from pimout3-ext.prodigy.net (pimout3-int.prodigy.net [207.115.4.218]) by ylpvm29.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id jBHNKuri012941 for ; Sat, 17 Dec 2005 18:20:56 -0500 X-ORBL: [68.89.209.57] Received: from [192.168.1.25] (68-89-209-57.ded.swbell.net [68.89.209.57]) by pimout3-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id jBHNKfac140284; Sat, 17 Dec 2005 18:20:49 -0500 Message-ID: <43A49D46.40301@mkproductions.org> Date: Sat, 17 Dec 2005 17:20:38 -0600 From: Mark Kane User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051130) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bill Nicholls References: <20051217120101.BBEDB16A440@hub.freebsd.org> <43A45789.7080601@ywave.com> In-Reply-To: <43A45789.7080601@ywave.com> X-Enigmail-Version: 0.93.0.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF913370F768B9BE431F60354" Cc: freebsd-stable@freebsd.org Subject: Re: Release Schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 23:20:53 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF913370F768B9BE431F60354 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Bill Nicholls wrote: > Let me add my voice to this discussion. I have been a happy user of > FreeBSD from 4.0 thru 4.11, but have stumbled repeatedly on 5.x and now > 6.0. > > For some reason, I can get these (5 & 6) installed, but not stable or > running KDE, yet 4.11 runs solid for months. In addition, not being able > to run KDE from Generic has been an additional headache. > > This has become such a problem that I finally loaded Suse Linux 10 on my > alternate disk so I can move ahead. I use dual 9G disks and alternate > installs, stairstepping from one release to the next, with the ability > to boot back to an older release. This has worked well until now. > > This is particularly bad timing because FreeBSD is my *preferred* OS for > significant parts of my work, and it was planned to host an important > DB project on another machine bought for that purpose. > > I was hoping that 6.0 would enable me to move ahead on my FreeBSD > workstation, and then on my DB project. Instead I am stalled and forced > to go to a less preferred solution. > > I don't know what, if anything, I am doing wrong. I gave away an > expensive SOYO MB because FreeBSD would not install, later found out > that the advanced SOYO ACPI was the problem, apparently solved later. > > Color me frustrated. For me the issue is very simple - I need to install > release X.Y, install KDE, configure X and get to work. Becoming an > internals expert or even small time developer is not what I need to do > even though I have done that kind of work in the past. Now I concentrate > on getting applications into production, with OS maintenence limited to > chasing glitches. > > Color me very frustrated. I've been used to great stability on FreeBSD, > less frequent changes than Linux, and fewer problems. The system just > *worked*. No longer. > > I don't blame anybody on the team for this issue because from my POV, > the attention on getting better SMP and generally upgrading the kernel > quality was and is a good objective. However, along the way, a few less > obvious characteristics have lost out. > > When it gets to the point that I am forced to use something else despite > my efforts, then attention needs to be spent making FreeBSD work 'Out of > the Box' again. Simple is good - you can always get complicated if that > is your preference, but for a lot of us, FreeBSD is a tool, not a career. > > Again, this is not a flame but a plea to make the system simply work. I do not know your situation or what you have tried in order to resolve your problems, but I do know that I have several FreeBSD machines as desktops and they all work great. My main desktop is an Athlon64 3000+ running FreeBSD 5.4-RELEASE [amd64]. I am not sure why you have not been able to get X and KDE running. I don't use KDE anymore, but it was extremely simple to get X and my window manager (Xfce) up and running. I installed the Xorg and Xfce4 metaports and it was as simple as that. I did the "Xorg -configure" steps outlined in the handbook, copied the configuration file to the proper place, and I was up and running. I cannot code anything but I had the system up and running in only the time it took to compile things and modify a few config files. I've also setup FreeBSD as a desktop on my Athlon XP 2000+ (FreeBSD 5.4-RELEASE) which did run KDE before, my Athlon XP 1800+ (FreeBSD 5.4-RELEASE), and my 533MHz Compaq Laptop (FreeBSD 6.0-RC1). All of those were able to get X and my window manager of choice (Xfce on two, and fvwm on laptop) installed very quickly and easily through ports (and packages on laptop). I have not used 6.0-RELEASE at all yet, and only use my laptop with RC1 of 6.0 a little. So far there have been no issues with any of my machines except one random reboot on my amd64 that I have yet to track down. However, my point is that most people do not have problems that prevent them from getting a working machine or have the need to modify code as you said you do. That's the beauty of the ports system. You can install things easily that were "ported" to work with FreeBSD. Whether applications require special configure arguments, code changes, or other settings, the ports system is there to automate that whole process and build things so they do work right. I'm not blaming it on you or saying it's your error, but without knowing the actual issues I must say it sounds very weird and isolated. Just one thing to keep in mind though: If you have issues, why not ask the very helpful FreeBSD community? Mailing lists like freebsd-questions have great people who are willing to help people out with questions and issues like yours. I've gotten help there when I've had some weird problems and I also try to help whenever I can. In other words, if it was me, I would try my best to solve it first before switching operating systems...especially since I love FreeBSD so much. Again, I don't know your particular issues/problems, but I am certain there would be some help available for you. Just my input/comments. -Mark -- GnuPG Public Key: http://www.mkproductions.org/mk_pubkey.asc Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) --------------enigF913370F768B9BE431F60354 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDpJ1IlH2ybcmj7I8RAvCPAJ487jrusfkcWargbRaS/2vdYlW8QgCeLbUq eivB1dZKsnCX1bcqzo5THi4= =kKFX -----END PGP SIGNATURE----- --------------enigF913370F768B9BE431F60354-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 23:29:00 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDE2C16A41F; Sat, 17 Dec 2005 23:29:00 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail23.syd.optusnet.com.au (mail23.syd.optusnet.com.au [211.29.133.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C3B443D5A; Sat, 17 Dec 2005 23:28:59 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail23.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBHNSv79027788 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 18 Dec 2005 10:28:57 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBHNSuHh088005; Sun, 18 Dec 2005 10:28:56 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBHNSuPf088004; Sun, 18 Dec 2005 10:28:56 +1100 (EST) (envelope-from pjeremy) Date: Sun, 18 Dec 2005 10:28:56 +1100 From: Peter Jeremy To: =?iso-8859-1?Q?K=F6vesd=E1n_G=E1bor?= Message-ID: <20051217232856.GT77268@cirb503493.alcatel.com.au> References: <43A266E5.3080103@samsco.org> <20051217215434.GB92180@svcolo.com> <20051217220807.GA28741@freebie.xs4all.nl> <43A492B6.6050305@t-hosting.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <43A492B6.6050305@t-hosting.hu> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 23:29:01 -0000 On Sat, 2005-Dec-17 23:35:34 +0100, Kövesdán Gábor wrote: >I agree. And after all, tracking a security branch isn't too difficult, ... ># cd /usr/src ># patch < /path/to/patch ># cd /usr/src/gnu/usr.bin/cvs/cvsbug ># make obj && make depend && make && make install ># cd /usr/src/gnu/usr.bin/send-pr ># make obj && make depend && make && make install > >Is that difficult? Speaking as a developer, I think it's trivially easy. As an end user, I don't think this is acceptable. Firstly, it requires that the user has installed the src distribution - which is optional. Secondly, the user is expected to use development tools without understanding what they do - this is scary for them. Running the above commands is OK as long as nothing goes wrong but the "support" group (who inhabit -questions and answer seemingly silly questions) are going to have to cope with people who've made a typo somewhere in the sequence and can't explain exactly what they did - without putting them off FreeBSD. I think FreeBSD Update shows the way forward but IMHO there needs to be an "official" binary update tool accessible from www.freebsd.org. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 23:44:53 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF73716A420 for ; Sat, 17 Dec 2005 23:44:53 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3608E43D69 for ; Sat, 17 Dec 2005 23:44:50 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 005B31A3C25; Sat, 17 Dec 2005 15:44:50 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 048FB5128F; Sat, 17 Dec 2005 18:44:48 -0500 (EST) Date: Sat, 17 Dec 2005 18:44:48 -0500 From: Kris Kennaway To: Bill Nicholls Message-ID: <20051217234448.GA68713@xor.obsecurity.org> References: <20051217120101.BBEDB16A440@hub.freebsd.org> <43A45789.7080601@ywave.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <43A45789.7080601@ywave.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Release Schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 23:44:54 -0000 --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 17, 2005 at 10:23:05AM -0800, Bill Nicholls wrote: > Let me add my voice to this discussion. I have been a happy user of=20 > FreeBSD from 4.0 thru 4.11, but have stumbled repeatedly on 5.x and now 6= .0. It looks like in the course of writing your long email you forgot to describe any of the problems you are having. Kris --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDpKLwWry0BWjoQKURAiAHAKDepVeSfl2TWe3Kp1vpLCItNenFSwCfTa4B qz0Fqz7/fFFqJ3X1QbIckgc= =Pvpt -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 23:46:48 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C39F216A41F; Sat, 17 Dec 2005 23:46:48 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C43DF43D8D; Sat, 17 Dec 2005 23:46:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 349321A3C27; Sat, 17 Dec 2005 15:46:28 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6E2E751257; Sat, 17 Dec 2005 18:46:27 -0500 (EST) Date: Sat, 17 Dec 2005 18:46:27 -0500 From: Kris Kennaway To: Joe Rhett Message-ID: <20051217234627.GB68713@xor.obsecurity.org> References: <43A266E5.3080103@samsco.org> <20051217220021.GB93998@svcolo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mxv5cy4qt+RJ9ypb" Content-Disposition: inline In-Reply-To: <20051217220021.GB93998@svcolo.com> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org, current Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 23:46:48 -0000 --mxv5cy4qt+RJ9ypb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 17, 2005 at 02:00:21PM -0800, Joe Rhett wrote: > On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: > > There will be three FreeBSD 6 releases in 2006. >=20 > While this is nice, may I suggest that it is time to put aside/delay one > release cycle and come up with a binary update mechanism supported well by > the OS? Increasing the speed of releases is good. Increasing the number > of deployed systems out of date because there are no easy binary upgrade > mechanisms is bad. >=20 > It has been bad, it's getting worse. Suggestions are nice, but who do you think will work on solving this? Kris --mxv5cy4qt+RJ9ypb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDpKNTWry0BWjoQKURArrgAJ46xm5kLCiEpGDtHeWHA8L3fkjMCgCeLTiu UfX7Pm71Cu1oNGyQ+QHj3vc= =Qoqa -----END PGP SIGNATURE----- --mxv5cy4qt+RJ9ypb-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 23:55:06 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25EA316A41F; Sat, 17 Dec 2005 23:55:06 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7F4643D53; Sat, 17 Dec 2005 23:55:05 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id E768A5EA2; Sat, 17 Dec 2005 18:55:04 -0500 (EST) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28850-03; Sat, 17 Dec 2005 18:55:04 -0500 (EST) Received: from [192.168.1.3] (pool-68-161-122-227.ny325.east.verizon.net [68.161.122.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id D0A8E5E80; Sat, 17 Dec 2005 18:55:03 -0500 (EST) Message-ID: <43A4A557.3010600@mac.com> Date: Sat, 17 Dec 2005 18:55:03 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joe Rhett References: <43A266E5.3080103@samsco.org> <20051217220021.GB93998@svcolo.com> In-Reply-To: <20051217220021.GB93998@svcolo.com> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: stable@freebsd.org, current Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 23:55:06 -0000 Joe Rhett wrote: > On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: >>There will be three FreeBSD 6 releases in 2006. > > While this is nice, may I suggest that it is time to put aside/delay one > release cycle and come up with a binary update mechanism supported well by > the OS? Increasing the speed of releases is good. Increasing the number > of deployed systems out of date because there are no easy binary upgrade > mechanisms is bad. > > It has been bad, it's getting worse. YMMV. I burned a 6.0 release from the ISO image, and did a binary upgrade on an IBM ThinkPad (T.34? maybe), which worked perfectly. All of the 5.x binaries, including X11, KDE, printing, Mozilla, etc worked just fine. Upgrading the ports from there was somewhat annoying, as this guy's machine had ~400 or so, but deleting them all, and then using "pkg_add -r " works just fine if you want to grab the latest current binaries. From there you can portupgrade as usual. Now, if you want to talk about upgrading to intermediate patch releases, you've got a valid point there. :-) -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Sat Dec 17 23:58:29 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4084316A41F for ; Sat, 17 Dec 2005 23:58:29 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0537A43D5A for ; Sat, 17 Dec 2005 23:58:27 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Sat, 17 Dec 2005 15:58:24 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id BADD15D07; Sat, 17 Dec 2005 15:58:23 -0800 (PST) To: hartzell@alerce.com In-reply-to: Your message of "Fri, 16 Dec 2005 16:05:51 PST." <17315.22111.426723.110802@satchel.alerce.com> Date: Sat, 17 Dec 2005 15:58:23 -0800 From: "Kevin Oberman" Message-Id: <20051217235823.BADD15D07@ptavv.es.net> Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 23:58:29 -0000 > From: George Hartzell > Date: Fri, 16 Dec 2005 16:05:51 -0800 > > Kevin Oberman writes: > > [...] > > No. There is no conflict between Cx states and EST. Cx states specifies > > how deeply the CPU will sleep when idle. EST controls processor speed > > and voltage. In most cases, your REALLY want to use both of these. They > > are very significant in saving power. (Of course, USB tends to limit the > > effectiveness of Cx states. I need to run without USB to get really good > > battery life and to make suspend (S3) really ut power drain. > > Can you expand a bit on that "Of course USB...". What's the problem > with USB? Can one just kunload it before suspend? > > g. Only a bit. I believe it is the polling activity of the USB driver that causes the problem, but, if USB drivers are loaded, most systems will never get to the "deeper" sleep levels. My T30 has 3 sleep level of which C2 is only a very modest power savings over C1. C3 is a significant savings, but it is never used if USB devices are present. If you unload the drivers, you should be to lower levels. Take a look at sysctl hw.acpi.cpu for detail and to see how much time is spent in each sleep state. I assume that you can unload the drivers, but my kernel has USB at this time. I do plan on building a kernel without USB and see if unloading is a workable solution. I think it should be. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634