Date: Wed, 7 Jun 2000 10:48:07 +0100 From: Jose Monteiro <jm@sindigit.pt> To: John <papalia@udel.edu> Cc: "Kenneth D. Merry" <ken@kdm.org>, John Lengeling <johnl@raccoon.com>, freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000607104807.O46433@sindigit.pt> In-Reply-To: <4.3.1.2.20000606224635.00ad3450@mail.udel.edu>; from papalia@udel.edu on Tue, Jun 06, 2000 at 10:47:16PM -0400 References: <20000601212248.A96817@panzer.kdm.org> <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <3935DAA5.7859492B@raccoon.com> <20000531233754.A88537@panzer.kdm.org> <393724F1.B90D3283@raccoon.com> <20000601212248.A96817@panzer.kdm.org> <20000605105023.B44716@sindigit.pt> <4.3.1.2.20000606224635.00ad3450@mail.udel.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/06/00 03:47 WEST, John wrote: > >after testing and testing (different disks, new controller, etc...) > >the problem turned out to be a faulty motherboard. Specificaly, one > >of the pci slots (curiously, an unused one) had electrical problems > >and thus the bus resets and master aborts. > > Now, forgive my ignorance (since in this case, it truly is ignorance), but > how do you actually find an electrical problem with an unused pci > slot? Multimeter and a lot of patience? actually, during the box setup, i sometimes noticed problems detecting any card installed on that particular slot. the suspicion arose and i isolated the slot, but kept using the board. probably some piece of metallic debris has fallen into the slot, or something similar. Justin Gibbs pointed out that having a faulty (even unused) pci slot is cause for parity errors on the pci bus. other causes can be an unproperly seated card or a faulty trace or chip connection on the motherboard. Jose Monteiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000607104807.O46433>