FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F7.1.0_cvs 2008-12-31T22:57:14Z 2008-12-31T22:57:14Z Ken Smith kensmith@FreeBSD.org 2008-12-31T22:57:14Z urn:sha1:8d4eb975d2e49f56d057a19aac09bcb92b3e71f7 Approved by: re (implicit) This commit was manufactured to restore the state of the 7.1-RELEASE image. 2007-07-02T20:08:20Z Matt Jacob mjacob@FreeBSD.org 2007-07-02T20:08:20Z urn:sha1:4607e8eed375ee34622d510c6de7d922843caca5 First, we were never correctly checking for a 24XX Status Type 0 response- that cased us to fall through to evaluate status for commands as if this were a 2100/2200/2300 Status Type 0 response. This is *close*, but not quite the same. This has been reported to be apparent with some wierd lun configuration problems with some arrays. It became glaringly apparent on sparc64 where none of the correct byte swap things were done. Fixing this omission then caused a whole universe shifting debug cycle of endian issues for the 2400. The manual for 24XX f/w turns out to be wrong about the endianness of a couple of entities. The lun and cdb fields for the type 7 request are *not* unconditionally big endian- they happen to be opposite of whatever the endian of the current machine type is. Same with the sense data for the 24XX type 0 response. While we're at it investigate and resolve some NVRAM endian issues. Approved by: re (ken) MFC after: 3 days 2007-04-02T01:04:20Z Matt Jacob mjacob@FreeBSD.org 2007-04-02T01:04:20Z urn:sha1:9a1b0d43c2f8d1deb2221cb48d3c0227875cc5fa When the linux port changes were imported which split the target command list to be separate from the initiator command list and the handle format changed to encode a type in the handle the implications to the function isp_handle_index (which only the NetBSD/OpenBSD/FreeBSD ports use) were overlooked. The fault is twofold: first, the index into the DMA maps in isp_pci is wrong because a target command handle with the type bit left in place caused a bad index (and panic) into dma map. Secondly, the assumption of the array of DMA maps in either PCS or SBUS attachment structures is that there is a linear mapping between handle index and DMA map index. This can no longer be true if there are overlapping index spaces for initiator mode and target mode commands. These changes bandaid around the problem by forcing us to not have simultaneous dual roles and doing the appropriate masking to make sure things are indexed correctly. A longer term fix is being devloped. 2007-03-22T23:38:32Z Matt Jacob mjacob@FreeBSD.org 2007-03-22T23:38:32Z urn:sha1:5f634111fa1d8624be0e9dc62e38dbbacc2342e0 b) Split default param fetching/setting into scsi and fibre functions and retry the fibre fetch more than once. MFC after: 1 week 2007-03-10T02:39:54Z Matt Jacob mjacob@FreeBSD.org 2007-03-10T02:39:54Z urn:sha1:e48b2487a0c478497ada13a111ea69861d7853a1 2006-11-18T03:53:16Z Matt Jacob mjacob@FreeBSD.org 2006-11-18T03:53:16Z urn:sha1:04697f7aa340daf1ab2198e63aafd1115436b9b3 and provied an isp_control entry point so that the outer layers can do PLOGI/LOGO explicitly. Add MS IOCB support. This completes the cycle for base support for SMI-S. 2006-11-16T00:39:56Z Matt Jacob mjacob@FreeBSD.org 2006-11-16T00:39:56Z urn:sha1:2cad1d98578c14cb49f77b764e4073d545ae8b6f Only complain about FC Reponse errors if they're nonzero. Shorten some PortID printouts for local loop. Add an internal isp_xcmd_t data structure which we'll use for some CT-Passthru support as part of adding SMI-S. 2006-11-16T00:31:46Z Matt Jacob mjacob@FreeBSD.org 2006-11-16T00:31:46Z urn:sha1:e49f99cd9fb539b5f6a83e08dc56045288488ea4 2006-11-14T08:45:48Z Matt Jacob mjacob@FreeBSD.org 2006-11-14T08:45:48Z urn:sha1:f7c631bcf0297e0517d7867f754228c34d5d7d59 gone device timers and zombie state entries. There are tunables that can be used to select a number of parameters. loop_down_limit - how long to wait for loop to come back up before declaring all devices dead (default 300 seconds) gone_device_time- how long to wait for a device that has appeared to leave the loop or fabric to reappear (default 30 seconds) Internal tunables include (which should be externalized): quick_boot_time- how long to wait when booting for loop to come up change_is_bad- whether or not to accept devices with the same WWNN/WWPN that reappear at a different PortID as being the 'same' device. Keen students of some of the subtle issues here will ask how one can keep devices from being re-accepted at all (the answer is to set a gone_device_time to zero- that effectively would be the same thing). 2006-11-02T03:21:32Z Matt Jacob mjacob@FreeBSD.org 2006-11-02T03:21:32Z urn:sha1:10365e5a68725142a2a7effaec46ca1d8f5b273a