From owner-freebsd-current Wed Jan 17 11:41:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 919BE37B6A5; Wed, 17 Jan 2001 11:41:29 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0HJfIZ54249; Wed, 17 Jan 2001 20:41:18 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Alfred Perlstein Cc: Soren Schmidt , Randell Jesup , arch@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: Your message of "Wed, 17 Jan 2001 10:43:18 PST." <20010117104318.U7240@fw.wintelcom.net> Date: Wed, 17 Jan 2001 20:41:18 +0100 Message-ID: <54247.979760478@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010117104318.U7240@fw.wintelcom.net>, Alfred Perlstein writes: >* Poul-Henning Kamp [010117 10:25] wrote: >> >> >Perhaps you can explain how you're able to trigger this instability >> >with a test script? Poul-Henning told me he just needed to do a >> >make -j256 world, I did 10 of them without a problem... >> >> Then you misunderstood me, I don't have anything in the dept >> of SMP hw which can trigger it. > >If you could be more vague it would assist me greatly in figuring >out what's broken. I have been as clear as possible at all times, so if anything here has been vague, it gotta be in your end. The only reason why I'm in this fracas is to get people to take the anguished cries of sos seriously so that we don't loose our ATA maintainer... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message