All of this logic was simplified back in '05 in the BSD drivers by adding
this to the top of the function:
u_int dummy_column;
if (cur_column == NULL) {
dummy_column = 0;
cur_column = &dummy_column;
}
and then stripping out the cur_column =
>Yes, the module apa1480_cb was reported missing. Anyone know where can I
>find this module? It is not in redhat 7.1 pcmcia.
That module is no longer needed. The aic7xxx module (v6.1.13) should probe
cardbus cards.
--
Justin
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi
>I've installed kernel 2.4.5 on my box and 3 days later i got this
>message (repeated)
>
>May 29 10:33:31 phaistos kernel: scsi0:0:0:0: Cmd aborted from QINFIFO
>May 29 10:33:31 phaistos kernel: aic7xxx_abort returns 8194
>May 29 10:33:31 phaistos kernel: scsi0:0:0:0: Attempting to queue an
>ABORT
>On Fri, May 25, 2001 at 03:46:40PM +0200, Christian Hammers wrote:
>> On Fri, May 25, 2001 at 07:30:34AM -0600, Justin T. Gibbs wrote:
>> > Your bus settle delay is too short. Reconfig your kernel with
>> > a longer delay.
>> I set CONFIG_AIC7XXX_RESET_DE
>On Fri, May 25, 2001 at 07:30:34AM -0600, Justin T. Gibbs wrote:
>> Your bus settle delay is too short. Reconfig your kernel with
>> a longer delay.
>I set CONFIG_AIC7XXX_RESET_DELAY from 5 to 10
>and now after modprobe'ing it I got a segmentation fault and the mo
>Hello
>
>The "new"/"normal" aic7xxx driver of kernel 2.4.4 does not detect my
>Teac writer R55S. The aic7xxx_old does. In case this is not a known
>problem (apologies for not browsing the list..:)) I can give you more
>information on this.
Your bus settle delay is too short. Reconfig your kern
>Just joined the list so I apologize if this has already been addressed.
>
>Ever since I upgraded my kernel to 2.4.4 from 2.4.2, it will no longer
>recognize my Onstream ADR50 tape drive.
Your bus settle delay is too short. Reconfig your kernel with
a longer delay.
You should also upgrade to th
>Hi there,
>
>[1.] One line summary of the problem:
>
>Kernel 2.4.3 and 2.4.4 do not recognize my SCSI CD-ROM
Your bus settle delay is too short. Reconfig your kernel with
a longer delay.
You should also upgrade to the latest driver from here:
http://people.FreeBSD.org/~gibbs/linux/
In later
>Howdie, Justin
>
>Thanks for your reply. I checked: the source of the message is my
>"cdrecord -scanbus" command. It is supposed to check for devices on my
>bus.
>
>Apparently it does this by attempting to read one byte from each? I
>don't know much about them SCSI, but this seems to be a particu
>May 6 20:42:49 zeus kernel: (scsi0:A:3:0): data overrun detected in
>Data-in phase. Tag == 0x9.
>May 6 20:42:49 zeus kernel: (scsi0:A:3:0): Have seen Data Phase. Length
>= 1. NumSGs = 1.
>May 6 20:42:49 zeus kernel: sg[0] - Addr 0x3c38000 : Length 1
I don't know about the mod-probe message
>[EMAIL PROTECTED] wrote:
>> I want to create a subdirectory under scsi for my module. The
>> tree that I want to create a something like this:
>>
>> drivers/scsi/xxx
>> drivers/scsi/xxx/lib
>> drivers/scsi/xxx/my_hba_driver
>
>Hiren,
>
>aic7xxx is in a subdirectory under drivers/scsi in the 2.4.
>running RedHat Linux 7.0 on an i686 SMP system. The kernel
>compilation fails for the SCSI drivers?
Upgrade to the latest aic7xxx driver from here:
http://people.FreeBSD.org/~gibbs/linux
--
Justin
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message
>"Justin T. Gibbs" wrote:
>> It is bogus that this stuff depends on link order to function
>> correctly.
>
>No, it is simply one more rule, and one that is not immediately
>obvious. Take heart though. Like Rolaids, 2.5's updated makefile
>system will br
>The intent is that all built in HBA drivers are
>initialized _before_ the built in upper level
>drivers (e.g. sd). To get the effect you describe
>the driver init order seems to have been:
> register ncr53c8xxx
> register sd
> register aic7xxx # too late ...
It is bogus that this stuff
>
>I'm using 2.4.3 vanilla with aic7xxx (aic7880 onboard)
>I set the max # of TCQ commands per device setting to 50..what's a really
>good setting for this, just the default of 253?
Depends on the device. The aic7xxx driver will determine the
maximum number of tags that a particular device can h
>On Sun, 1 Apr 2001, Douglas Gilbert wrote:
>
>[...]
>
>> > scsihosts <
>>
>> As a boot time option try:
>> scsihosts=aic7xxx:ncr53c8xxx
>> or if you are using lilo, in /etc/lilo.conf add:
>> append="scsihosts=aic7xxx:ncr53c8xxx"
>
>that does indeed change the bus numberi
># dmesg
>...
>SCSI subsystem driver Revision: 1.00
>request_module[scsi_hostadapter]: Root fs not mounted
>scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.1.5
^
This is quite old. Try this:
http://people.FreeBSD.org/~gi
>120mm (width) x 64mm (height)
>
>What's the height of the 29160LP ?
The card is longer than that (essentially the long enough to fit in
a 64bit connector + ~3mm), but the hight sounds about right.
>Just located two low-profile Adaptec cards. 2930LP and 2915LP. Are these
>supported?
These are s
>I looked at Adaptec SCSI cards, and they are not really low profile as
>compared to the Logitec or IO-Data. But, I'll look through again.
The 29160LP is at most, half the hight of a normal PCI card. I believe
you can get it either with a full or half hight plate. How much smaller
are the Logit
While testing the aic7xxx error recovery handler under 2.2.18, I experienced
repeated panics complaining that host_failed was not zero after error
recovery completed. Since my driver does release the io_request_lock
during recover, it is possible for a command, that has passed the check
in the to
For some reason, the error recovery code issues a test unit ready
with a 256 byte buffer. This wouldn't be so bad (just a useless allocation)
except for the fact that the command correctly states that no data will
be transferred. This confuses the logic of some drivers which assume that
a data t
>Agreed. Good point for the theory. But in practice, entering driver
>methods without any lock against the access method may lead to subtle
>races. At least Linux/SCSI hasn't this kind of races.
>Btw, I am not so sure about FreeBSD/CAM, for example. :-)
In any system, you have to deal with races
>Note that the interrupt service routine should also be
>grabbing io_request_lock when the interrupt arrives, and releasing it before
>the interrupt service routine returns. Thus when the error handler thread
>wakes up from the sleep (as a result of either a timer firing or an
>interrupt), the e
>Well the driver isnt allowed to hold interrupts off for > 1 tick because
>that messes up the clock, and at 1 second the watchdog nmi will reboot
>
>scsi driver authors therefore need to adjust their drivers
If you ask me, it is a bug that the io_request lock is forced on low
level drivers at all
>Hi All,
>
>Is there any way to force the kernel/scsi layer to call
>the eh_device_reset_handler and other eh_?? entry points ?
>I need to test those routines for our HBA.
Set an extrememly short timeout in the peripheral drivers
servicing the peripherals on your bus. I use a 500 or 250ms
timeo
>The Scsi_Cmnd::scsi_level member looks promising for
>controlling whether that is done:
>if (SDpnt->scsi_level <= SCSI_2)
> scsi_cmd[1] = (lun << 5) & 0xe0;
This is the correct thing to do. You'll also need to inherit the
scsi_level on new lun instances for a target that already has p
>Hi people,
>
>Apparently my last mail to the aic7xxx beta driver people provoked no
>reaction. The patches didnt modify the aic7xxx readme so I might have been
>mailing wrong people.
>
>Does anyone now how to contact the actual people doing the 6.0.8 beta?
I'm listening. I just haven't had time
luded
in hosts.c
--
Justin
Justin T. Gibbs
OpenSource Embedding
Adaptec Inc.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
28 matches
Mail list logo
