From owner-freebsd-hackers Wed Jan 26 13:43:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8881D14C56 for ; Wed, 26 Jan 2000 13:43:20 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id OAA20447; Wed, 26 Jan 2000 14:07:51 -0800 (PST) Date: Wed, 26 Jan 2000 14:07:51 -0800 From: Alfred Perlstein To: Scott Hess Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read crashing certain kernels. Message-ID: <20000126140751.F26520@fw.wintelcom.net> References: <01b301bf6824$46e928a0$1e80000a@avantgo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <01b301bf6824$46e928a0$1e80000a@avantgo.com>; from scott@avantgo.com on Wed, Jan 26, 2000 at 09:39:20AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Scott Hess [000126 10:08] wrote: > Since nobody here seems to be able to figure it out... I wrote a program to > play around with aio_read(), and it ran stellarly well on my > FreeBSD3.4-release system using EIDE hard drives. But, when I tried to run > it on a system using our production kernel with Adaptec SCSI controllers, > it locked the kernel up HARD. No console messages, no Ctrl-Alt-Del, had to > push the hard reset switch. > > The kernel in question is a FreeBSD3.4-release kernel compiled with a > different set of options (lots of mbufs, etc, etc). I can't find anything > in it that seems at all related to async I/O. The appropriate sysctl > values all seem the same between the systems. And the fact that it locks > the system up instead of saying ENOTSUPP or "async I/O not compiled in" > concerns me greatly. > > Any ideas on why this might be happening? No, please provide a debug traceback and file a PR, see: http://www.freebsd.org/handbook/kerneldebug.html thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message