[944] in linux-scsi channel archive
Re: 2.0.0/2.0.25 oopses with buslogic 956C and two 4G seagates ...
daemon@ATHENA.MIT.EDU (Leonard N. Zubkoff)
Sat Nov 16 14:04:56 1996
Date: Sat, 16 Nov 1996 11:01:26 -0800
From: "Leonard N. Zubkoff" <lnz@dandelion.com>
To: alan@lxorguk.ukuu.org.uk
CC: ptb@dit.upm.es, linux-scsi@vger.rutgers.edu
In-reply-to: <m0vOmgJ-0005KgC@lightning.swansea.linux.org.uk>
(alan@lxorguk.ukuu.org.uk)
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
Date: Sat, 16 Nov 1996 15:29:18 +0000 (GMT)
> scsi0: CCB #0 to Target 0 Impossible State
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I suspect that is the important message.
Good spotting, Alan!
> To rub salt in the wound, here is the FreeBSD dmesg for this machine (again).
> Can anyone give me a clue?
> pci0:13: Bus Logic, device=0x1040, class=storage (scsi) [no driver assigned]
> map(10): io(6000)
Well they seem to both think the I/O is on 6000
I believe all this code is doing is reporting on the contents of the PCI
Configuration Space.
> bt0: Bt956C/ 0-PCI/EISA/VLB(32bit) bus
> bt0: Using Strict Round robin scheme
> bt0 at 0x330 irq 11 on isa
Does that imply FreeBSD is only using the ISA interface ports. Could
it be a PCI issue.
Correct. Last I checked the FreeBSD BusLogic driver, it had no understanding
of anything beyond the "S" series boards, and no clue about PCI. Unless
they've changed it recently, you'd have to enable the legacy ISA Compatible I/O
Port for a BT-948/958 to even be recognized. That's also why people get
strange reports about the synchronous/asynchronous operation of their boards
and devices. Worse still, if the FreeBSD driver detects certain error
conditions it will issue a soft reset command that stops the driver dead, since
they don't reinitialize the card properly.
> pci0:13: Bus Logic, device=0x1040, class=storage (scsi) [no driver assigned]
> map(10): io(6000)
^^^^^^^^^^^^^^^^^^
Again it appears the FreeBSD driver may be relatively primitive and not have
PCI I/O support. Does the PCI data appear sane ?
Looks OK to me. This wouldn't be the first machine where the PCI BIOS calls
screwed up normal operation, if that was even what was happening here. I've
had a few reports of Tyan Tempest boards where it was necessary to disable
CONFIG_PCI at least for the BusLogic driver in order for the driver to work.
Something about the calls to pcibios_... would leave the system in a wedged
state.
Leonard
