From owner-freebsd-scsi Thu Nov 30 9:28:50 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D69437B401 for ; Thu, 30 Nov 2000 09:28:48 -0800 (PST) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id LAA18122; Thu, 30 Nov 2000 11:28:36 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 30 Nov 2000 11:28:36 -0600 (CST) From: Chris Dillon To: Kevin Day Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sym driver in 4.1.1+ on Proliant In-Reply-To: <200011291950.NAA54487@temphost.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 29 Nov 2000, Kevin Day wrote: > I've got several Compaq Proliant ML530's with the internal '896 > SCSI controller. Everything works great on 4.1-RELEASE. Going to > 4.1.1 or 4.2 causes sym0 to say "Cannot allocate IRQ resource", > followed by a kernel trap inside the sym driver. Has anyone > experienced this, or know what I can try? I had this problem long before 4.1.1, several months ago, but I'm not exactly sure what caused it. I assume that your on-board SCSI controller is trying to use IRQ15. Go into the Compaq System Setup and make sure no devices are using IRQ15 except for possibly the on-board IDE controller (which is what is _supposed_ to be using it). That solved it for me. I've got a PR open on this, but I haven't yet had time to figure out exactly what caused it since it is on a production system. It might be a BIOS problem, but it definately works with some previous kernels and not with newer ones. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64 and PowerPC under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message