From owner-freebsd-hackers Wed Jan 26 9:41:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id 2B87E14D7A for ; Wed, 26 Jan 2000 09:41:18 -0800 (PST) (envelope-from scott@avantgo.com) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 381 for ; Wed, 26 Jan 2000 09:36:39 -0800 Message-ID: <01b301bf6824$46e928a0$1e80000a@avantgo.com> From: "Scott Hess" To: Subject: aio_read crashing certain kernels. Date: Wed, 26 Jan 2000 09:39:20 -0800 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 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? Thanks much, scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message