From owner-freebsd-questions Fri Oct 2 03:10:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28442 for freebsd-questions-outgoing; Fri, 2 Oct 1998 03:10:43 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from amanda.qmpgmc.ac.uk ([194.81.5.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28434 for ; Fri, 2 Oct 1998 03:10:38 -0700 (PDT) (envelope-from greg@qmpgmc.ac.uk) Received: from Greg by amanda.qmpgmc.ac.uk (UUNET Amanda using sendmail V8.9.1a) id LAA20969; Fri, 2 Oct 1998 11:09:54 +0100 (BST) Message-ID: <00fc01bdedec$fb07d060$380051c2@Greg.qmpgmc.ac.uk> Reply-To: "Greg Quinlan" From: "Greg Quinlan" To: Subject: PCI IRQ sharing! Date: Fri, 2 Oct 1998 11:11:05 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00F9_01BDEDF5.596C92A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_00F9_01BDEDF5.596C92A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable While talking (E-mail) to SuperMicro about a problem with an Adaptec = 3940UW OR a 2940UW and one of their motherboards. (P6DLH motherboard, i960 I/O controller) I suggested that there was some fundamental design problem with there = motherboard, because I have used that exact-same controller with FreeBSD = 2.2.7 on another motherboard with no problems. I have also been through = all the normal trouble-shooting. The original problem was that FreeBSD would just sit-there waiting for = the SCSI disk to settle, and timeout! But if I took it to another PC... = NO PROBLEM WHAT SO EVER! It was suggested that my problem with a standard Adaptec 3940UW, was a = driver issue and I quote SuperMicro: "As, I mentioned on last answer. A lot of Hardware manufacture use it. = There is no such problem at all. But I got a lot of call, most of their = problem came from the IRQ sharing. The software driver cannot share IRQ = resource." This can hardly be true?? I seem to be just going around in circles. I have given them the Adaptec = chip sets three times (7880) and yet they say they need to know what the = chip set is??? I'm confused!! Can anyone give me a decisive answer as to what might be wrong with the = SuperMicro Board (9 PCI slots, i960 controller...)? Greg ------=_NextPart_000_00F9_01BDEDF5.596C92A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
While talking (E-mail) to SuperMicro about a problem = with an=20 Adaptec 3940UW OR a 2940UW and one of their motherboards.
(P6DLH motherboard, i960 I/O = controller)
 
I suggested that there was some = fundamental=20 design problem with there motherboard, because I have used that = exact-same=20 controller with FreeBSD 2.2.7 on another motherboard with no problems. I = have=20 also been through all the normal trouble-shooting.
 
The original problem was that = FreeBSD would just=20 sit-there waiting for the SCSI disk to settle, and timeout! But if I = took it to=20 another PC... NO PROBLEM WHAT SO EVER!
 
It was suggested that my problem with a standard = Adaptec=20 3940UW, was a driver issue and I quote SuperMicro:
 
"As, I mentioned on last answer. A lot of = Hardware=20 manufacture use it. There is no such problem at all. But I got a lot of = call,=20 most of their problem came from the IRQ sharing. The software driver = cannot=20 share IRQ resource."
 
This can hardly be true??
 
I seem to be just going around in circles. I have = given them=20 the Adaptec chip sets three times (7880) and yet they say they need to = know what=20 the chip set is??? I'm confused!!
 
Can anyone give me a decisive answer as to what = might be wrong=20 with the SuperMicro Board (9 PCI slots, i960 = controller...)?
 
Greg
------=_NextPart_000_00F9_01BDEDF5.596C92A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message