From owner-freebsd-stable Fri Jun 21 2:34:38 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.firstcallgroup.co.uk (dilbert.firstcallgroup.co.uk [194.200.93.142]) by hub.freebsd.org (Postfix) with ESMTP id BF69437B40A for ; Fri, 21 Jun 2002 02:34:34 -0700 (PDT) Received: from pfrench by mailhost.firstcallgroup.co.uk with local (Exim 3.36 #1) id 17LKoD-0001RG-00; Fri, 21 Jun 2002 10:34:25 +0100 To: frank@exit.com, holger.kipp@alogis.com Subject: Re: Status of fxp / smp problem? Cc: pjklist@ekahuna.com, stable@FreeBSD.ORG In-Reply-To: <3D12EB49.3E3CC0D5@alogis.com> Message-Id: From: Pete French Date: Fri, 21 Jun 2002 10:34:25 +0100 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 > Not only sym/fxp, but also sym/ata, only sym, or only fxp or even others. Did we ever track down a time window as to *when* the changes were made thats caused this to start happening ? For me it was the update on May 22 that started it all going wrong, but I cant (unfortunately) remember what date of -STABLE the machine was running up until that point. > Problem seems to manifest itself especially on systems with: > - shared IRQs AND > - SMP enabled One added thing here - I had shared IRQ's between ata and sym, and the problem went away when I took the ata driver out of the kerenl. *but* I do not have any devices attached to the atat controller, so (preseumably) it could not have actually been interrupting ? Speculation: preseumably wth a shared IRQ the system scans devices it knows are attached to that IRQ until it finds one which needs service ? Any ideas what order it will do this in - i.e. would it be possible for it to scan ata, followed by sym, and for there to be some oddity in the IRQ code that stops it continuing on to scan sym under certain circumstances ? Unsure as to how this might happen, and I havent looked at the IRQ code, but I do have a machine on which I can reproduce the problem 100% reliably if that helps. -pcf. PS: committing that sym workaround would be really nice as I could at least then use our Compaq multiprocessor machines reliably. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message