From owner-freebsd-bugs Thu Dec 7 10: 0:12 2000 From owner-freebsd-bugs@FreeBSD.ORG Thu Dec 7 10:00:03 2000 Return-Path: <owner-freebsd-bugs@FreeBSD.ORG> Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id AE7E237B400 for <freebsd-bugs@hub.freebsd.org>; Thu, 7 Dec 2000 10:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id eB7I03j59103; Thu, 7 Dec 2000 10:00:03 -0800 (PST) (envelope-from gnats) Date: Thu, 7 Dec 2000 10:00:03 -0800 (PST) Message-Id: <200012071800.eB7I03j59103@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Kevin Day <toasty@temphost.dragondata.com> Subject: Re: i386/23347: New ATA code in 4.1.1+ breaks ServerWorks sym Reply-To: Kevin Day <toasty@temphost.dragondata.com> Sender: gnats@FreeBSD.org Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR i386/23347; it has been noted by GNATS. From: Kevin Day <toasty@temphost.dragondata.com> To: cdillon@wolves.k12.mo.us (Chris Dillon) Cc: bugs@FreeBSD.ORG, sos@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: i386/23347: New ATA code in 4.1.1+ breaks ServerWorks sym Date: Thu, 7 Dec 2000 11:55:35 -0600 (CST) > > After upgrading my Proliant ML530 server from 4.1 to 4.1.1, i got > > a panic on boot in the sym driver, saying "Unable to allocate IRQ > > resource", then a kernel trap. > > > > I narrowed down the breakage to a specific set of commits: > > > > Edit src/sys/dev/ata/ata-all.c > > Add delta 1.50.2.6 2000.08.22.08.41.28 sos > > Edit src/sys/dev/ata/ata-all.h > > Add delta 1.26.2.2 2000.08.22.08.41.29 sos > > Edit src/sys/dev/ata/ata-disk.c > > Add delta 1.60.2.6 2000.08.22.08.41.29 sos > > Edit src/sys/dev/ata/ata-dma.c > > Add delta 1.35.2.4 2000.08.22.08.41.29 sos > > Edit src/sys/dev/ata/atapi-cd.c > > Add delta 1.48.2.4 2000.08.22.08.41.29 sos > > Edit src/sys/dev/ata/atapi-cd.h > > Add delta 1.15.2.3 2000.08.22.08.41.29 sos > > Interesting. I narrowed down the problem to somewhere between August > 4 and August 19 (if you want to call that narrowing down), but these > commits occurred on August 22. My testing showed that it worked as of 2000.08.22.00.00.00, but not as of 2000.08.23.00.00.00 - I manually backed out each commit, until (I think) I proved it was those commits. > > This motherboard only has one IDE channel... at least, only one > > connector, and it's only designed to go to the CD-ROM. Everything > > else is SCSI. 4.1-RELEASE only saw the primary channel. But after > > that commit, it sees two channels. I don't know if this is correct > > or not, but the side effect is that the secondary IDE channel uses > > IRQ 15, which sym1 wants to use, and somehow can't share. > > I noticed the same thing. At first, I believe only the secondary > (ata1) IDE channel was recognized. Now both are recognized, > regardless of the BIOS settings. > > > Sym0 was sucessfully moved from 15 to 11, to avoid sharing i'm > > guessing... why didn't sym1 get moved, if that's the case? > > You should be able to move both of them in the system setup. You'll > have to use the "lock down" feature after changing settings to keep > other devices from using IRQ 15. > The servers are physically impossible for me to reach, so I'm not able to piddle in the system setup. In any case, whatever happened needs to be fixed, so that someone popping a CD in a new setup doesn't get a panic. -- Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message