From owner-freebsd-scsi@FreeBSD.ORG Fri Aug 29 22:43:43 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91930106567C for ; Fri, 29 Aug 2008 22:43:43 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id 64C8D8FC19 for ; Fri, 29 Aug 2008 22:43:43 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1408796rvf.43 for ; Fri, 29 Aug 2008 15:43:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=1XDLVW422pJxitM0R4olKQetpx6hiIpCAUV40FDC1CY=; b=kahms9NYL/rEcIAiyfOS5LfP9BWochCBPHslnbdoPYJpk7OGAK7CpiAQzcoghOSzds mY2ctzirfUzUniLX49ACMCrCzWttQ1Xu1EtvA9MvyhKKxIq9+E1ny5QAw5Yan0xnDqly Tpz+AaQqAK+40VPGq0z7mG1+r0gjGheErerYk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Ej08H4JrnPYR6GUGO90tvAWqKbZmBwSa0bAhDBASha4iCTkHvMWs4DmMjZP2uGxvLm jxkBJJo7/Mmpv/IaLbkM1IebJcbpSaX9Qq2YVbIArzXaAeEfwmVUycUR9RFUogsp/8N7 Ib1qs8qgzqkiY4SzmmgYlGw9uydF54lpBVYwI= Received: by 10.141.123.4 with SMTP id a4mr1800535rvn.172.1220049822637; Fri, 29 Aug 2008 15:43:42 -0700 (PDT) Received: by 10.140.127.19 with HTTP; Fri, 29 Aug 2008 15:43:42 -0700 (PDT) Message-ID: <3c0b01820808291543q694c9692jc0f1e7c922344f29@mail.gmail.com> Date: Fri, 29 Aug 2008 18:43:42 -0400 From: "Alexander Sack" To: "Sean Bruno" In-Reply-To: <48B837DB.1000903@miralink.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48B6E19A.7050603@miralink.com> <3c0b01820808281059k3c33e352g6be72f02817e8e6a@mail.gmail.com> <48B6EF1A.1040805@miralink.com> <3c0b01820808290951s6a3a8ebuf6ea501308ed91c3@mail.gmail.com> <48B837DB.1000903@miralink.com> Cc: freebsd-scsi@freebsd.org Subject: Re: [ISP] QLA2432 Target Mode Broken X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Aug 2008 22:43:43 -0000 If I get a chance, maybe I can try that and see what happens to me!! -aps On Fri, Aug 29, 2008 at 1:54 PM, Sean Bruno wrote: > Alexander Sack wrote: >> >> On Thu, Aug 28, 2008 at 2:31 PM, Sean Bruno wrote: >> >>> >>> Alexander Sack wrote: >>> >>>> >>>> On Thu, Aug 28, 2008 at 1:34 PM, Sean Bruno wrote: >>>> >>>> >>>>> >>>>> I tried putting a 2432 into target mode this week and noted that the >>>>> system >>>>> threw a pretty nice panic and thought I would post the output here. >>>>> Reviewing the 4G documentation from Qlogic, it looks like they've >>>>> substantially changed the target mode interface, so I'm not surprised >>>>> that >>>>> there's some work to do. If anyone has any patches they'd like me to >>>>> test, >>>>> I'm open to integration: >>>>> >>>>> >>>> >>>> Did you rebuild the isp driver with -DISP_TARGET_MODE defined? I only >>>> mention this because the output below seems like you twiddled the >>>> "role" hint instead of actually recompile the driver? >>>> >>>> -aps >>>> >>>> >>> >>> Ah, yes, that's a little magic I was trying ... sorry about that. >>> >>> Yes, I definitely compiled with ISP_TARGET_MODE defined. :) >>> >> >> Yea sorry, I just was checking. I don't have a clue right now why you >> are dying but some else is seeing similar nastiness in target mode. >> Minimally you should file a bug. >> >> How did you setup your box, how do you reproduce etc. etc.? >> >> thanks! >> >> -aps >> > > Well, I put a 2432 into my box and recompiled with target mode enabled. > Nothing fancy. > > :) > > A 23XX card in it's place works just fine. > I believe, due to the architecture difference between the 4G/8G and 2G cards > that it just doesn't work right now. > The 4G/8G architecture does nothing in target mode except DMA the incoming > data. the 2G cards do some things > for the driver. > > I was hoping that someone has some patches in their trees just lying around > that I could look over and test for > 4G target mode support. :) > > -- > Sean Bruno > MiraLink Corporation > 6015 NE 80th Ave, Ste 100 > Portland, OR 97218 > Phone 503-621-5143 > Fax 503-621-5199 > MSN: sbruno@miralink.com > Google: seanwbruno@gmail.com > Yahoo: sean_bruno@yahoo.com > >