From owner-freebsd-current Wed Jan 17 11:48:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 30E3037B402; Wed, 17 Jan 2001 11:47:51 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0HJlmZ54346; Wed, 17 Jan 2001 20:47:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: current@FreeBSD.org, arch@FreeBSD.org, Randell Jesup , Soren Schmidt , Alfred Perlstein Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: Your message of "Wed, 17 Jan 2001 10:55:09 PST." Date: Wed, 17 Jan 2001 20:47:48 +0100 Message-ID: <54340.979760868@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Baldwin writes: > >On 17-Jan-01 Poul-Henning Kamp wrote: >> >>>Perhaps you can explain how you're able to trigger this instability >>>with a test script? Poul-Henning told me he just needed to do a >>>make -j256 world, I did 10 of them without a problem... >> >> Then you misunderstood me, I don't have anything in the dept >> of SMP hw which can trigger it. > >Ok, what _does_ trigger this then? My theory is that it's related to disk-IO. My guess is that it may be related to calling a *_strategy() routine from an interrupt routine. That is what sets ccd, ata-raid and vinum apart from normal disk-IO. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message