From owner-freebsd-current Tue Feb 24 22:19:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17243 for freebsd-current-outgoing; Tue, 24 Feb 1998 22:19:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA17213 for ; Tue, 24 Feb 1998 22:19:33 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 25215 invoked by uid 1000); 25 Feb 1998 06:26:14 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-021598 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 24 Feb 1998 22:26:14 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: Re: Help needed with DPT card + Asus M/B Cc: freebsd-current@FreeBSD.ORG, Kingson Gunawan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Feb-98 Tom wrote: > > On Tue, 24 Feb 1998, Kingson Gunawan wrote: > >> Does anybody successfully run the DPT SmartRaid4 (PW-3334UW) with ASUS >> P2L97-DS? This combination keeps failing me... >> >> Detail: >> Asus P2L97-DS dual PII-300 >> 512MB SDRAM >> Intel EtherExpress 100B >> SB16-Vibra >> Matrox Millenium 2MB/VRAM >> >> Kernel: 3.0-980211-SNAP compiles with dpt0. >> >> Error message: >> >> dpt 0: xxx Lost Interrupts Recovered > > Check IRQ settings. Is anything else on the same IRQ as the DPT > controller? That is not it. Unless some other driver is stealing the PCI interrupt (which I do not know how to do with PCI). The message comes from the fact that I see the controller status register indicating an interrupt posted, but no interrupt delivered by the O/S for a whole second. There is a bit of race condition ther, so, once or twice a day is normal (Yes, I'll fix it ;-). What Kinkston is seeing is a total failure to boot. Wait! Try to disable caches on the board. Completely. It will run like a pig, but let's see if it is/not a cache coherency problem. > > Tom > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message