From owner-freebsd-stable Fri Aug 17 13:25:30 2001 Delivered-To: freebsd-stable@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 F173737B401 for ; Fri, 17 Aug 2001 13:25:26 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) 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 PAA67912; Fri, 17 Aug 2001 15:25:23 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 17 Aug 2001 15:25:22 -0500 (CDT) From: Chris Dillon To: Warner Losh Cc: Subject: Re: DOH! Something PCI-related recently broken in -STABLE In-Reply-To: <200108170352.f7H3qaW37429@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 16 Aug 2001, Warner Losh wrote: > In message Chris Dillon writes: > : addition of PCI interrupt routing support, so I reverted sys/pci/pci.c > : to 1.141.2.7 and sys/pci/pcisupport.c to 1.154.2.6 to see if that > : would solve the problem, but it doesn't. > > You also need to back out pcibus.c to rev 1.57.2.2 to get rid of > changes there. This is the same code that current runs and has > been running for a very long time. I wouldn't have thought I'd > have broken anything given its age (predates the smpng changes). Aaah. That's one that I missed. I didn't think to look under the i386/isa directory for PCI-related stuff because, well, it says "isa". :-) > : I looked through the cvs-all archives and browsed through cvs logs to > : try and find something else that may have changed recently that could > : cause this, but nothing caught my eye. Anybody know of any > : PCI-related changes within the past three weeks or so that I should > : revert to try and narrow down the problem? > > I don't know of anything except my pci interrupt routing code that > would have touched this stuff at all. Maybe as an extra sanity check > you can cvsup to > > date=2001.08.15.04.04.00 tag=RELENG_4 > > just to make sure that you got everything. Ok, I've done that. Compiled a new kernel and everything works OK. The problem is occurring on a Compaq Proliant ML530, which is a ServerWorks ServerSet III LE based system. The other person that I know of seeing this problem (on the -scsi list, thinking it was a RAID controller problem) was using a Dell system, probably also ServerSet III LE based as well. I'm also using the most recent -STABLE on a SuperMicro 370DE6 which uses the ServerSet III HE-SL, and it has no problem with the new code. I'm about to update the BIOS on the Compaq box (it still has a late-1999 BIOS image on it) and see if that makes any difference. Could the BIOS matter in this case? -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet - Available for IA32 (Intel x86) and Alpha architectures - IA64, PowerPC, UltraSPARC, and ARM architectures under development - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message