Date: Wed, 11 Mar 1998 11:33:18 -0600 From: Doug Ledford <dledford@dialnet.net> To: "Robert G. Brown" <rgb@phy.duke.edu> Cc: aic7xxx@FreeBSD.ORG Subject: Re: lookups with 2.1.8x Message-ID: <3506CADE.FFAC822C@dialnet.net> References: <Pine.LNX.3.96.980310151708.339A-100000@ganesh.phy.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert G. Brown wrote:
>
> Regarding the 2.1.X lockup when scanning the onboard 2940 on a P6DLS:
>
> I have a bit more data for anyone listening (possibly Doug Ledford?).
I'm here and listening, I'm just swamped at the moment with regular DialNet
work. Considering the size of our ISP is likely to close to double in the
next few months as we hit four more cities, I'm very busy getting new
systems, new Ciscos, new portmasters, new everything else, and tons of other
changes done as well as answering a lot of email from customers about other
things.
> (scsi0:0:0:0) Using wide (16 bit) transfers.
> (scsi0:0:0:0) Synchronous at 20.0MHz, offset 8.
> Vendor: SEAGATE Model: ST19101W Rev: 0014
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
> (scsi0:0:1:0) Using wide (16 bit) transfers.
> (scsi0:0:1:0) Synchronous at 20.0MHz, offset 8.
> Vendor: SEAGATE Model: ST34371W Rev: 0338
> ...
>
> generated in aic7xxx_parse_msg() called (I believe) from
> aic7xxx_handle_scsiint(), I expected to get some response from the
aic7xxx_parse_msg() is called from aic7xxx_handle_reqinit() which is called
from aic7xxx_handle_scsiint() which is called from aic7xxx_isr() which is
called by the core kernel code when we get an interrupt. The general
situation you are running into is a problem with the I/O APIC code in 2.1.85
and above with your motherboard. It's failing to get the interrupts to our
interrupt handler so we never finish things up. Try disabling the I/O APIC
code and also get in touch with Ingo Molnar about the problem and see if it
can get worked out.
> latter, but it was not invoked at all. So, somewhere between and the
> bus_width switch in the controller, 2.1.X goes off to neverland. From
> the observation that this appears to occur for more than one kind of
> SCSI controller (a buslogic, I believe, had the same problem with
> 2.1.(x>82)) it is probably in a non-driver specific section of the scsi
> initialization process. If you give me a hint where to look, I'll dump
> a bunch more printk's in and try to narrow it down some more.
--
Doug Ledford <dledford@dialnet.net>
Opinions expressed are my own, but
they should be everybody's.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3506CADE.FFAC822C>