From owner-freebsd-current Wed Jan 17 10:57:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id E060737B400; Wed, 17 Jan 2001 10:57:12 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0HIrGL38308; Wed, 17 Jan 2001 10:53:16 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <53775.979755928@critter> Date: Wed, 17 Jan 2001 10:55:09 -0800 (PST) From: John Baldwin To: Poul-Henning Kamp Subject: Re: HEADS-UP: await/asleep removal imminent Cc: current@FreeBSD.org, arch@FreeBSD.org, Randell Jesup , Soren Schmidt , Alfred Perlstein Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-01 Poul-Henning Kamp wrote: > >>Perhaps you can explain how you're able to trigger this instability >>with a test script? Poul-Henning told me he just needed to do a >>make -j256 world, I did 10 of them without a problem... > > Then you misunderstood me, I don't have anything in the dept > of SMP hw which can trigger it. Ok, what _does_ trigger this then? And what kernel config are you using: GENERIC? GENERIC is rather plagued with problems right now due to its bloated size. There have been reports of people not being able to boot a freshly installed system because of the kernel bloat, so you really probably want to be using a custom kernel until that bug is found and uncovered. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message